Anyone using Crashlytics, is it normal to not see ...
# random
u
Anyone using Crashlytics, is it normal to not see crashes that cause app to never startup again? i.e. crash on start? Because I messedup sqlite migration, google play console is full of reports, crashlytics doesn't show any. (However google play reports are stupid because they for what ever reason strip exception messages, so its mostly useless)
l
Crashlytics runs from within your app, so yes, it's normal, it never has a chance to run.
u
are play store console reports without messages as well for you? i.e. the stacktrace is full but 1st line say just
FooException: ... nothing
l
Do you really need them if you know you need up database migration and can reproduce it?
u
Huh? Migration contains a crash, and I need to know why, why would you even argue that
l
Sorry, I meant "messed" instead of "need", typed too fast. What I meant is that you have both apps, and the source code of both versions, so you can reproduce it on your end anyway.
u
If I could I would fix it, I'm not yesterday's. Locally the trace contains exactly the issue, google strips it I bet for some "personal info protection" reason, which it contains none of, and rendering it useless
l
It's useful enough for you to know it's the same as what you have locally apparently. Anyway, you can still fix it for future upgraders, and I think there's also ways to fix it for existing users that upgrade, and you can try it on your side. Also, I'm pretty sure some of your users are hoping that you publish a version that fixes the crashes and lets them recover their data.
u
I don't follow. I cannot reproduce the issue, it works on all my phones and emulators, hence anything, i.e. a message would be helpful, but google knows better apparently; and at the thing, users are waiting for a fix, have no idea what you mean
l
If there's truly a database migration issue, you an reproduce that one time trigger issue by installing an older version with the schema the app had, and installing the upgrade on top of it.