Open uwe-neuronation opened 11 months ago
Did you find any solution for that exception? @uwe-neuronation I have an app that is migrating from Xamarin iOS to .NET iOS and the same problem is occurring on some lotties.
Thanks.
@FelipeLlinaresGomez Could you share one of the failing animations for analysis maybe?
@markuspalme I can't share the animations but I have found a solution for the ones that were failing. The json i was using had a fill layer with a malformed color. It was working fine with Xamarin but now there was something making it crash. I leave the changes I did on the file so it might be useful for someone else.
Did you find any solution for that exception? @uwe-neuronation I have an app that is migrating from Xamarin iOS to .NET iOS and the same problem is occurring on some lotties.
Thanks.
I did made a new binding based on the current Lottie.xcframework. Since it is a swift only lib a objectiv-C proxy was needed.
Did you find any solution for that exception? @uwe-neuronation I have an app that is migrating from Xamarin iOS to .NET iOS and the same problem is occurring on some lotties. Thanks.
I did made a new binding based on the current Lottie.xcframework. Since it is a swift only lib a objectiv-C proxy was needed.
Hello @uwe-neuronation . Do you happen to have this binding into any public repo to check it out myself? I'm also in the same boat and desperately need a new bind
Thanks
I get this exception on some of our Lottie files. The app was migrated from Xamarin.iOS to .NET iOS
Same Lottie-Files are ok on Xamarin and crashing on .NET. I could not yet find out what in the json tiggers the problem. Most of our animations behave normal.
Maybe someone can help us.