Open ChrisJan00 opened 3 years ago
Another way
-keep class io.reactivex.** {*;}
-keep class com.unsplash.pickerandroid.photopicker.** { *; }
-keep class io.reactivex.** {*;}
This proguard rules doesn't work on latest android project.
I will have to create my own unsplash picker just because of no proper consumer proguard rules
added to this library.
-keep class com.unsplash.pickerandroid.photopicker.** { *; } -keep class io.reactivex.** {*;}
This proguard rules doesn't work on latest android project. I will have to create my own unsplash picker just because of no proper
consumer proguard rules
added to this library.
There are new magical incantations to add to the proguard file, in addition to the known two lines:
-keep,allowobfuscation,allowshrinking class kotlin.coroutines.Continuation
-keep,allowobfuscation,allowshrinking interface retrofit2.Call
-keep,allowobfuscation,allowshrinking class retrofit2.Response
I hope this fixes your issue @MitulVarmora
-keep class com.unsplash.pickerandroid.photopicker.** { *; } -keep class io.reactivex.** {*;}
This proguard rules doesn't work on latest android project. I will have to create my own unsplash picker just because of no proper
consumer proguard rules
added to this library.There are new magical incantations to add to the proguard file, in addition to the known two lines:
-keep,allowobfuscation,allowshrinking class kotlin.coroutines.Continuation -keep,allowobfuscation,allowshrinking interface retrofit2.Call -keep,allowobfuscation,allowshrinking class retrofit2.Response
Great, Thanks. It worked.
Describe the bug A project using this component crashes in Release mode when launching the picker. The problem does not happen in Debug mode.
To Reproduce Steps to reproduce the behavior:
Expected behavior The picker activity is open and the user can navigate through a stacked grid view of photos from the unsplash website.
Observed behavior The app crashes.
Additional context Stacktrace from Logcat:
Solution I fixed the issue by adding the following line to my project's proguard-rules.pro file:
The problem is fixed this way on my side. I thought I'd be nice to report it, for other users. Imho this or an equivalent addition to the proguard rules should be mentioned in the README file. Or, if that's reasonable, directly applied to the relevant files in this repository.