Android app crashing #5757
Comments
|
Hi @SteveScott, thanks for the report! What version of Android are you on? |
|
I am running Android 13
…On Tue, Sep 5, 2023, 6:00 PM Chris Bobbe ***@***.***> wrote:
Hi @SteveScott <https://github.com/SteveScott>, thanks for the report!
What version of Android are you on?
—
Reply to this email directly, view it on GitHub
<#5757 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABHLFSNF5RICOQNAFULYCWTXY6OGDANCNFSM6AAAAAA4MMTI4M>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Hmm, I wonder if this is #5741. |
|
I have also been experiencing the same issue for the past couple weeks, on Android 13 as well. |
|
We're aware that Android crashes have been becoming much more frequent recently, especially on Google Pixel devices, and we're investigating the cause. |
|
I also have this, started recently (in last two or three days) on Xiaomi phone running latest version of Android 13. Crashes now every time I open the app. How can I get logs to share, I can't work it out. Tried deleting cache and all app data and logging in again, same issue. |
|
I've been experiencing crashes for the past 2ish weeks as well, Android 13, almost always when typing, sometimes when not. Other lichess team members are also all starting to experience the same crashes as well. |
Me too. |
chrisbobbe
added
P0 critical
|
Thank you all for your patience. Debugging continues in the Zulip development community, here. Quoting @gnprice from there (link):
We suspect that a Google Play system update from August 1 is a factor in this crash. It seems those updates are rolled out gradually. If you tap Settings > About phone > Android version, you should see two dates, like this:
For anyone who's been seeing this issue's symptoms—crashes that started or became frequent in the last week or two—you may want to check that "Google Play system update" date. We expect you'll see August 1 there, and we'd like to know if that's wrong. Also, we don't yet have reports from anyone on a September 1 update, and we'd like to know if these new crashes persist with that update. |
|
I've been experiencing this issue since Sept 14. Zulip crashes frequently on Samsung Galaxy S23 Ultra, Android 13, "Google Play system update" date is August 1. |
|
chiming in: I've been seeing crashes for the past week at least, primarily after tapping on push notifications or typing out messages. |
|
Same as above, been having random crashes for a few weeks on a Pixel 7 Pro. Here's a crash log I got, from two crashes that happened last night.
|
|
Galaxy S23, new. Unusably bad crashing. Android 13 |
Our hope here is to fix the Android crashes in zulip#5757. If it works (as it seems to in internal testing!), it would support the theory that the Sentry Native SDK at 0.4.12 (and from others' reports, also 0.5.4) has a bad interaction with something in Google's Play Services system update on 2023-08-01 -- and that the interaction is not present with Sentry Native 0.6.5 (its current latest). Those Sentry Native SDK versions are deduced from Sentry *React Native* SDK versions (3.4.3, 5.1.1, and 5.9.2, respectively), using a process I wrote down: https://chat.zulip.org/#narrow/stream/48-mobile/topic/Android.20crashes/near/1643817 See a React Native issue: facebook/react-native#39505 and an issue in a Google tracker: https://issuetracker.google.com/issues/300840851?pli=1 and an issue in the Sentry Unity tracker: https://github.com/getsentry/sentry-unity/issues/1444 Done by following the upgrade guide at https://docs.sentry.io/platforms/react-native/migration/ starting in the "From 3.x to 4.x" section and working up through "From 4.x to 5.x". Not many declared breaking changes relevant to our app: - The `Severity` enum is removed in favor of string literals - The Sentry CLI had a big upgrade with declared breaking changes to handle in our iOS build We want to get this out to Android users quickly, so we postpone a few things for now: - Any testing on iOS - Flow types generated from the TypeScript using TsFlower. (We have a hand-translated libdef, but it's likely to be misleading because it's now outdated by two major versions. I've ripped it out here.) See our long debugging thread on CZO: https://chat.zulip.org/#narrow/stream/48-mobile/topic/.40sentry.2Freact-native.20to.20latest/near/1643986
Our hope here is to fix the Android crashes in zulip#5757. If it works (as it seems to in internal testing!), it would support the theory that the Sentry Native SDK at 0.4.12 (and from others' reports, also 0.5.4) has a bad interaction with something in Google's Play Services system update on 2023-08-01 -- and that the interaction is not present with Sentry Native 0.6.5 (its current latest). Those Sentry Native SDK versions are deduced from Sentry *React Native* SDK versions (3.4.3, 5.1.1, and 5.9.2, respectively), using a process I wrote down: https://chat.zulip.org/#narrow/stream/48-mobile/topic/Android.20crashes/near/1643817 See a React Native issue: facebook/react-native#39505 and an issue in a Google tracker: https://issuetracker.google.com/issues/300840851?pli=1 and an issue in the Sentry Unity tracker: https://github.com/getsentry/sentry-unity/issues/1444 Done by following the upgrade guide at https://docs.sentry.io/platforms/react-native/migration/ starting in the "From 3.x to 4.x" section and working up through "From 4.x to 5.x". Not many declared breaking changes relevant to our app: - The `Severity` enum is removed in favor of string literals - The Sentry CLI had a big upgrade with declared breaking changes to handle in our iOS build We want to get this out to Android users quickly, so we postpone a few things for now: - Any testing on iOS - Flow types generated from the TypeScript using TsFlower. (We have a hand-translated libdef, but it's likely to be misleading because it's now outdated by two major versions. I've ripped it out here.) See our long debugging thread on CZO: https://chat.zulip.org/#narrow/stream/48-mobile/topic/.40sentry.2Freact-native.20to.20latest/near/1643986 Fixes: zulip#5757
TODO: - Testing on iOS - Flow types generated from the TypeScript using TsFlower? (We have a hand-translated libdef, but it's likely to be misleading because it's now outdated by two major versions. I've ripped it out here.) Our hope here was to fix the Android crashes in zulip#5757. It didn't work; testing showed that the crash still happens on this later version: https://chat.zulip.org/#narrow/stream/48-mobile/topic/Android.20crashes/near/1644202 So if there's a bad interaction between the Sentry Native SDK and Google's Play Services system update on 2023-08-01, it's still present with Sentry Native 0.6.5 (the current latest), as well as other versions in prior reports: 0.4.12 (ours, just before this commit) and 0.5.4. For how to deduce a Sentry Native SDK version from a Sentry *React Native* SDK version, see https://chat.zulip.org/#narrow/stream/48-mobile/topic/Android.20crashes/near/1643817 See a React Native issue: facebook/react-native#39505 and an issue in a Google tracker: https://issuetracker.google.com/issues/300840851?pli=1 and an issue in the Sentry Unity tracker: https://github.com/getsentry/sentry-unity/issues/1444 Still, good to do the upgrade anyway, and if Sentry comes out with a fix, we'll be best placed to take it having already upgraded to the current latest. Done by following the upgrade guide at https://docs.sentry.io/platforms/react-native/migration/ starting in the "From 3.x to 4.x" section and working up through "From 4.x to 5.x". Not many declared breaking changes relevant to our app: - The `Severity` enum is removed in favor of string literals - The Sentry CLI had a big upgrade with declared breaking changes to handle in our iOS build See our long debugging thread on CZO: https://chat.zulip.org/#narrow/stream/48-mobile/topic/.40sentry.2Freact-native.20to.20latest/near/1643986
|
Thanks everyone for the reports! We've investigated this intensively over the past few days, and we've just released a version of Zulip that fixes these crashes: v27.213. If you're in the beta, the update is available now; if not, it'll be available once Play Store review is complete, which typically takes under a day. For more details, read on. This turns out to be an issue that's appearing in a number of different apps by different developers. It's being investigated in the issue trackers for Sentry, which is an error-reporting service we use, and for Android upstream:
The conditions that trigger the bug appear to be:
It's not yet clear whether the bug is in Sentry or in the Android system components that are updated in the Google Play system update. The issue persists even with the latest versions of the Sentry libraries, as we determined at #5765. In order to make these crashes stop happening for everyone using Zulip, our v27.213 release simply disables Sentry on Android. This isn't a super comfortable state to be in — error reporting is important for us to learn of other issues and fix them — but it lets us resolve the crashes while the Sentry folks work on a diagnosis and fix. I'll file a follow-up issue (→ #5766) for re-enabling Sentry without the crashes. |
gnprice
added
the
upstream: other
|
If you see a crash after updating to v27.213, please open a new issue. |
This is a workaround for zulip#5757, the crashes we've started to regularly see as many users' devices have started taking the Google Play system update dated 2023-08. See the (long) chat thread here: https://chat.zulip.org/#narrow/stream/48-mobile/topic/Android.20crashes/near/1640893 and issue threads reported in Android's and Sentry's trackers: https://issuetracker.google.com/issues/300840851 https://github.com/getsentry/sentry-unity/issues/1444 Our issue for re-enabling Sentry on Android is zulip#5766. This commit was cherry-picked from 29cea89, part of v27.213, with tweaks to mention zulip#5766.
This is a workaround for #5757, the crashes we've started to regularly see as many users' devices have started taking the Google Play system update dated 2023-08. See the (long) chat thread here: https://chat.zulip.org/#narrow/stream/48-mobile/topic/Android.20crashes/near/1640893 and issue threads reported in Android's and Sentry's trackers: https://issuetracker.google.com/issues/300840851 https://github.com/getsentry/sentry-unity/issues/1444 Our issue for re-enabling Sentry on Android is #5766. This commit was cherry-picked from 29cea89, part of v27.213, with tweaks to mention #5766.
This reverts commit f792c39, and effectively reinstates commit e8c57e7. It's aimed as a workaround for #5778, which appears to revive #5757. See chat thread: https://chat.zulip.org/#narrow/stream/48-mobile/topic/Android.20crash.20.23M5778/near/1659732
For the past month, as I am typing on my Android Pixel 7 Pro, Zulip crashes. No message or notification. I re-load the app and my text is still there. What can I do to help troubleshoot or report this bug? Version 27.211.
The text was updated successfully, but these errors were encountered: