android-instant-apps

问题 We are preparing to publish instant app apks to play store via "Instant app development" channel for testing purpose. When we sign instant app (using same keystore used for Installed App), only geting one feature module apk inside zip folder(instant-release.zip) which giving error while uploading to Play Store by complaining "Your Instant App APKs should contain at least one base APK" Anyway we able to see the expected structure under instant-debug version Structure deference between debug

问题 I am working with multi feature android application with instant app and wear app.Here i am able to successfully run my application but getting following error during building APK or rebuild projects . java.lang.IllegalStateException: Expected configuration ':module1:debugFeatureCompileClasspath' to contain exactly one file, however, it contains 2 files. at org.gradle.api.internal.file.AbstractFileCollection.getSingleFile(AbstractFileCollection.java:62) at com.android.build.gradle.tasks

问题 I'm currently experimenting with InstantApps and would like to include dagger into my project. I'm facing an issue setting up an application AppComponent. My application component includes all the feature dagger modules of my app. I basically have: One Base app module containing my Application class Multiple features with each a dagger Module per Activity, all with Base as a dependency. One app module and instant module both importing all the features and the base app module. I'm trying to

问题 Fairly straight forward question. Does anyone happen to know if Google Play App Signing supports Instant Apps? The reason I ask: Enter your app’s signing config, or select a keystore file. While it’s possible to use a debug config or keystore during testing, the generated Digital Asset Links file won’t be compatible with the release version of your app. If you do upload a Digital Asset Links file that uses a debug config or keystore, then before publishing your app you’ll need to generate and

问题 I have set up an app as an instant app based on this guides: https://codelabs.developers.google.com/codelabs/android-instant-apps/index.html?index=..%2F..index#6 and https://developer.android.com/topic/google-play-instant/getting-started/feature-plugin So I have now 2 modules (installed & instant). If I try to create an app bundle, then I'm not able to select the instant module, because the module selection is disabled in my case. Running of the instant app is working as expected. Is it even

问题 I created an app which picks up images from images folder in emulator and displays selected image in my layout of application. When I converted my app to instant app, the same code that picks up images from image folder throws exception. I used runtime permissions READ_EXTERNAL_STORAGE. My code: private static final int PICK_IMAGE_REQUEST = 234; Intent intent = new Intent(); intent.setType("*/*"); intent.setAction(Intent.ACTION_GET_CONTENT); startActivityForResult(intent, PICK_IMAGE_REQUEST);

问题 Android recently came out with a new com.android.feature plugin to be used to split up applications into features for the new Instant apps. It seems to be an architecture they are recommending in general, not just for features you are splitting up for instant apps. You can do some reading about it's usage here. What I'm failing to understand is what this plugin actually does better / differently than the normal android-library plugin. I ask, because my team is legitimately considering

问题 Android recently came out with a new com.android.feature plugin to be used to split up applications into features for the new Instant apps. It seems to be an architecture they are recommending in general, not just for features you are splitting up for instant apps. You can do some reading about it's usage here. What I'm failing to understand is what this plugin actually does better / differently than the normal android-library plugin. I ask, because my team is legitimately considering

问题 Android recently came out with a new com.android.feature plugin to be used to split up applications into features for the new Instant apps. It seems to be an architecture they are recommending in general, not just for features you are splitting up for instant apps. You can do some reading about it's usage here. What I'm failing to understand is what this plugin actually does better / differently than the normal android-library plugin. I ask, because my team is legitimately considering

问题 From the developer document of Instant Apps Installed apps can make themselves available to interact with instant through explicit intents. And later, it is mentioned that instant apps cannot Discover the list of installed apps on the device, unless the installed apps have made themselves discoverable to instant apps . But I can't find the details about how to expose the component of an installed app or any part of an app, for that matter, to be visible (and accessible) by instant app. And