-
Notifications
You must be signed in to change notification settings - Fork 24.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
react-native run-android no longer supports --configuration=release #12698
Comments
Shall we update the official tutorial as well? it still contains outdated info here: |
@laalaguer I fixed this in #12699 but it seems that the doc has not been released yet. Let's close this when the updated version is released. |
@sungwoncho not updated in 0.43 :/ |
Just tripped over this too. Would be great to update it |
@janicduplessis #12699 was merged but doc has not been updated. Any action required to ship the updated docs? |
Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally! If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:
If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution. |
Description
Documentation for Testing the release build of your app for Android seems to be outdated.
Concretely, the flag
--configuration
does not exist anymore.Reproduction
Running
react-native run-android --configuration=release
gives me:Solution
Replacing
configuration
flag withvariant
flag works.Additional Information
The text was updated successfully, but these errors were encountered: