Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Attachment actions
Unintended behavior
View staffing
Description
Version used: 1.2.0
Devices/Android versions reproduced on: All
Sample project is attached.
With an instant-enabled base module (run configurations is added to the sample project) and an install-time dynamic feature module (full app) the initialization only runs with the full app and not the instant app. If the initialization provider is removed from the dynamic feature module then it works fine in the instant app.
Current behavior:
Full app - [correct] both initialization providers in the feature module and base module run
Instant app - [bug] the initialization provider in the base app module DOES NOT RUN
Expected behavior:
Full app - both initialization providers in the feature module and base module run
Instant app - the initialization provider in the base app module runs
Workaround: Remove the initialization provider from the feature module and just invoke a custom initialization function in the feature module through reflection (if present) from the base app modules initialization provider.