iOS: addViewToLayer not working

[Brianggalvez]

trying to add a subview to the following animation [https://www.lottiefiles.com/558-rewards-icon] doesn't work.

$.lottie.addViewToLayer({
        view : Ti.UI.createView({
            height : 40,
            width : 40,
            backgroundColor : "red",
            zIndex : 4
        }),
        layer : "Star"
    });

[m1ga]

iOS? I didn't implement the feature on Android. I think it is not available in lottie-android

[hansemannn]

Please try the iOS 1.2.0 Beta.

[Brianggalvez]

Yes, iOS. Now it shows the view but not in the correct layer :

It should be inside the star.

Also the beta version only works with the 6.2.0.RC

[hansemannn]

It is expected to be there, as it's by default placed at a 0/0 rect inside the wrapper view. You will have to position it to the correct rect for your use-case. I need to check that, as well as the < 6.2.0 compatibility. What does not work? Simply saying something doesn't work doesn't bring us to a solution :).

EDIT: It was a dynamic library, which is only supported natively in Ti SDK 6.2.0+. Removed that and replaced it with the source-files again. Works now.

[Brianggalvez]

Yes sorry for not pointing it...

As I see in the exaple [http://airbnb.io/lottie/ios/addsubviews.html] it's correct, you have to manually position it, I thought it would be centered automatically.

Thanks!

EDIT:

I've added two methods that I found useful:

-(void)logHierarchyKeypaths:(id)unused
{
    [[self animationView] logHierarchyKeypaths];
}

But with this I cna only see the logs with iOS Console App.

- (void)setValueforKeypathAtFrame:(id)args
{
    ENSURE_UI_THREAD(setValueforKeypathAtFrame, args);
    ENSURE_DICT(args);

    id value = [args objectForKey:@"value"];
    id keypath = [args objectForKey:@"keypath"];
    id frame = [args objectForKey:@"frame"];

    TiColor *newColor = [TiUtils colorValue:value];
    if(newColor!=nil)
    {
        value = [newColor _color];
    }
    [[self animationView]setValue:value forKeypath:keypath atFrame:frame];
}

And this one, but I feel that we could miss some cases for the 'value' key. How I should proceed, wait for the 1.2.0 release and do a PR or should I do it now?

[hansemannn]

Please wait for the 1.2.0 release, thx.

[hansemannn]

Closing this issue as it's solved.