Closed Bug 1535168 Opened 9 months ago Closed 7 months ago

Crash reporter broken on Android Q

Categories

(GeckoView :: General, defect, P1)

Unspecified
Android
defect

Tracking

(geckoview66 wontfix, firefox-esr60 wontfix, firefox65 wontfix, firefox66 wontfix, firefox67 wontfix, firefox68 fix-optional)

RESOLVED WORKSFORME
Tracking Status
geckoview66 --- wontfix
firefox-esr60 --- wontfix
firefox65 --- wontfix
firefox66 --- wontfix
firefox67 --- wontfix
firefox68 --- fix-optional

People

(Reporter: snorp, Assigned: snorp)

References

(Blocks 1 open bug, )

Details

(Whiteboard: [geckoview:fenix:m7] [bcs:p2] [webcompat-sci-exclude])

Attachments

(1 file)

Fennec Nightly (and GV) runs, but fails to report crashes. I get the following in logcat:

03-13 16:35:21.450 27755 27780 W google-breakpad: ExceptionHandler::GenerateDump cloned child
03-13 16:35:21.450 27755 27780 W google-breakpad: 27866
03-13 16:35:21.450 27755 27780 W google-breakpad:
03-13 16:35:21.450 27755 27780 W google-breakpad: ExceptionHandler::SendContinueSignalToChild sent continue signal to child
03-13 16:35:21.450 27866 27780 W google-breakpad: ExceptionHandler::WaitForContinueSignal waiting for continue signal...
03-13 16:35:21.859 1243 4058 W ActivityManager: Permission Denial: ActivityManagerShellCommand asks to run as user -2 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL

It looks like maybe am always tries to run as the shell user now, so we may not be able to use it within our app. All invocations of run-as org.mozilla.geckoview_example am start-foreground-service give the above error, but it's happier without run-as.

[geckoview:fenix:m4] because we should fix this for Fenix MVP but it is not an urgent blocker because Android Q is still pre-release.

OS: All → Android
Whiteboard: [geckoview:fenix:m4]

I filed https://issuetracker.google.com/issues/128544984 against Android, and I'm told (via backchannel) that it's a known issue in the beta.

Deferring to Fenix M5. This is not an urgent priority because Fenix MVP will be released before Android Q.

Whiteboard: [geckoview:fenix:m4] → [geckoview:fenix:m5]

Demoting to priority [geckoview:fenix:p2] because Android Q support is not a Fenix MVP release blocker.

Whiteboard: [geckoview:fenix:m5] → [geckoview:fenix:p2]
Blocks: android-q
Type: enhancement → defect
Whiteboard: [geckoview:fenix:p2] → [geckoview:fenix:p2][webcompat-sci-exclude]

Adding [geckoview:fenix:m7] whiteboard tag because we should fix our Android Q bugs soon but they're not strictly Fenix MVP release blockers.

Whiteboard: [geckoview:fenix:p2][webcompat-sci-exclude] → [geckoview:fenix:m7][webcompat-sci-exclude]
Whiteboard: [geckoview:fenix:m7][webcompat-sci-exclude] → [geckoview:fenix:m7] [bcs:p2] [webcompat-sci-exclude]

I just updated my Q beta to the one released today. While I was able to get the crash reporter to fire on the latest Nightly a few times, I did get instances where it didn't fire and I get the attached screenshot with an error message about a background activity being blocked. I also did get the error message in conjunction with the crash reporter dialog a few times.

Lets file a new bug for the background activity start issue. The issue in comment 0 is resolved with Android Q beta 3.

Status: NEW → RESOLVED
Closed: 7 months ago
Resolution: --- → WORKSFORME
Blocks: 1550291
No longer blocks: 1550291
You need to log in before you can comment on or make changes to this bug.