Repository navigation
0.4.1
Fixes
- Scope shared-element registration, readiness, visibility, and navigation lineage to unique route instances, keeping repeated instances of the same screen independent in React Navigation and Expo Router. (36e0486)
- Share navigation preparation ownership and request queueing across callers under one provider, with stronger handling of stale requests, interruptions, and source unmounts. (36e0486)
- Restore Back navigation fallback when reverse preparation finds no matching element pairs. (604bae5)
- Restore coordinator subscriptions correctly after React Strict Mode effect cleanup and replay. (604bae5)
- Retain a custom opening spring for Back transitions, including native Back and interrupted returns. Transitions without a custom spring retain the faster default return. (c7cbee8)
Integration Note
Keep ChoreographyScreen screenId, navigation destinations, and Expo Router's targetScreenId option as logical screen names. Session and renderer sourceScreenId, targetScreenId, and side screenId values now identify unique route instances, not logical screen names. Update custom renderers or instrumentation that compare those values with screen names.
Full changelog: v0.4.0...v0.4.1