[com.microsoft.skydrive] crashes on start using v0.2.13.203915 while working with v0.2.12.203315
See original GitHub issueAffected app Name: OneDrive Package id: com.microsoft.skydrive
Describe the bug Crashes on start
To Reproduce Always, even after reinstall
Expected behavior Working as with v0.2.12.203315
Screenshots If applicable, add screenshots to help explain your problem.
System Android Version: 10 Custom ROM: LineageOS 17.1
microG microG Core version: 0.2.13.203915 microG Self-Check results: all ticked
Additional context Initially thought the issue is caused by “FakeStore”, but @JonnyTech leads me finally to “GmsCore”, see also https://github.com/microg/FakeStore/issues/24
Related log lines.
10-31 08:10:03.798 5773 5790 I ActivityTaskManager: START u0 {flg=0x4000000 cmp=com.microsoft.skydrive/.fre.OnboardingExperienceActivity (has extras)} from uid 10220
10-31 08:10:03.812 7015 7042 D GmsFirebaseAuth: bound by: GetServiceRequest{serviceId=FIREBASE_AUTH, gmsVersion=12451000, packageName='com.microsoft.skydrive', extras=Bundle[{com.google.firebase.auth.API_KEY=AIza***}]}
10-31 08:10:03.813 11886 11938 E AndroidRuntime: FATAL EXCEPTION: GoogleApiHandler
10-31 08:10:03.813 11886 11938 E AndroidRuntime: Process: com.microsoft.skydrive, PID: 11886
10-31 08:10:03.813 11886 11938 E AndroidRuntime: java.lang.IllegalStateException: A fatal developer error has occurred. Class name: zzf. Start service action: com.google.firebase.auth.api.gms.service.START. Service Descriptor: com.google.firebase.auth.api.internal.IFirebaseAuthService.
10-31 08:10:03.813 11886 11938 E AndroidRuntime: at com.google.android.gms.common.internal.BaseGmsClient$a.zza(SourceFile:13)
10-31 08:10:03.813 11886 11938 E AndroidRuntime: at com.google.android.gms.common.internal.BaseGmsClient$zzc.zzo(SourceFile:6)
10-31 08:10:03.813 11886 11938 E AndroidRuntime: at com.google.android.gms.common.internal.BaseGmsClient$b.handleMessage(SourceFile:35)
10-31 08:10:03.813 11886 11938 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:107)
10-31 08:10:03.813 11886 11938 E AndroidRuntime: at com.google.android.gms.internal.common.zze.dispatchMessage(SourceFile:1)
10-31 08:10:03.813 11886 11938 E AndroidRuntime: at android.os.Looper.loop(Looper.java:214)
10-31 08:10:03.813 11886 11938 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:67)
Issue Analytics
- State:
- Created 3 years ago
- Reactions:4
- Comments:9 (1 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I was able to downgrade to GmsCore-v0.2.12.203315.apk using adb without downgrading MicroG release on the phone - but only with the former LOS with MicroG from October 16 (I did an update to get the German Corona Warn app running).
Today updated to LOS with MicroG from November 10 and here the downgrade will not work anymore because the bundled version can’t be erased
Downgrade with “adb sideload” did not succeed, Android claimed about broken system encryption…fortunatly update to latest version brought phone back to life…
Potentially this issue will get more attention now since the LOS with MicroG upgrade is available for the public now…
Installed https://microg.org/dl/core-nightly.apk now, OneDrive is starting again (no reboot required) => THANK YOU VERY MUCH!!!