New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dialog animation for pre-Lollipop (Android 4.3) #10
Comments
Hi! |
Sorry, can't reproduce at my 4.3 device. It works.
|
Do you use proguard ? Can you reproduce this issue on emulator/genymotion? |
Yes I use proguard. Funny thing is that your library works on genymotion, but I have issue on real device. |
I saw somewhere in logs which might be related with issue : Could not find method android.widget.FrameLayout., referenced from method dmax.dialog.ProgressLayout.. I have debugged app and I suppose that compilation agains Android 23 is too much, because some method is missing. |
Well, first, try to add these lines into you caustom proguard config file to avoid any shrinks:
Next, can you add here whole stack-trace? |
Try to use verison build with build tools 22
It will be available in 2-3 hours |
Hi, Lukasz! How is it going with this problem? |
I was not be able to fix it and unfortunately I used standard android's ProgressDialog. Thanks for help, but it was force majeure. Thanks for your help! |
Okay, I see. Tell me please one more thing. Did you try this 6-bt22 version? |
I remember that I was trying but without success. |
Okay. Thanks |
I have same issue in 4.4.3 nexus. edited) |
Finally I found a solution. Change public class (HesitateInterpolator, AnimatorPlayer, AnimatedView) or Keep these three class in proguard rule. Thanks! |
Hi, |
Hi,
I am using your library in Android app which is compiled to Android SDK version 23. I am running this app on Android 4.3. As far I can see the title of dialog, but I cannot see the animation composed from dots. My style.xml configuration looks like this one :
Could you give me some additional guidance how fix this issue ? Thanks in advance!
The text was updated successfully, but these errors were encountered: