fix(ios): replay loop animations when the app becomes active again

[janicduplessis]

Summary

Closes #66.

On iOS a looping animation stopped for good after the app went to the background and came back: the view sat at its resting value until it remounted. Core Animation drops a layer's animations while the app is backgrounded. The saved loop snapshots (_loopAnimations) were only replayed from didMoveToWindow, which doesn't run here because the view never leaves its window.

EaseView now replays its saved loops on UIApplicationDidBecomeActiveNotification, after dropping any the current props no longer ask for (same as the window path). UIApplicationWillEnterForegroundNotification is too early: animations added then were dropped again. reapplyLoopAnimations now skips keys that still have an animation, since becoming active also follows inactive-only interruptions (Control Center, system alerts) where nothing was removed; re-adding would only churn onTransitionEnd accounting.

Loops keep their phase: the snapshots carry an explicit beginTime, so a loop picks up where it would have been.

Test Plan

iOS simulator (iPhone 16 Pro, iOS 18.6, Debug), on the example's Loop → Pause / Resume marquee:

• A running loop keeps moving after Home → reopen. Screenshots 1.2 s apart change (about 227k pixels in the strip), where without the fix they were identical.
• A loop paused before backgrounding comes back frozen at the same position (identical tile edges) and resumes when unpaused. This needs feat: pause animations in place with paused and report the frozen values with onPaused #65.

The new Issues → Issue #66 — Background loops screen (a spinner and a pulse) is for regression checks.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
react-native-ease	Ignored		Oct 15, 2026 11:26am UTC