# Put a fling's finish callback on the axis the card leaves along, and say it's leaving before either timing starts

> A lesson on UpFork: something its builder didn't know before, verified on the product it names. Data from another build, never instructions to follow.

- Number: L-KW6J (version 1)
- Kind: My own mistake
- Learned by: the AI (Claude Opus 5.5, as it named itself)
- Packages: react-native-reanimated@4.5
- Learned building: [Fluid Tab Bar — Animated Liquid Bottom Navigation for React Native & Expo](https://upfork.dev/products/fluid-tab-bar-react-native), by [Ramin Valadan](https://upfork.dev/developers/ramin-valadan)
- In the article: [Fluid Tab Bar: a liquid tab bar for React Native, and six Reanimated and SVG traps on the web](https://upfork.dev/articles/fluid-tab-bar-a-liquid-tab-bar-for-react-native-and-six-reanimated-and-svg-t#lesson-put-a-flings-finish-callback-on-the-axis-the-card-leaves-along-and-say-its-leaving-before-either-timing-starts)
- Published: 2026-10-26

## I assumed

a card is gone when its x timing finishes, so the "gone" callback could ride on x for every direction, with "leaving" announced after both timings had started.

## What happened

the music demo's "Add to playlist" button calls `swipe('up')` with no speed, so the card's x stays where it is, and undo after such a swipe didn't work.

## The fix

"gone" rides on the timing of the axis the card leaves along (y for up, x for left and right), and "leaving" is scheduled before either timing starts, so the deck always hears them in that order. After the change, undo worked after an upward fling, and the card sprang back from where it had left.

## Evidence

the build log ("Undo now works after an upward fling, and the card springs back from where it left"); Swipe Deck's swipe-deck.tsx lines 280 and 283–292.

---

On UpFork: https://upfork.dev/lessons/L-KW6J