[targetSdk 31 / Android 12] - Indirect notification activity start (trampoline) from <package-name> blocked #250
Comments
nishanttatva
changed the title
|
Forgot to mention, this only happens when app is in background or kill state and only in Android 12. Other versions and iOS are working fine. |
|
what's your build.gradle targetSdk ? Does this happen when you target 31, or just run on 31, regardless of target? Relevant new restriction:
How to diagnose: Remediation:
🤔 |
mikehardy
changed the title
SDK versions We were facing crashes on Android 12 devices when using a lower targetSdkVersion, so upgraded to 31. If its required we'll try to run a test with targetSdk=30 in an Android 12 device, would take some time though.
Yup, used the above docs to find the error log, (linked the same in my description). As mentioned, got the notification interaction logs to find the component which is using the trampolines. Attaching, if that's useful notif-interaction-logs.txt. |
|
Why not just paste the text in 🤔 ? This is a rich text environment :-) You should have no problem with targetSdk30 / compileSdk31, I don't believe targetSdk 31 is ready yet in the ecosystem in general, certainly not here, for example you will see silent failures to schedule alarms until this is resolved: #239 I do really appreciate the digging though, I did use your link directly :-) This will likely require some time to resolve, I certainly don't have the time now and won't for months. Luckily the targetSdkVersion cutovers on Play store are November 1, so there's 11 months to go. |
Hate scrolling through huge error logs in issue comments 😛 , sorry about that.
Okay will try out this config and report back here. |
|
Not sure about all maintainers but at least myself, I like having it all visible in one space. Can always use the markdown details feature to make it collapsible. I never expect people to have the ability to open attachments (think: mobile notification reading offline) so I try to keep it all up in a text trail. I may be old school though Definitely curious for reports on how targetSdkVersion 30 went |
|
Sorry for taking so long! But yes, setting @mikehardy I'm going to close this issue, but some libraries have moved to targetSdk31 (eg. react-native-bootsplash), so might need to do those changes later on (or sooner?). I might try to do those changes and open a PR for it, once I get the chance. Thanks! |
|
There is a big difference between compile, target, and min on those SDK versions. Compile 31 is early for most, but needed for some. And it's definitely needed in this module. It implies using JDK11, as a related item. Target 31 is very early, and too early for this module yet. It will take time. No modules for a target though, that should remain under control of the app. Google enforces target 30. Will not require target 30 until Nov 1, 2022. We already support target 30 though. No problem minSdkVersion is limited by ability to remain compatible and moves about same speed as target. Currently 21 is where we are at, same as react-native current I think. |
|
I think this needs to stay open, there is a workaround of using targetSdkVersion 30, but we will eventually (by Nov 1, 2022) need to support targetSdkVersion 31 |
|
If |
|
notifee does require compile of 31 |
|
@mikehardy |
|
Not sure where you would like it? Could be a help though. There's an edit button at top right of each page if you want to propose something |
Not by Nov 1. I think SDK / Library should target latest version of Android ASAP, so it will not become a blocker for app developer. |
|
@seventhmoon a reasonable point - that said, it is in progress, there is no intention to delay for example #301 |
|
Fixed in latest release (v4.1.0). |
(Accidental submit 🤦♂️ )
I'm facing an issue when displaying a local notification after receiving data-only message in the background (using react-native-firebase).
For android 12 devices, the app is not brought to foreground when tapping on notification. I need to press the app-icon to launch the app. Once the app is opened, it receives the notification and internal navigation works correctly.
On checking the logs and researching a bit about Android 12 notification changes, found that this error is thrown when I click on the notification.
Here's a screenshot of the logcat:
There's another error with
notifee.hideNotificationDrawer();but that's for another day(issue).Text file for your convienience
react-native infoSystem: OS: macOS 11.1 CPU: (6) x64 Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz Memory: 396.46 MB / 16.00 GB Shell: 5.8 - /bin/zsh Binaries: Node: 14.18.1 - ~/.nvm/versions/node/v14.18.1/bin/node Yarn: Not Found npm: 6.14.15 - ~/.nvm/versions/node/v14.18.1/bin/npm Watchman: 2021.11.15.00 - /usr/local/bin/watchman Managers: CocoaPods: 1.11.2 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: iOS 14.5, DriverKit 20.4, macOS 11.3, tvOS 14.5, watchOS 7.4 Android SDK: API Levels: 25, 28, 29, 30, 31 Build Tools: 28.0.3, 29.0.2, 30.0.2, 30.0.3, 31.0.0, 32.0.0 System Images: android-30 | Google APIs Intel x86 Atom, android-31 | ARM 64 v8a, android-31 | Intel x86 Atom_64, android-31 | Google APIs Intel x86 Atom_64 Android NDK: Not Found IDEs: Android Studio: 2020.3 AI-203.7717.56.2031.7784292 Xcode: 12.5.1/12E507 - /usr/bin/xcodebuild Languages: Java: 11.0.11 - /usr/bin/javac Python: 2.7.16 - /usr/bin/python npmPackages: @react-native-community/cli: Not Found react: 16.13.1 => 16.13.1 react-native: 0.63.2 => 0.63.2 react-native-macos: Not Found npmGlobalPackages: *react-native*: Not Foundpackage.json:{ "dependencies": { "@notifee/react-native": "^4.0.0", "@react-native-async-storage/async-storage": "^1.15.4", "@react-native-community/art": "^1.2.0", "@react-native-community/blur": "^3.6.0", "@react-native-community/clipboard": "^1.5.1", "@react-native-community/netinfo": "^6.0.0", "@react-native-firebase/app": "^13.0.1", "@react-native-firebase/crashlytics": "^13.0.1", "@react-native-firebase/messaging": "^13.0.1", "@react-native-masked-view/masked-view": "^0.2.6", "@react-navigation/native": "^5.1.5", "@twotalltotems/react-native-otp-input": "^1.3.11", "axios": "^0.19.2", "lodash": "^4.17.21", "react": "16.13.1", "react-native": "0.63.2", "react-native-drop-shadow": "^0.0.2",, "react-native-exit-app": "^1.1.0", "react-native-fast-image": "^8.3.4", "react-native-fs": "^2.17.0", "react-native-gesture-handler": "^1.5.0", "react-native-image-crop-picker": "^0.36.2", "react-native-keychain": "6.1.1", "react-native-linear-gradient": "^2.4.0", "react-native-modal": "^11.10.0", "react-native-paper": "^4.8.1", "react-native-permissions": "^3.0.3", "react-native-reanimated": "^2.1.0", "react-native-responsive-fontsize": "^0.5.0", "react-native-restart": "^0.0.22", "react-native-safe-area-context": "^0.7.3", "react-native-screens": "^2.10.1", "react-native-vector-icons": "^8.1.0", "react-native-version-info": "^1.1.0", "react-native-video": "^2.3.1", "react-navigation": "^4.4.4", "reanimated-bottom-sheet": "*", "rn-fetch-blob": "^0.12.0", "validate.js": "0.13.1" } }The text was updated successfully, but these errors were encountered: