Facing FATAL EXCEPTION: McsHandler after integrating micro g into my android 11 based ROM while doinf money stress state
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
06-01 15:08:37.018 3417 3725 E AndroidRuntime: FATAL EXCEPTION: McsHandler
06-01 15:08:37.018 3417 3725 E AndroidRuntime: Process: com.google.android.gms:persistent, PID: 3417
06-01 15:08:37.018 3417 3725 E AndroidRuntime: java.lang.IllegalArgumentException: Cursor for query content://com.google.android.gms.microg.settings/gcm [gcm_full_log, gcm_last_persistent_id, gcm_confirm_new_apps, gcm_enable_mcs_service, gcm_network_mobile, gcm_network_wifi, gcm_network_roaming, gcm_network_other, gcm_learnt_mobile, gcm_learnt_wifi, gcm_learnt_other] was null
06-01 15:08:37.018 3417 3725 E AndroidRuntime: at org.microg.gms.settings.SettingsContract$getSettings$1.invoke(SettingsContract.kt:160)
06-01 15:08:37.018 3417 3725 E AndroidRuntime: at org.microg.gms.settings.SettingsContract.withoutCallingIdentity(SettingsContract.kt:151)
06-01 15:08:37.018 3417 3725 E AndroidRuntime: at org.microg.gms.settings.SettingsContract.getSettings(SettingsContract.kt:158)
06-01 15:08:37.018 3417 3725 E AndroidRuntime: at org.microg.gms.gcm.GcmPrefs$Companion.get(GcmPrefs.kt:46)
06-01 15:08:37.018 3417 3725 E AndroidRuntime: at org.microg.gms.gcm.GcmPrefs.get(Unknown Source:2)
06-01 15:08:37.018 3417 3725 E AndroidRuntime: at org.microg.gms.gcm.McsService.logd(McsService.java:168)
06-01 15:08:37.018 3417 3725 E AndroidRuntime: at org.microg.gms.gcm.McsService.handleMessage(McsService.java:684)
06-01 15:08:37.018 3417 3725 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:103)
06-01 15:08:37.018 3417 3725 E AndroidRuntime: at android.os.Looper.loop(Looper.java:214)
06-01 15:08:37.018 3417 3725 E AndroidRuntime: at org.microg.gms.gcm.McsService$HandlerThread.run(McsService.java:163)
06-01 15:14:15.833 11594 11676 E AndroidRuntime: FATAL EXCEPTION: McsHandler
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the crash on the reported Android 11 ROM, then trace SettingsContract.getSettings through GcmPrefs.get and McsService.handleMessage using the supplied stack trace. Done means the McsHandler fatal exception no longer occurs in the reported money stress state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100