We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We had a problem that kit activated broadcast (MParticle.ServiceProviders.BROADCAST_ACTIVE_xx) were not received on devices on Android 14.
It turns out that our registered receiver used recommended flag Context.RECEIVER_NOT_EXPORTED and that requires package set on intent.
Context.RECEIVER_NOT_EXPORTED
Here sdk code from v5.55.2
v5.55.2
mparticle-android-sdk/android-kit-base/src/main/java/com/mparticle/kits/KitManagerImpl.java
Lines 319 to 320 in 9b5068e
We suggest change like:
Intent intent = new Intent(MParticle.ServiceProviders.BROADCAST_ACTIVE + activeKit.getConfiguration().getKitId()); if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.UPSIDE_DOWN_CAKE) { intent.setPackage(getContext().getPackageName()) } getContext().sendBroadcast(intent);
See external tracked issue here: https://issuetracker.google.com/issues/293487554#comment14 and stackoverflow: https://stackoverflow.com/a/76920719
The text was updated successfully, but these errors were encountered:
No branches or pull requests
We had a problem that kit activated broadcast (MParticle.ServiceProviders.BROADCAST_ACTIVE_xx) were not received on devices on Android 14.
It turns out that our registered receiver used recommended flag
Context.RECEIVER_NOT_EXPORTED
and that requires package set on intent.Here sdk code from
v5.55.2
mparticle-android-sdk/android-kit-base/src/main/java/com/mparticle/kits/KitManagerImpl.java
Lines 319 to 320 in 9b5068e
We suggest change like:
See external tracked issue here: https://issuetracker.google.com/issues/293487554#comment14
and stackoverflow: https://stackoverflow.com/a/76920719
The text was updated successfully, but these errors were encountered: