Fixed
Status Update
Comments
da...@google.com <da...@google.com> #2
+1, this is a severe bug if I've ever seen one. If it is on par with the #74139250 (https://issuetracker.google.com/issues/74139250 ), this should be at least P1
ap...@google.com <ap...@google.com> #3
1) Thank you for reporting this issue.We were not able to reproduce the issue with the information provided here.
Logs after follow mentioned steps in comment #1
===============================================
V/TAG: ViewModelFirst Created
2) Can you please provide the below requested information to better understand the issue:
Android build
Which Android build are you using? (e.g. KVT49L)
Device used
Which device did you use to reproduce this issue?
Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
Logs after follow mentioned steps in
===============================================
V/TAG: ViewModelFirst Created
2) Can you please provide the below requested information to better understand the issue:
Android build
Which Android build are you using? (e.g. KVT49L)
Device used
Which device did you use to reproduce this issue?
Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
Description
Component used: Fragment Version used: Devices/Android versions reproduced on:
When using Hilt Jetpack integration, the Hilt Work factory failed to create Worker with the following exception:
It appears this is due to a but in the class name mapping.
I declared my worker inside a Kotlin object like this:
Which create a
com.example.webservices.Device.Worker
entry in the Worker Factory mapping. But this entry do not match the real runtime class name which iscom.example.webservices.Device$Worker