How would you access a Hilt dependency in a non-injectable ContentProvider?
Tests Hilt's escape hatch for framework classes. Strong answer: define an EntryPoint in SingletonComponent, expose the dependency, and retrieve it with EntryPointAccessors.fromApplication. Red flag: field injection or manual static singletons.
Tests your understanding of Hilt's static entry point API for framework classes outside Hilt's graph. A strong answer defines an EntryPoint interface with InstallIn SingletonComponent, exposes SettingsManager as a method, and retrieves it in ContentProvider onCreate via EntryPointAccessors.fromApplication with the Application context. Red flags include field injection in the ContentProvider, using an Activity context instead of Application, or falling back to manual static singletons which bypass Hilt's scoping and testability.
Read the original → developer.android.com
- #android
- #hilt
- #dependency-injection
- #contentprovider
- #entrypoint
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.