Update android export page for AAB requirement #9637
Merged
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
skyace65
added
enhancement
area:manual
Calinou
reviewed
Aug 2, 2024
Comment on lines
146
to
151
| By default, the AAB or APK will contain native libraries for both ARMv7 and ARMv8 | ||
| architectures. This increases its size significantly. To create a smaller file, | ||
| uncheck either **Armeabi-v 7a** or **Arm 64 -v 8a** in your project's Android | ||
| export preset. This will create an APK that only contains a library for | ||
| export preset. This will create an file that only contains a library for | ||
| a single architecture. Note that applications targeting ARMv7 can also run on | ||
| ARMv8 devices, but the opposite is not true. |
There was a problem hiding this comment.
With AAB, the practice of including fewer architectures to reduce download size is obsolete. Google automatically splits up the AAB on their backend so the user only downloads the architecture they need.
Also, 64-bit ARM Android devices may no longer be able to run 32-bit ARM code at some point in the future (in fact, I've heard this was the case for Android 14 or later, or Android 15 or later).
|
I've updated that section to state that you don't need to make multiple AABs, and added an explanation at the end of the paragraph. |
mhilbrunner
reviewed
Nov 17, 2024
mhilbrunner
reviewed
Nov 17, 2024
mhilbrunner
approved these changes
Nov 17, 2024
|
Thanks! |
mhilbrunner
added a commit
that referenced
this pull request
Nov 30, 2024
* Update android export page for AAB requirement --------- Co-authored-by: Max Hilbrunner <[email protected]>
|
Cherrypicked to 4.3 in #10347. |
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.
Does what the title says. Since august of 2021 all new apps uploaded to Google Play must be in AAB format, that requirement is noted on the top of this page in the Android documentation.
I've added a sentence on that requirement and re-worded a few things. I've also removed the section on multiple APK signing, that's obsolete with the AAB format. And I figure anyone still uploading APKs because their app was grandfathered in should know how to do that already if they don't want to switch to AABs for some reason.
Closes #9134.