On a related topic -
I'm maintaining a Gradle plugin that works with generated .dex files,
running on the output of 'assemble${flavor}'. I'd like to be able to
access all included .dex files, in a stable way. Right now I just expand
'instant-run.zip', but as you say this is officially undocumented and
subject to change. Are there any plans to nail down a canonical package
format?
On Friday, April 8, 2016 at 1:47:01 PM UTC-7, Jerome Dochez wrote:
>
> from within the app it's difficult although you could check for the
> presence of the $change field that we add on every instrumented class (not
> an official API, can change anytime). Also the structure of the APK is very
> different. Right now the presence of an instant-run.zip at the root of the
> APK is indicative that's an InstantRun enabled APK but again that's can
> change in the future.
>
> On Fri, Apr 8, 2016 at 11:32 AM thierryd <thie...@gmail.com <javascript:>>
> wrote:
>
>> Is there a way to know if we are running an Instant Run build inside our
>> App? i.e. programatically?
>>
>> Sometimes we give to our QA debug builds made with Android Studio. But I
>> want to make sure that official QA builds are not done using Android
>> Studio. It would be great if I could detect this scenario and show some
>> sort of warning message if we are in an Instant Run build.
>>
>> --
>> 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 adt-dev+u...@googlegroups.com <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
--
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 adt-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
