Open jeudi93 opened 8 months ago
I think you may need to seek help from Allatori as we're not familiar with that obfuscator. Also, right now, we only really support usage with R8 and Proguard. Note that we do package in some configuration for those where needed (like with @HiltViewModel
), so please be aware that if Allatori doesn't read that configuration you'll need to replicate those rules for Allatori yourself too.
@Chang-Eric I already checked with Allatori side and they told me to keep all dagger-hilt generated classes from obfuscation. The problem is, I am struggling to find out what classes were auto generated. Could you possibly guide me how to find out all those classes so that I will be able to keep it from obfuscation?
Er, this is an odd request as that really isn't necessary for other obfuscators like R8 and Proguard since generated classes should be treated the same as user written classes. The main way to find all of them though would be to find the classes we put the @Generated
annotation on, but that is source retention so I don't know if you'll be able to use that.
I resolved the same issue by adding 'hilt { enableAggregatingTask = false }' to build.gradle."
My project does not apply Proguard obfuscation, but uses the paid obfuscation library 'allatori'. https://allatori.com/
When obfuscation is applied using the 'allatori' library, a crash error occurs saying that the Application Class cannot be found as shown below.
When applying obfuscation other than Proguard, Could you share the configuration that need to be set or keep the auto generated classes from the obfuscation?
My Project Dagger-Hilt Dependencies . implementation("com.google.dagger:hilt-android:2.48") kapt("com.google.dagger:hilt-android-compiler:2.48")