Skip to content
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

App crash with error "index=4 count=3" using LayoutAnimation.easeInEaseOut() on Android #17118

Closed
jer-sen opened this issue Dec 8, 2017 · 11 comments
Labels
Ran Commands One of our bots successfully processed a command. Resolution: Locked This issue was locked by the bot.

Comments

@jer-sen
Copy link

jer-sen commented Dec 8, 2017

Is this a bug report?

Yes

Have you read the Contributing Guidelines?

Yes

Environment

This bug has been there for several months and is still there with react-native@0.51.0.

Environment:
OS: Windows 10
Node: 8.9.1
Yarn: 1.3.2
npm: 5.6.0
Watchman: Not Found
Xcode: N/A
Android Studio: Version 3.0.0.0 AI-171.4443003

Packages: (wanted => installed)
react: ^16.2.0 => 16.2.0
react-native: 0.51.0 => 0.51.0

Steps to Reproduce

On Android, updating a specific (but very simple) component tree after calling LayoutAnimation.easeInEaseOut() leads to an error.
Here is a repro : https://snack.expo.io/H1H0AbDZM
Just click 2 times on the top text component to see the app crash.

Expected Behavior

No app crash.

Actual Behavior

Component are not correctly rendered after first click (some are missing).
App crash after second click.:

index=4 count=3
addInArray
    ViewGroup.java:3971
addViewInner
    ViewGroup.java:3902
addView
    ViewGroup.java:3733
addView
    ViewGroup.java:3678
addView
    ViewGroupManager.java:47
manageChildren
    NativeViewHierarchyManager.java:401
execute
    UIViewOperationQueue.java:180
run
    UIViewOperationQueue.java:819
flushPendingBatches
    UIViewOperationQueue.java:926
access$2100
    UIViewOperationQueue.java:47
doFrameGuarded
    UIViewOperationQueue.java:986
doFrame
    GuardedFrameCallback.java:31
doFrame
    ReactChoreographer.java:136
doFrame
    ChoreographerCompat.java:107
run
    Choreographer.java:765
doCallbacks
    Choreographer.java:580
doFrame
    Choreographer.java:549
run
    Choreographer.java:753
handleCallback
    Handler.java:739
dispatchMessage
    Handler.java:95
loop
    Looper.java:135
main
    ActivityThread.java:5221
invoke
    Method.java
invoke
    Method.java:372
run
    ZygoteInit.java:899
main
    ZygoteInit.java:694

Reproducible Demo

Cf Steps to Reproduce

@jer-sen jer-sen mentioned this issue Dec 8, 2017
@stale
Copy link

stale bot commented Feb 6, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. If you think this issue should definitely remain open, please let us know why. Thank you for your contributions.

@stale stale bot added the Stale There has been a lack of activity on this issue and it may be closed soon. label Feb 6, 2018
@jer-sen
Copy link
Author

jer-sen commented Feb 6, 2018

Hey !

@stale stale bot removed the Stale There has been a lack of activity on this issue and it may be closed soon. label Feb 6, 2018
@DanGDroid
Copy link

#15698

@react-native-bot
Copy link
Collaborator

Thanks for posting this! It looks like you may not be using the latest version of React Native, v0.53.0, released on January 2018. Can you make sure this issue can still be reproduced in the latest version?

I am going to close this, but please feel free to open a new issue if you are able to confirm that this is still a problem in v0.53.0 or newer.

How to ContributeWhat to Expect from Maintainers

@react-native-bot react-native-bot added Ran Commands One of our bots successfully processed a command. Stale There has been a lack of activity on this issue and it may be closed soon. labels Feb 24, 2018
@stale stale bot removed the Stale There has been a lack of activity on this issue and it may be closed soon. label Feb 24, 2018
@Larrysea
Copy link

@react-native-bot hello I am still face this exception com.facebook.react.uimanager.IllegalViewOperationException: ViewManager for tag 10 could not be found did this also solved in v0.53.0

@AndrePech
Copy link

I am having the same issue.

1 similar comment
@psg2
Copy link

psg2 commented Mar 14, 2018

I am having the same issue.

@AsensioM
Copy link

AsensioM commented Apr 9, 2018

I have the same issue as well w/ v0.53.0

@tiaaaa123
Copy link

Same. with RN 0.55.2

@mstiggle
Copy link

mstiggle commented Jun 1, 2018

Same issue here. Real bummer that I have to disable most uses of LayoutAnimation for android

@evanjmg
Copy link

evanjmg commented Jul 29, 2018

Android crashes on Flatlist with LayoutAnimation. Please note this in the docs as warning until this index handling is fixed

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Ran Commands One of our bots successfully processed a command. Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

10 participants