fix: use RECEIVER_NOT_EXPORTED on SDK 33 and up #663
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@gotev can this be merged and released by any chance? Currently, using this library and targeting SDK 34 crashes apps. Thank you! |
gotev
approved these changes
Oct 10, 2024
PavlosTze
approved these changes
Nov 7, 2024
|
Hello @gotev , we plan to use your library but having crashes on SDK 33 devices is a no-go currently. Can you please merge this fix and release a new version including this? Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This API was introduced in SDK 33, but wasn't required until you targeted SDK 34. Once you target SDK 34, running the app on a 33 device will trigger an error stating this is required.