-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Android 14] Crash One of RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED #52
Comments
@baveku That error come from targeting Android 34. When registering a receiver on Android 34, we must specify either the RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED flag; in this case, the RECEIVER_EXPORTED flag is required. You can use the patch-package to fix that error here |
hmm I try but it doesn't work. |
I'm still in the process of upgrading the target to 34. It involves more changes. Can you use this fork while waiting for new version? |
thanks, I will try. |
The v1.0.0 has just been released. I will close this issue. Please open a new issue if you have any other concerns |
Nice job 👍 |
Unable to start service com.reactnativefullscreennotificationincomingcall.IncomingCallService@3654304 with Intent { act=ACTION_SHOW_INCOMING_CALL com.reactnativefullscreennotificationincomingcall.IncomingCallService (has extras) }: java.lang.SecurityException: com.bitu.user.staging: One of RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED should be specified when a receiver isn't being registered exclusively for system broadcasts
How can we fix it on Android 14?
The text was updated successfully, but these errors were encountered: