Fix installing on Android 12 #123
Merged
Conversation
This file contains hidden or 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
TheLastProject
changed the title
|
Hi! Thanks for the PR! The strange thing is that the version on the playstore that is built from the same source can be installed without problems on android 12. In any case, I'll keep an eye on the release notes in the future 😅 |
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.
Hey there,
I noticed your F-Droid forum thread: https://forum.f-droid.org/t/problem-building-app-for-android-12/16158
After looking at andrewc's reply I decided to see what your AndroidManifest.xml looks like and it seems you don't have any exporting info: https://developer.android.com/about/versions/12/behavior-changes-12#exported
For future reference, always make sure to read the release notes and test your app (in an emulator for example) on the newest Android versions, especially if you update targetSdk (because that means you're telling Android your app is ready for new behavioural changes), so you can prevent such surprises in the future :)
Note that I haven't tested it, as I don't currently have all the stuff setup to build Flutter apps. So I'd suggest trying this patch, building a new .apk and testing it in an Android 12 emulator or asking @mondlicht-und-sterne to test it for you :)