Explicitly specify android:exported to activity-alias #870
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
android:exported should be explicitly specified to activity-alias element(just like activity, service and receiver) when the corresponding component has an intent filter defined. This will be enforced in the future version of AGP.
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.
📢 Type of change
📜 Description
Added android:exported attribute to the activity-alias element.
💡 Motivation and Context
android:exported should be explicitly specified to activity-alias element(just like activity, service and receiver) when the corresponding component has an intent filter defined. This will be enforced in the future version of AGP.
💚 How did you test it?
📝 Checklist
./gradlew spotlessApplybefore submitting the PR🔮 Next steps
📸 Screenshots / GIFs