[BUG] arc() is not working since v13 #3945

Activity

1. KingSora

   added

   bugSomething isn't workingSomething isn't working

   on Oct 17, 2026
2. mattgperry commented on Oct 17, 2026

   

   mattgperry

   on Oct 17, 2026 via email

   Collaborator

   More actions

   Should be fixed in latest - it’s just not on the site yet

   …

   On Sat, 17 Oct 2026 at 10:08, Rene Haas ***@***.***> wrote: *KingSora* created an issue (motiondivision/motion#3945) <#3945> Note *Motion for Vue issues:* Please open in the Motion for Vue repo <https://github.com/motiondivision/motion-vue>. *1. Read the FAQs <#m_-5392932929921264106_faqs> 👇* *2. Describe the bug* The arc() transition example is not working. *3. IMPORTANT: Provide a CodeSandbox reproduction of the bug* Simply go to https://motion.dev/docs/arc and check the result. Just to be sure I've copy & pasted the example into stackblitz: https://stackblitz.com/edit/vitejs-vite-lmsztagd - I've traced back the latest working version: v12.43.0 (latest v12.x) *4. Steps to reproduce* Use the example and click on the button. *5. Expected behavior* arc() should work like it did in the latest v12.x version // Bad: AnimatePresence is unmounted - exit animations won't run{ isVisible && ( <AnimatePresence> <Component /> </AnimatePresence> )} // Good: Only the children are unmounted - exit animations will run<AnimatePresence>{isVisible && <Component />}</AnimatePresence> — Reply to this email directly, view it on GitHub <#3945?email_source=notifications&email_token=AB34WKWXCU76OWYT4F2NP4L5UMSHZA5CNFSL4Z3JMQ5C6L3HNF2C22DVMIXUS43TOVSS6NJYHE3DGNRTG43TDJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB34WKQQBNB7GCG7IWWMWJT5UMSHZAVCNFSNUABFKJSXA33TNF2G64TZHMYTKNZYGQ3DQNZWHNEXG43VMU5TKOBZGYZTMMZXG4Y2C5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AB34WKVYZOBCQ2CZIGEHSXD5UMSHZA5CNFSL4Z3JMQ5C6L3HNF2C22DVMIXUS43TOVSS6NJYHE3DGNRTG43TDJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/AB34WKSRVKW53ZSWB4YSGQ35UMSHZA5CNFSL4Z3JMQ5C6L3HNF2C22DVMIXUS43TOVSS6NJYHE3DGNRTG43TDJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
3. KingSora commented on Oct 17, 2026

   

   KingSora

   on Oct 17, 2026

   ContributorAuthor

   More actions

   @mattgperry with "latest" do you mean the currently latest version v14.3.0 or a unreleased version? Because just wanna mention that in v14.3.0 its also not working.
4. mattgperry commented on Oct 17, 2026

   

   mattgperry

   on Oct 17, 2026 via email

   Collaborator

   More actions

   Ah yes you’re right the fix isn’t published yet, coming in the next release!

   …

   On Sat, 17 Oct 2026 at 11:43, Rene Haas ***@***.***> wrote: *KingSora* left a comment (motiondivision/motion#3945) <#3945 (comment)> @mattgperry <https://github.com/mattgperry> with "latest" do you mean the currently latest version v14.3.0 or a unreleased version? Because just wanna mention that in v14.3.0 its also not working. — Reply to this email directly, view it on GitHub <#3945?email_source=notifications&email_token=AB34WKWFNOEJ7Y2JQCNFQYD5UM5NNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTMMRTGI2DENBTGUZ2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-6232424353>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB34WKX3HCT2XGYSPG4UT6L5UM5NNAVCNFSNUABFKJSXA33TNF2G64TZHMYTKNZYGQ3DQNZWHNEXG43VMU5TKOBZGYZTMMZXG4Y2C5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AB34WKRK2BV6FZD3JL6MEA35UM5NNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTMMRTGI2DENBTGUZ2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/AB34WKXMWANUV5GWQ4QJ6XT5UM5NNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTMMRTGI2DENBTGUZ2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>
5. mattgperry commented on Oct 19, 2026

   

   mattgperry

   on Oct 19, 2026 – with Claude

   Collaborator

   More actions

   This is fixed in motion@14.3.1. 14.3.0 was published just before the fix (#3939) landed, which is why it still reproduced there. In 14.3.1, transition.path / arc() is followed again when animating elements with animate() and useAnimate(), and motion components still work as before. Thanks for tracking down the last working version, it made this quick to pin down!

   ---

   Generated by Claude Code
6. mattgperry

   closed this as completedon Oct 19, 2026