The conversionwasn't difficult at all for me. There's only one solution: convert your object animators to tween animations. It won't give you a compiler error because they're both referenced by resource id. The reason is that setCustomAnimations() in vanilla use object animators, whereas setCustomAnimations() in the support package use tween animations. : Unknown animation name: objectAnimatorĪt .createAnimationFromXml(AnimationUtils.java:124)Īt .createAnimationFromXml(AnimationUtils.java:91)Īt .loadAnimation(AnimationUtils.java:72)Īt 4.(FragmentManager.java:710)Īt 4.(FragmentManager.java:876)Īt 4.(FragmentManager.java:1080)Īt 4.(BackStackRecord.java:622)Īt 4.(FragmentManager.java:1416)Īt 4.app.FragmentManagerImpl$1.run(FragmentManager.java:420)Īt android.os.Handler.handleCallback(Handler.java:587)Īt android.os.Handler.dispatchMessage(Handler.java:92)Īt android.os.Looper.loop(Looper.java:132)Īt (ActivityThread.java:4123)Īt .invokeNative(Native Method)Īt .invoke(Method.java:491)Īt .ZygoteInit$n(ZygoteInit.java:841)Īt .ZygoteInit.main(ZygoteInit.java:599)Īt (Native Method) Your app will crash in the most glorious fashion: FATAL EXCEPTION: main If you do this and you're using tCustomAnimations() you may be in for a shock. To be clear: I'm converting apps that use to now use support versions of Fragments. I've been converting a lot of my apps to the support library recently and ran into one issue worth mentioning.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |