Fixed
Status Update
Comments
yb...@google.com <yb...@google.com>
se...@google.com <se...@google.com> #2
I should probably elaborate on that a bit more here :P. The ideal case would be that data classes written in other modules work the same when consumed. A standard data class (no secondary constructors, `val` properties) works fine when in the same module. The errors produced are also pretty confusing. They'll usually give what they read from the bytecode (constructor params called "var0" or the like) and reports missing setters for fields without names of said fields.
Description
Version used: 1.0.0-alpha1
Devices/Android versions reproduced on: any
If I obfuscate the code with proguard using "-repackageclasses ''" option, i.e. moving all obfuscated classes to root package the app crashes trying to get GenericLifecycleObserver constructor with NullPointerException because getPackage() returns null for root package.
Please add null check.
Deobfuscated stacktrace is attached.
Test case:
Compile release version of BasicSample from proguard_npe branch