6

Preface: I acknowledge that the official mobile apps are no longer supported by Stack Exchange and no proper bug fixes will be deployed. This is more for documentation/announcement (and possibly a heads-up, and finding a workaround if any) since Android supports sideloading an app and some are still using it exclusively for the push notifications. It also serves as a duplicate target for future such reports.


On the final version of the Stack Exchange Android app, v1.0.95, the app crashes on startup on Android 12 while it's still (kind of) working on older Android versions.

According to the logcat, this is due to improper initialization of Fabrics/Crashlytics, a 3rd-party library for reporting crashes (which is somewhat ironic).

10-21 09:18:09.967 28168 28168 E Fabric  : Crashlytics must be initialized by calling Fabric.with(Context) prior to calling Crashlytics.getInstance()
10-21 09:18:09.967 28168 28168 D AndroidRuntime: Shutting down VM
10-21 09:18:09.967 28168 28168 E AndroidRuntime: FATAL EXCEPTION: main
10-21 09:18:09.967 28168 28168 E AndroidRuntime: Process: com.stackexchange.marvin, PID: 28168
10-21 09:18:09.967 28168 28168 E AndroidRuntime: java.lang.IllegalStateException: Must Initialize Fabric before using singleton()
10-21 09:18:09.967 28168 28168 E AndroidRuntime:        at io.fabric.sdk.android.Fabric.singleton(Fabric.java:254)
10-21 09:18:09.967 28168 28168 E AndroidRuntime:        at io.fabric.sdk.android.Fabric.getKit(Fabric.java:502)
10-21 09:18:09.967 28168 28168 E AndroidRuntime:        at com.crashlytics.android.Crashlytics.getInstance(Crashlytics.java:432)
10-21 09:18:09.967 28168 28168 E AndroidRuntime:        at com.crashlytics.android.Crashlytics.isDisabled(Crashlytics.java:1074)
10-21 09:18:09.967 28168 28168 E AndroidRuntime:        at com.crashlytics.android.Crashlytics.doLog(Crashlytics.java:486)
10-21 09:18:09.967 28168 28168 E AndroidRuntime:        at com.crashlytics.android.Crashlytics.log(Crashlytics.java:482)
10-21 09:18:09.967 28168 28168 E AndroidRuntime:        at com.stackexchange.marvin.utils.Helpers.log(Helpers.java:186)
10-21 09:18:09.967 28168 28168 E AndroidRuntime:        at com.stackexchange.marvin.utils.Helpers.log(Helpers.java:190)
10-21 09:18:09.967 28168 28168 E AndroidRuntime:        at com.stackexchange.marvin.Current$1.onConnected(Current.java:246)

While proper fixes cannot be expected, something like a workaround will be appreciated.

12
  • Quick note - we were discussing this on chat, and for those of us still using the app, having some documentation of when it broke is probably useful. Dec 12, 2021 at 5:30
  • @JourneymanGeek I posted this chat message on the day it broke, October 20. Dec 12, 2021 at 5:33
  • Yeah, I saw that. It probably broke 'earlier' tho, Just that folks are seeing failures as they upgrade to android 12 Dec 12, 2021 at 5:33
  • 3
    What is wrong with this, and why isn't this a dupe of it: How can I report bugs with or request features for the Stack Exchange mobile apps?
    – Luuklag
    Dec 12, 2021 at 7:50
  • 5
    Sorry not sure what's the point here? The horse is dead. Bury it and let it rest in peace. Dec 12, 2021 at 7:50
  • 1
    Broke 6 years ago, the incorrect call is simply being caught now.
    – Rob
    Dec 12, 2021 at 9:21
  • 2
    @ShadowWizardIsVaccinatedV3 - If people are still using the app, like me, this is literally the point where the app is unusable for everyone still using it. No "It does notifications then it crashes", no "It could work.... In addition since android 12 upgrades don't happen all at once it gives something searchable. Dec 12, 2021 at 10:07
  • 2
    @JourneymanGeek still using horse metaphor... you were just riding a dead horse all those years, fact he kept going was just a miracle, never intended by its creator. I don't have anything against it, but still consider this the same as all bug reports since the official declaration about the app death. This just happens to be a bigger bug. People can still, in theory, just use a device with lower version of android and "enjoy" the app. (And remember to never let the device update to 12 ;)) Dec 12, 2021 at 11:12
  • 4
    Does this answer your question? How can I report bugs with or request features for the Stack Exchange mobile apps?
    – Luuklag
    Dec 12, 2021 at 12:28
  • 3
    @Luuklag The top part of the post explains why it's not a duplicate of the general "app is unsupported" posts. Can you please explain why you believe that explanation to be inadequate? Dec 12, 2021 at 17:48
  • "this is a documentation" That's not something that we really need. I see value in this as a "signpost" because mentioning Android 12, but thats about it. @SonictheAnonymousHedgehog
    – Luuklag
    Dec 12, 2021 at 22:36
  • 1
    And what about the clause in the proposed duplicate that says that "...[support] questions can still be asked, and perhaps the community here knows a workaround for your [bug]"? I think this question is a perfect fit for that clause, so... if we're not going to respect it, it should really be removed. Otherwise, this question should stay open.
    – zcoop98
    Dec 13, 2021 at 16:56

0

You must log in to answer this question.

Browse other questions tagged .