Closed jarnove closed 5 months ago
Hi @jarnove,
This report is somewhat conflicting.
Commenting out launch()
would only have an impact on the second crash/screenshot you shared, as it would prevent that code from running.
This first crash you shared takes place during the native app's initialisation process. It runs far before reaching your launch()
invocation.
Both crashes seem to be related to code minification. The crashes should be consistent regardless of upgrading or doing a clean install.
We're trying to reproduce what you described, so far to no avail.
It would help if you could share your build.gradle
files. It may provide additional insight.
It would also definitely help if you could provide us with a minimal app that exhibits this problem.
Hmm think I found a link.
Saw this configuration in my app/ build.gradle.
configurations.all {
resolutionStrategy.force ‘androidx.work:work-runtime:2.7.1’ // Notifee depends on 2.8.0 but Notificare depends on 2.7.1
}
Updated this to 2.9.0 and now it's working as expected. But it's not clear to me if I still need this?
Notificare 3.8.0 uses version 2.9.0 of the AndroidX Work Manager. To answer your question, you may not need the resolution strategy if Notifee updated its dependencies and no longer has a conflict. You can remove the resolution strategy and verify which version of the work manager is resolved for your application.
Is there an existing issue for this?
Describe the bug
After updating from RN 0.72.9 to 0.73.6 and overwriting the build with the newer version the app keeps crashing on Android. This happens in both debug and client builds.
It crashes when "Notificare.launch();" is called. If I put this in comment, no crash happens. Starting from a clean sheet and clean install a build, no crash happens.
Errors in debug build:
Errors in client (/enterprise) build:
Any idea?
Steps to reproduce
Expected behaviour
No crash should happen.
Relevant log output
Library version
3.8.0
Operating system
Android 14
React Native version
0.73.6
Smartphone model
No response
Additional context
No response