feat(android)!: Remove AVD creation on --list #349
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
jcesarmobile
requested review from
markemer,
theproducer,
ItsChaceD,
dallastjames,
IT-MikeS and
giralte-ionic
giralte-ionic
approved these changes
Oct 24, 2023
IT-MikeS
approved these changes
Oct 24, 2023
github-actions bot
pushed a commit
that referenced
this pull request
Oct 26, 2023
# [2.0.0](v1.7.4...v2.0.0) (2023-10-26) ### Bug Fixes * typo in android variable logs ([#318](#318)) ([3d9251f](3d9251f)) * chore!: support only node 16+ (#354) ([eb20983](eb20983)), closes [#354](#354) * feat(android)!: Remove AVD creation on list (#349) ([2a310ff](2a310ff)), closes [#349](#349) ### BREAKING CHANGES * drop node 10-14 support * removal of AVD creation feature
|
🎉 This PR is included in version 2.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
BREAKING CHANGE: removal of AVD creation feature
native-run android --listcreates a new AVD for the installed SDK, even if there are AVDs already, and if the users have a SDK installed that native-run doesn't support yet it throwsERR_UNSUPPORTED_API_LEVEL. Which is a yearly problem since Android Studio installs latest SDK despite it's still beta and we don't support it until it's final around 6 months later.By removing the AVD creation native-run logic simplifies and reduces maintenance burden of adding support every year and it won't be an issue for users installing unsupported SDKs.
closes #334
closes #332
closes #322
closes #321
closes #303
closes #257