-
Notifications
You must be signed in to change notification settings - Fork 429
ProGuard with Conceal v.2 #182
Comments
Hey @2x2xplz , thanks for the heads-up. Very helpful. I have been battling with the crash. As you suggested, including the code below in the proguard fixed it.
|
I am experiencing this problem as well. The working solution suggested by @2x2xplz is not optimal, because it effectively turns off ProGuard for the vast majority of classes in this library. |
I will review the ProGuard definitions. The projects I work with use the same code but different build and proguard definitions. I must have missed something probably from the fbjni library. |
Hey @2x2xplz , Thanks for the solutions..
|
Bump. Current proguard-annotations file is not sufficient for proguard to work. |
proguard-annotations is still not updated |
Still true as of 2.0.2. An update would be appreciated :) |
New Android project using Conceal 2.0.1 and I'm having some issues with the previous ProGuard suggestions. Conceal works fine in debug builds but not with ProGuard. I'm using Android Studio 3.0 beta 7, and testing on a device running Android 5.1.
I did eventually find settings that prevented crashes (see below) but my concern is, on other devices running other Android versions (4, or 6+), will my settings be sufficient?
As per the documentation, I include
SoLoader.init(this, false)
in Application.onCreate()Finally after much trial and error I was finally able to prevent the app from crashing when I call
crypto.isAvailable()
by adding these lines to my ProGuard config:The first 2 lines are necessary to prevent this error:
And the third line is required to prevent this error:
Using
-keepnames
for any of the 3 will not prevent the crashes-keep class com.facebook.** { *; }
is an alternative that will work, but the entirety of this package will go un-minified.I'm no ProGuard expert so I'm unsure if my setup is optimal, any input from the project maintainers would be great, especially settings that are known to work on a wide variety of Android devices.
The text was updated successfully, but these errors were encountered: