not working on Android 9 (release apk)
See original GitHub issueOS:
- Windows
- MacOS
- Linux
Platform:
- iOS
- Android
SDK:
-
@sentry/react-native
-
react-native-sentry
react-native
version: 0.60.4
Init Code:
Sentry.init({
dsn: 'https://...@sentry.io/...'
});
I have following issue: not working on Android 9 (simulator or device)
Description goes here …
Steps to reproduce:
- Step build simple application in Android Studio (release.apk)
Actual result:
- Actual Sentry no catching crush or messages
url to repo (simple app) https://bitbucket.org/webforuse/sandbox/src/master/
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:8 (1 by maintainers)
Top Results From Across the Web
Fix an installed Android app that isn't working - Google Support
Step 1: Restart & update · Open your phone's Settings app. · Near the bottom, tap System and then Advanced and then System...
Read more >Android Pie - 9 (API 28) : Installing APK .... not successfully ...
1 Answer 1 · Go to settings and turn off your Developer Options . · Restart your device. · Go to settings again...
Read more >Android 9 release notes | Android Open Source Project
This page summarizes the major features in the Android 9 release, and provides links to additional information. These feature summaries are ...
Read more >How to Fix Android App Not Installed Error
If your phone and apps go wrong, generally you can also clear the cache and data of the Package installer. To do this:...
Read more >Fetch not working in release APK · Issue #24361 - GitHub
If anyone is facing the same issue, because of the "http" just add android:usesCleartextTraffic="true" to the Manifest, and you should be good.
Read more >
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 found the origin of the crash and a workaround (at least for my case).
@MacKentoch Good work!!