Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resources from dynamic feature modules are not available immediately after install #365

Open
nitinsethi86 opened this issue Jun 20, 2024 · 0 comments

Comments

@nitinsethi86
Copy link

Describe the bug
When using --local-testing flag, accessing a dynamic feature modules just after install crashes the app with FileNotFoundException.

The same flow works in the release variant of the app.

Bundletool version(s) affected
Version: [1.16.0]

Stacktrace
Unable to load Texture registryId='android.resource://com.microsoft.skype.teams.dev/drawable/com.microsoft.skype.teams.dev.remoteassist%3Asceneform_plane'
java.util.concurrent.CompletionException: java.lang.IllegalStateException: java.io.FileNotFoundException: No resource found for: android.resource://com.microsoft.skype.teams.dev/drawable/com.microsoft.skype.teams.dev.remoteassist%3Asceneform_plane

To Reproduce

  1. Build a bundle.
  2. Generate APKs using --local-testing.
  3. Download a DFM on-demand and launch on install.
  4. App crashes with FileNotFoundException. The resource file is present in the DFM installed.

One unique setup is that we attach a Fragment from DFM in an existing Activity (present in base APK). Is this setup supported by local-testing?

Expected behavior
The launch of on-demand installed DFM locally should be successful without crash.

Known workaround
Ignore the crash and launch the second time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant