[3.2] Hardcode the export format for the editor 'run' feature #44639
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
m4gr3d
force-pushed
the
export_format_util_method_3_2
branch
from
5651211
to
ca3df5c
Compare
RandomShaper
approved these changes
Dec 26, 2020
m4gr3d
force-pushed
the
export_format_util_method_3_2
branch
from
ca3df5c
to
3ba1a8c
Compare
akien-mga
approved these changes
Dec 30, 2020
|
Thanks! |
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.
The
runfeature generates anapkfile that is automatically installed on the connected Android device. With the previous logic, switching the export format to Android app bundle (aab) for manual export would also negatively impact therunfeature: the logic would attempt to generate anaabfile instead of theapkfile needed by therunfeature hence causing an error.This PR resolves this issue by hardcoding the export format for the
runfeature.master PR