The install task should already print the devices on which it installs the app or the one it skips. It may only be displayed with --info though.
I do want to have it fail when the app ends up not being installed anywhere. I've filed https://code.google.com/p/android/issues/detail?id=76726 to track it. On Fri, Sep 26, 2014 at 3:51 AM, Tom Billiet <[email protected]> wrote: > Ok, we'll update our scripts. > Why we do is because we have a generic android script where we do all this > logic. Now the user of that script will have to set the variable we use to > compute the versioncode before they include the generic android script. > With our current implementation the place where the variable was defined > was not relevant, hence a bit more user-friendly. > > About the installDebug task not reporting errors. Any chance that's going > to change again? > > > Op vrijdag 26 september 2014 01:23:45 UTC+2 schreef Xavier Ducrohet: >> >> This is really not going to work. The handling of the versionCode is now >> more complicated because of the split handling which can override the >> versionCode. >> >> You should really do this before the afterEvaluate. Any reason you can't >> do it then? >> >> On Wed, Sep 24, 2014 at 7:43 AM, Tom Billiet <[email protected]> wrote: >> >>> I've noticed behavior that changed when upstepping from 0.12.2 to >>> 0.13.0/0.13.1 which is quite inconvinient: >>> >>> 1. It's not possible to configure the versionCode property anymore in >>> afterEvaluate. It get's ignored if you do so. We have some generic android >>> script where the versioncode is auto-generated based on a version variable, >>> but it has to be done in afterEvaluate in order to configure that variable: >>> android { >>> defaultConfig { >>> afterEvaluate { >>> versionCode = some_calculated_value //this value is not used in >>> the merged manifest >>> } >>> } >>> } >>> >>> 2. If the installDebug task fails (which we had as android says it's a >>> downgrade because of the issue above), there's no indication printed. I >>> believe it really makes sense to print at least something (or even have the >>> job fail) if the installation fails. It took me a while to figure out why >>> my code did not work while it just did not install. >>> >>> Tom >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "adt-dev" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Xavier Ducrohet >> Android SDK Tech Lead >> Google Inc. >> http://developer.android.com | http://tools.android.com >> >> Please do not send me questions directly. Thanks! >> > -- > You received this message because you are subscribed to the Google Groups > "adt-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Xavier Ducrohet Android SDK Tech Lead Google Inc. http://developer.android.com | http://tools.android.com Please do not send me questions directly. Thanks! -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
