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

Document the fact that `run` does both `debug` and `release` #100

Open
stanch opened this Issue Sep 9, 2014 · 2 comments

Comments

Projects
None yet
4 participants
@stanch

stanch commented Sep 9, 2014

It seems that android:run chooses between a debug build and a release build, depending on which of (android:package-debug, android:package-release) was the most recent. In particular, it does a debug build by default, however it switches to a release build after I run android:package-release. I think this is not obvious and could be documented for two reasons:

  • For people who want to know how to launch a release build and have no idea, how
  • For people who get FAILED_INCONSISTENT_CERTIFICATES after ;android:package-release;...;...;run and have no idea, why
@aafa

This comment has been minimized.

Show comment
Hide comment
@aafa

aafa Nov 4, 2015

Contributor

👍 That's very confusing behavior. I think run should always do debug builds unless explicitly specified that release build is needed.

To introduce runLast to run recent package -- is an option.

Contributor

aafa commented Nov 4, 2015

👍 That's very confusing behavior. I think run should always do debug builds unless explicitly specified that release build is needed.

To introduce runLast to run recent package -- is an option.

@pfn pfn added the FAQ label Nov 26, 2015

@DavidPerezIngeniero

This comment has been minimized.

Show comment
Hide comment
@DavidPerezIngeniero

DavidPerezIngeniero Jan 26, 2016

+1 for aafa proposal.

DavidPerezIngeniero commented Jan 26, 2016

+1 for aafa proposal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment