-
Notifications
You must be signed in to change notification settings - Fork 24.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Animated.sequence undefined is not an object (evaluating 'animations[current].start')
#43120
Labels
API: Animated
Needs: Attention
Issues where the author has responded to feedback.
Needs: Repro
This issue could be improved with a clear list of steps to reproduce the issue.
Needs: Triage 🔍
Newer Patch Available
Comments
|
github-actions
bot
added
Needs: Author Feedback
Needs: Repro
This issue could be improved with a clear list of steps to reproduce the issue.
labels
Feb 21, 2024
|
The PR that was closed does not seem like it would be a "bad" thing to include, as it is only a check that only avoids throwing error in an unexpected scenario. |
github-actions
bot
added
Needs: Attention
Issues where the author has responded to feedback.
and removed
Needs: Author Feedback
labels
Feb 21, 2024
This was referenced Apr 10, 2024
facebook-github-bot
pushed a commit
that referenced
this issue
May 28, 2024
Summary: Currently, if the `Animated.sequence` animation is finished, and then the `start()` method is called without a `reset()` method being invoked beforehand, the failure happens: ```undefined is not an object (evaluating 'animations[current].start')```. Use cases: - sequence animation started, finished, and then started again - sequence animation is used in `Animation.loop` with `resetBeforeIteration` set to `false`, which essentially does the same as the previous case Related issues: - #43120 - #37611 ## Changelog: [General] [Fixed] - Fix sequence restart failure Pull Request resolved: #44031 Test Plan: Test cases are included: 1 for regression and 2 for mentioned use cases in the summary Reviewed By: cipolleschi Differential Revision: D56015346 Pulled By: dmytrorykun fbshipit-source-id: 8b0f46c8a33397fece807634463ce630c89d28af
kosmydel
pushed a commit
to kosmydel/react-native
that referenced
this issue
Jun 11, 2024
Summary: Currently, if the `Animated.sequence` animation is finished, and then the `start()` method is called without a `reset()` method being invoked beforehand, the failure happens: ```undefined is not an object (evaluating 'animations[current].start')```. Use cases: - sequence animation started, finished, and then started again - sequence animation is used in `Animation.loop` with `resetBeforeIteration` set to `false`, which essentially does the same as the previous case Related issues: - facebook#43120 - facebook#37611 ## Changelog: [General] [Fixed] - Fix sequence restart failure Pull Request resolved: facebook#44031 Test Plan: Test cases are included: 1 for regression and 2 for mentioned use cases in the summary Reviewed By: cipolleschi Differential Revision: D56015346 Pulled By: dmytrorykun fbshipit-source-id: 8b0f46c8a33397fece807634463ce630c89d28af
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
react-native-bot
added
the
Stale
There has been a lack of activity on this issue and it may be closed soon.
label
Aug 20, 2024
This issue was closed because it has been stalled for 7 days with no activity. |
react-native-bot
removed
the
Stale
There has been a lack of activity on this issue and it may be closed soon.
label
Aug 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
API: Animated
Needs: Attention
Issues where the author has responded to feedback.
Needs: Repro
This issue could be improved with a clear list of steps to reproduce the issue.
Needs: Triage 🔍
Newer Patch Available
Description
From what I can tell, I am essentially running into the same problem as a prior closed issue. Which had a PR created to "fix" the issue, but was eventually closed without being merged.
I too (think) am running into the issue described before. I receive the following error in an unknown situation:
I am not certain of the root cause of it. Quite possibly it is as @hansencj06 described on the PR in 2020.
It is challenging to extract a minimal reproduction. But I can tell you that I essentially am animating a button to full width (normal) or a circle (loading state).
However, I am stopping and starting the two different animation sequences (
animateToCircle
,animateToButton
) in auseEffect
based on incoming states. i.e. If the incoming prop isloading=true
and I'm in the process of animating from a button to a circle when I receive updated propsloading=false
I will then interrupt the animation to a circle and begin the animation back to a button again.The animation related code is as follows:
Possibly I am misusing animations here and would welcome any suggestions on the "correct" way to accomplish this.
Steps to reproduce
Again, not 100% certain how to do this reliably, although a reproduction was provided in the original issue that should suffice hitting this scenario.
React Native Version
0.72.4
Affected Platforms
Runtime - Web
Output of
npx react-native info
Stacktrace or Logs
Reproducer
#17699
Screenshots and Videos
No response
The text was updated successfully, but these errors were encountered: