On Mon, Nov 30, 2015, at 10:53, 'Tor Norbye' via adt-dev wrote:
> The IDE and the app have a shared secret (baked into the app, and the IDE
> can look it up by consulting the build directory) that the IDE has to
> provide as part of the message protocol when supplying patches (code,
> resources). This isn't fully hooked up yet but will be soon.

OK.

> The easiest way is to to inspect the apk's manifest (e.g. via aapt dump
> xmltree) and see if it's pointing to the instant run bootstrap
> application:
> $ aapt dump xmltree ./app/build/outputs/apk/app-debug.apk
> AndroidManifest.xml | grep
> com.android.tools.fd.runtime.BootstrapApplication
>       A:
> android:name(0x01010003)="com.android.tools.fd.runtime.BootstrapApplication"
> (Raw: "com.android.tools.fd.runtime.BootstrapApplication")

Ah, that's easy enough.

> The Gradle plugin only injects this stuff for debug variants.

Oy. Since shipping debuggable builds is unfortunately "a thing", that's
definitely something distribution channels should validate.

Many thanks!

-- 
Mark Murphy (a Commons Guy)
https://commonsware.com | https://github.com/commonsguy
https://commonsware.com/blog | https://twitter.com/commonsguy

-- 
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.

Reply via email to