Open daniel-waiguru opened 3 years ago
I am also getting the same error
Got a solution Create a file named error_frame_in.xml in your anim folder and add the following content.
<set xmlns:android="http://schemas.android.com/apk/res/android">
<alpha android:fromAlpha="0"
android:toAlpha="1"
android:duration= "400"
/>
</set>
I am also getting the same error. What do mean by "anim folder". Where should it be? I use this lib within a mobile app. Where should this xml be stored in this case?
I am also getting the same error. What do mean by "anim folder". Where should it be? I use this lib within a mobile app. Where should this xml be stored in this case?
the anim folder means animation folder, can be found in res-resource directory
I have no animation folder or something like that. Can the above XML entry be in any folder? For example I have a folder called XML in which I set general settings.
The animation folder is created when you create an animation file normally in anim folder is where all the animations files reside
when app publishes as release mode. inside the 'OptAnimationLoader' class> 'createAnimationFromXml' method> default case ' throw RuntimeException'. I just replace RuntimeException with a break. (library tries to dynamically choose the constructor).
when app publishes as release mode. inside the 'OptAnimationLoader' class> 'createAnimationFromXml' method> default case ' throw RuntimeException'. I just replace RuntimeException with a break. (library tries to dynamically choose the constructor).
Nice, but file is read only, how can you modify it?
when app publishes as release mode. inside the 'OptAnimationLoader' class> 'createAnimationFromXml' method> default case ' throw RuntimeException'. I just replace RuntimeException with a break. (library tries to dynamically choose the constructor).
Nice, but file is read only, how can you modify it?
I downloaded the source code then modified it
Getting this error after enabling obfuscation, here is a full stack trace
Tried adding the following rules to my
proguard-rules.pro
file but the error still persists