Closed Bug 956581 Opened 11 years ago Closed 11 years ago

RuntimeException (NPE) in selecting 'Firefox Account' in Android's Settings

Categories

(Firefox for Android Graveyard :: Android Sync, defect)

Firefox 29
ARM
Android
defect
Not set
normal

Tracking

(firefox29 verified, fennec29+)

VERIFIED FIXED
Firefox 29
Tracking Status
firefox29 --- verified
fennec 29+ ---

People

(Reporter: aaronmt, Assigned: nalexander)

References

Details

(Keywords: reproducible, Whiteboard: [qa+])

W/Binder ( 772): Caught a RuntimeException from the binder stub implementation. W/Binder ( 772): java.lang.NullPointerException W/Binder ( 772): at com.android.server.accounts.AccountManagerService$Session.onResult(AccountManagerService.java:2203) W/Binder ( 772): at android.accounts.IAccountAuthenticatorResponse$Stub.onTransact(IAccountAuthenticatorResponse.java:59) W/Binder ( 772): at android.os.Binder.execTransact(Binder.java:404) W/Binder ( 772): at dalvik.system.NativeStart.run(Native Method) This RuntimeException currently locks up Android's Settings utility requiring a force-stop needed to undo the damage. Steps: * LG Nexus 5 (Android 4.4.2) → Settings → Accounts → 'Add Account' → 'Firefox Accounts' -- Nightly (01/05)
Blocks: 808813
Never seen this one before. I wonder if this is due to the multiple-SyncAdapter hijinks I'm playing with? Those are scheduled to go. This whole Add Account flow is being re-worked, so I expect this to be resolved in the course of the battle, but we'll block on it for release. Thanks, Aaron!
Whiteboard: [qa+]
tracking-fennec: ? → 29+
Status: NEW → ASSIGNED
Whiteboard: [qa+] → [qa+][fixed in services]
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [qa+][fixed in services] → [qa+]
Target Milestone: --- → Firefox 29
Flags: needinfo?(aaron.train)
Keywords: verifyme
Status: RESOLVED → VERIFIED
Flags: needinfo?(aaron.train)
Keywords: verifyme
Product: Android Background Services → Firefox for Android
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.