Note: Lottie 3.4.0 added a new rendering engine powered by Core Animation. Please try it out and let us know if you encounter any issues! It will be enabled by default in Lottie 4.0, which we plan on releasing later this month. More information is available in this announcement: #1627
Lottie 3.5.0
This version renames several public types, to resolve conflicts with types in Apple frameworks (#1420):
Lottie.Animationhas been renamed toLottieAnimation, to resolve a conflict withSwiftUI.AnimationLottie.Colorhas been renamed toLottieColor, to resolve a conflict withSwiftUI.ColorLottie.Vector3Dhas been renamed toLottieVector3D, to resolve a conflict withSpatial.Vector3D
For consistency with these new names, we have also renamed the following public types:
Lottie.AnimationViewhas been renamed toLottieAnimationViewLottie.Vector1Dhas been renamed toLottieVector1DLottie.Vector2Dhas been renamed toLottieVector2D.
For backwards compatibility Lottie 3.5.0 includes typealiases for the old names, which map to the new names. These typealiases are marked as deprecated and include fix-its to update call-sites to the new name.
Lottie 4.0
We plan on releasing Lottie 4.0 in the next few weeks. In Lottie 4.0 we will remove the compatibility typealiases (for Animation, AnimationView, Color, etc) , so code using the old names will no longer compile. This will resolve the naming conflicts with SwiftUI types. Consider updating to Lottie 3.5.0 first, applying the fix-its recommended by the deprecation warnings, and then update to Lottie 4.0 once it is released (Lottie 4.0 will no longer include deprecation warnings with fix-its). Thank you for bearing with us through this transition process!
Lottie 4.0 will also make the new Core Animation rendering engine (added in Lottie 3.4.0) the default rendering engine option. As mentioned above, please try out the new rendering engine if you haven't yet and let us know if you encounter any issues! We've been hard at work fixing issues reported by the community.