refactor: use target SDK of built APK to determine best emulator #1267
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.
Motivation and Context
This reduces usage of
check_reqs.get_target
since that function only considersconfig.xml
to find the target SDK and moreover relies on the script location to findconfig.xml
(which has to change if we want to run the script from node_modules; also see #1265).Description
When looking for the best emulator image to run an APK on, the target SDK of that APK is determined by running
apkanalyzer manifest target-sdk
.apkanalyzer
is part of the Android SDK Tools since Revision 26.1.1 (September 2017).Testing
cordova run