Skip to content

3.5.0
Compare
Choose a tag to compare
@calda calda released this 11 Oct 00:08
· 218 commits to master since this release
3.5.0
b4bd060
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

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.Animation has been renamed to LottieAnimation, to resolve a conflict with SwiftUI.Animation
  • Lottie.Color has been renamed to LottieColor, to resolve a conflict with SwiftUI.Color
  • Lottie.Vector3D has been renamed to LottieVector3D, to resolve a conflict with Spatial.Vector3D

For consistency with these new names, we have also renamed the following public types:

  • Lottie.AnimationView has been renamed to LottieAnimationView
  • Lottie.Vector1D has been renamed to LottieVector1D
  • Lottie.Vector2D has been renamed to LottieVector2D.

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.

Known issues

If your application has a storyboard that references AnimationView, it may crash when using Lottie 3.5.0 (#1771). The fix for this issue is to update all references of AnimationView to LottieAnimationView and update all references of Animation to LottieAnimation. This should be resolved in Lottie 4.0, where code using the old names will no longer compile.

Assets 2
Loading