Skip to content
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

Update AndroidManifest.tmpl.xml #2538

Closed
wants to merge 1 commit into from
Closed

Update AndroidManifest.tmpl.xml #2538

wants to merge 1 commit into from

Conversation

drahba
Copy link
Contributor

@drahba drahba commented Jan 13, 2022

For the apps targeting api level 31 (A12) and contain activities, services, or broadcast receivers that use intent filters, you must explicitly declare the android:exported attribute for these app components. If an activity, service, or broadcast receiver uses intent filters and doesn't have an explicitly-declared value for android:exported, your app can't be installed on a device that runs Android 12 or higher. (https://developer.android.com/about/versions/12/behavior-changes-12). I added three changes accordingly with the requirements.

For the apps targeting api level 31 (A12) and contain activities, services, or broadcast receivers that use intent filters, you must explicitly declare the android:exported attribute for these app components. If an activity, service, or broadcast receiver uses intent filters and doesn't have an explicitly-declared value for android:exported, your app can't be installed on a device that runs Android 12 or higher. (https://developer.android.com/about/versions/12/behavior-changes-12). I added three changes accordingly with the requirements.
@HyTurtle
Copy link
Contributor

closes #2511

@misl6
Copy link
Member

misl6 commented Jan 13, 2022

Thank you @drahba!

We have some other bootstraps that use intent filters, how do you feel about taking care of them all?

See: https://github.com/kivy/python-for-android/tree/develop/pythonforandroid/bootstraps

@drahba
Copy link
Contributor Author

drahba commented Jan 15, 2022 via email

@Neizvestnyj
Copy link
Contributor

Today, with these changes, I have successfully collected 2 releases of the application and published them, everything works

@misl6
Copy link
Member

misl6 commented Jan 22, 2022

@drahba Can you mix PR #2543 #2542 #2541 and #2538 as a single one so we can have a single commit?

@misl6
Copy link
Member

misl6 commented Feb 5, 2022

@drahba Did you have the occasion to mix the 4 PRs (#2543 #2542 #2541 #2538)?
I would really like to merge your changes, but in order to not pollute the commit history is better to have one single commit for all these PRs 😄

@drahba
Copy link
Contributor Author

drahba commented Feb 5, 2022 via email

@misl6
Copy link
Member

misl6 commented Feb 6, 2022

No problem, take your time 😃

Seen the changes you made in the new PR.

Closing as: Superseded by #2551

@misl6 misl6 closed this Feb 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants