Closed Hoosein closed 7 years ago
Having this issue too. Anyone with any solutions? Thanks.
Same problem here. +1
Not sure, but it seems it happens on pre-Lollipop devices.
@Hoosein I think it isn't related with ProGuard. It's some bug in my library that occurred in your production app accidentally. (It can be happen without ProGuard)
Please update to version 1.0.5 to fix this problem.
Thank you for your feedback
I had the same problem with 1.0.4 after setting ProGuard. 1.0.5 didn't work with ProGuard either (except it didn't throw NullPointerException).
I fixed it by adding several lines in proguard-rules.pro file:
-keep class com.akexorcist.* { ; } -keep interface com.akexorcist.* { ; }
-keep class com.google.android.gms.maps.* { ; } -keep interface com.google.android.gms.maps.* { ; }
while proguard is true