Android App crashing after Google Play System August update #39505
Comments
github-actions
bot
added
the
Needs: Repro
|
|
UnderTheMoonspell
changed the title
UnderTheMoonspell
changed the title
UnderTheMoonspell
changed the title
|
Potentially related to #39183 Without a reproducer, we can't really help further. |
|
Hi, just for additional context: I think it's safe to assume this is an OS side issue and not related to react-native. |
|
Closing as moved to https://issuetracker.google.com/issues/300840851 |
|
@AtomicTroop have you singled out a configuration for the issue? We were initially considering the Google Play System update of August as for Samsung we were observing just for those but just found an user with an older update that also crashes. This issue is affecting all our previous app versions retro-actively. Also what kind of errors are you getting? We're seeing a variation of SIGSEGV, SIGABRT and SIGBUS, generally with a stack corruption message on libc. Majority of our errors are on Samsung devices. |
|
@4knahs I think this conversation is best continued over on Google's issue tracker, linked by @cortinico just now. Please repost your question there for the sake of visibility on Google's side. |
|
I also posted this over on the Google issue tracker, but through it would be best also here for clarity: We're looking at issues relating to Android app crashes and we noticed your post on this topic and we'd be interested to understand a bit more what you're seeing. Recently we're aware of there being an:
Is this what you're seeing and, if so, are you using any of the following pacakges?
|
cortinico
removed
Needs: Triage 🔍
Needs: Repro
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
|
We are having the same issue on :
|
|
For all Sentry users here: we just released fixes to our Native, Android, React Native and Unity SDKs to address these crashes as far as our codebase is concerned, see the updates here: getsentry/sentry-java#2955 (comment) (also posted on Google's issue tracker) |
Description
Hey all.
Recently, through Crashlytics, we started to notice a decrease in Crash Free Users % in our Android app. In iOS it stayed around 99%, but in Android dropped from 98%-99% we always had until next week, to about 88% since Friday.
Android:
iOS:
These are the errors that started to increase like crazy:
We had a new deploy of our production app few days before this started happening (although even prior versions of the app also had an uptick of errors), so we started procedures to deploy an older version. We rolledback two versions and it didnt help as our app kept crashing.
During the weekend we ran multiple tests to understand the root of the problem, as we were not able to reproduce it ourselves in the beginning:
The first (and so far only) cellphone we were able to reproduce the problem was a Samsung S21 Ultra 5G. We were then also able to replicate with Samsung Remote Lab Device S21 Ultra and the thing they have in common is that they both have Google Play System version from August 1st. All the other devices we've used to replicate the problem have a version prior to August, and we were never able to replicate it.
Although we had a problem trying to minify our app after upgrading to 0.72.4 (from 0.71.4), we ran it without minifying, but still had the crash.
We tried with versions of our app going as far back as one year, still had the crash.
This is the LogCat we have from the crash
This is the crashdump:
We didnt see a spike in memory/CPU consumption
React Native Version
0.71.4
Output of
npx react-native infoSystem:
OS: macOS 13.5.2
CPU: (10) arm64 Apple M1 Pro
Memory: 82.78 MB / 16.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 16.17.0
path: ~/.nvm/versions/node/v16.17.0/bin/node
Yarn:
version: 1.22.18
path: /opt/homebrew/bin/yarn
npm:
version: 8.15.0
path: ~/.nvm/versions/node/v16.17.0/bin/npm
Watchman:
version: 2022.10.24.00
path: /opt/homebrew/bin/watchman
Managers:
CocoaPods:
version: 1.12.1
path: *******
SDKs:
iOS SDK:
Platforms:
- DriverKit 22.4
- iOS 16.4
- macOS 13.3
- tvOS 16.4
- watchOS 9.4
Android SDK: Not Found
IDEs:
Android Studio: 2022.2 AI-222.4459.24.2221.9971841
Xcode:
version: 14.3.1/14E300c
path: /usr/bin/xcodebuild
Languages:
Java:
version: 11.0.11
path: /usr/bin/javac
Ruby:
version: 2.7.6
path: *******
npmPackages:
"@react-native-community/cli": Not Found
react: Not Found
react-native: Not Found
react-native-macos: Not Found
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: Not found
newArchEnabled: Not found
iOS:
hermesEnabled: Not found
newArchEnabled: Not found
Steps to reproduce
Open the app and it crashes right away, or eventually after fiddling with it briefly, it will crash
Snack, screenshot, or link to a repository
The text was updated successfully, but these errors were encountered: