android-instant-apps

问题 UPDATE: 20170703 Using Android Studio 3.0 Canary 5 Modified some AndroidManifest and build.gradle files, Moved from inside to inside for both Base's AndroidManifest and App's AndroidManifest, like below: <application ...> <meta-data android:name="asset_statements" android:resource="@string/asset_statements" /> <activity ...> </application> resource asset_statements: <string name="asset_statements">[{\n \"relation\": [\"delegate_permission/common.handle_all_urls\"],\n \"target\": {\n \

问题 I am trying to create a demo instant app which was demonstrated at Google IO 2017. I see, this needs Android Studio 3.0 and latest build tools and only few devices are white-listed to use this newly introduced concept. Here, you can see that I have created an avd machine named Nexus 5X , I captured details of created machine, here you can see: Name: Nexus_5X_API_25 CPU/ABI: Google APIs Intel Atom (x86) Path: C:\Users\williams\.android\avd\Nexus_5X_API_25.avd Target: google_apis [Google APIs]

问题 Unable to use foreground service inside InstantApp feature module. Getting below runtime security exception. java.lang.RuntimeException: Unable to start activity ComponentInfo{ . .XYZActivity}: java.lang.SecurityException: Method class android.app.ActivityManagerProxy.getServices not available to instant apps Android document says, Restricted features: Run on the device without users being aware. Foreground services are available. Instant apps can only be started through activities that

问题 In an Instant App feature module, I'm importing an aar (using "api" statement from a maven repository) which contains an activity declaration in its manifest and a "style" resource used in this declaration. The resulting manifest merging fails because the style resource is not found in the base feature project. It seems resources from imported aar in features modules are not included in the base feature module. Since the plugin is still in alpha mode I'm not sure if I'm doing something wrong,

问题 I recently upgraded to the gradle-3.0.0-alpha8 after which some styles are not resolved at compile time. Develop envirment: IDE: Android studio 3.0 Bate3 Gradle build tools : 'com.android.tools.build:gradle:3.0.0-beta3' Gradle :gradle-4.1-all.zip Error info: Error:(94, 5) style attribute '@android:attr/windowExitAnimation' not found Error:(94, 5) style attribute '@android:attr/windowEnterAnimation' not found Setting android.enableAapt2=false in gradle.properties file can solve this isuue. But

问题 When developing for Instant Apps the use of Configuration APKs (https://developer.android.com/topic/instant-apps/guides/config-splits.html) offers useful option for cutting down on APK size. However it looks like they are only supported when using mindSdk of 21 or later. For example, you get following error if you try to use this capability for lower sdk versions. MinSdkVersion 17 is too low (<21) to support pure splits, reverting to full APKs Is there way to have base module for example use

问题 my android project min sdk level is 16. I want to turn it into instant app but I need to maintain min sdk level but instant app supports min 23. I tried to set different api levels for the installable and instant app in the same project and tried to override them but I wasn't able to do. So is there any way to work in same project with installable app and instant app with different min sdk levels? 回答1: Another way to do this so that the instant app APKs have the desired minSdkVersion is with

问题 Unable to use Android Emulator, for testing the Instant Apps!! Every-time I'm getting "Side loading instant app failed: Reading bundle timed out." I'm using, Android Studio 3.0 Canary-5 Emulator : Nexus 5X image running Android 6.0 (API level 23), x86, with Google APIs. Google APIs Intel x86 Atom System Image (Revision 21) Note: After updating Android Studio 3.0 (Canary-4 > Canary-5) & Emulator system image from revision (20 > 21) . I'm unable to run the instant App through emulator. Always I

问题 I am using Gradle 4.4 with Gradle-Android plugin 3.1.1 on Android Studio 3.1.1. I have 2 flavors 'a' and 'b' and I am unable to build my project due to the following error: Cannot choose between the following configurations of project :app: - aDebugMetadataElements - bDebugMetadataElements All of them match the consumer attributes: - Configuration 'aDebugMetadataElements': - Required com.android.build.api.attributes.BuildTypeAttr 'debug' and found compatible value 'debug'. - Found com.android

问题 I am using Gradle 4.4 with Gradle-Android plugin 3.1.1 on Android Studio 3.1.1. I have 2 flavors 'a' and 'b' and I am unable to build my project due to the following error: Cannot choose between the following configurations of project :app: - aDebugMetadataElements - bDebugMetadataElements All of them match the consumer attributes: - Configuration 'aDebugMetadataElements': - Required com.android.build.api.attributes.BuildTypeAttr 'debug' and found compatible value 'debug'. - Found com.android