Move optional ML features to dynamic feature modules is not possible
See original GitHub issueThe doc says that we could move ML to dynamic feature, but I think it will effect the whole firebase app modules because of ComponentDiscoveryService
.
All firebase modules depends on registering the extended ComponentRegistrar
classes so that FirebaseApp
init will discover them via AndroidManifest
once. This flow will cause firebase components can’t move to dynamic feature while base module has other components.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Overview of Play Feature Delivery | Android Developers
What not to include in the feature module build configuration ... Under Dynamic features to deploy in the General tab, check the box...
Read more >Reduce the size of your ML Kit Android app's APKs
Build your app as an Android App Bundle; Advanced: Move optional ML features to dynamic feature modules; Advanced: Exclude unused ML Kit binaries....
Read more >Dynamic feature modules. Is it worth the effort? - Medium
Code from dynamic modules is not directly accessible to the base module. This brings in the need of Reflection class, which is still...
Read more >Dynamic module feature and ML Kit Crash on App open
To set up your dynamic module, you will need to move the mlkit translate dependency from the base app's gradle file to the...
Read more >Modules - Retool Docs
A module is a reusable group of components and queries. You might use a module to reuse common components in multiple apps or...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@ashwinraghav LGTM, please let me in. I’m also in the firebase alpha group.
Thanks for raising this. Your observations are correct. This requires some ground up redesign of component discovery. The good news is that we are working on a fix. Please let us know if you would like to try the alpha and we’ll give you an early release candidate.