-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
[ScrollView] Cannot find view with tag #XXX #1941
Comments
+1 |
+1 Strangely I get the opposite trigger. I cannot get it to happen the JS in bundled into the app but it frequently happens when the app is running via the packager but I'm yet to see it unless I have https://github.com/Shuangzuan/RCTRefreshControl active for that particular note. The errors I have seen are with |
Are there any solutions? |
Updating React-Native with master doesn't seem to give me the error anymore... |
Which version of RN are you running @ilansas? |
Master looks like it's out of date. It currently says v0.6.0, @ilansas. |
Yep v0.6.0, I was working on the previous version of master, the error was thrown there. So I updated it. |
My point is that the master that you have downloaded is out of date. v0.7.1 is current release and v0.8.0 will be out soon. The bug began in v0.7.0. You have, in fact, downgraded to fix the problem.
|
Note that we haven't been very good about updating the version numbers in the source as we make new releases...
|
@MossP Sorry, you might be right, the actual master is on v0.8, I didn't downgraded anything I just ran |
@ilansas Yeah, master got updated just after we spoke. |
Well to be clear I'm under v0.8.0 and I'm getting the error |
Yea, me too (0.8.0-rc.2) :) It all got a bit confusing then, sorry. |
I've seen this before as well, definitely worth looking into 👍 I haven't been able to create a reproducible example, so it would be great if someone could post one up here! |
+1 ,0.8.0.-rc ,when I onpress some element of scrollView, it crash. |
@cssoul - I'm not having that problem, do you have a reproducible example project? |
Ok, I might have some news here. This seems to happen only when you enable Live Reload, here are the cases I observed :
|
@ilansas I am not sure if that is true. I get the error on the iPhone too. Will try to create a reproducible example project |
@NishanthShanker, I don't think @ilansas was suggesting that it only happens on the simulator. |
Yep as said @MossP I wasn't suggesting that, I assume you based your thought on the (cmd+R), I just wanted to be precise about the "Reload". |
@ilansas Sorry my bad. |
Anything else on this guys? I have been getting these errors more frequently as well. |
I was able to bypass this error by adding a timeout before the interaction is executed. Though this reduces the responsiveness of the app by a bit, it doesn't throw the error anymore |
@NishanthShankar so did i, however at times i can still get it to throw the error. It's not the best solution (timeout) :/ |
Can confirm I'm encountering this when I press on |
Just seen this for the first time when jumping between tabs and I think I was touching the ListView while it happened. |
I was encountering this exact error when jumping between tabs / rapidly navigating between routes while testing my app I fixed it by decreasing the intialListSize prop value from 10 to 3. I think the error occurs because I was navigating away so quickly before the initial render had time to fully complete. <ListView
dataSource={this.state.dataSource}
renderRow={this._renderRow}
renderHeader={this._renderHeader}
initialListSize={3}
automaticallyAdjustContentInsets={false}
/> Perhaps try explicitly setting this prop's value to something small? |
Looking through ListView.js, I imagine the cause of this is several callbacks that don't check if the component is still mounted :/ |
I'm also getting this error, it's tricky to reproduce, may need to be reloaded a few times before it throws this error but here's an example of this: https://rnplay.org/apps/0OLARw |
I'm also get this error, I don't know how it happen. |
Summary: When bridge calls are made, they should be dispatched to their destination GCD queue in the same order they were made. (It looks like this invariant broke in 336e18d, which caused call order to depend on the iteration of `NSMapTable` keys whenever there are calls to multiple modules that share a queue) Fixes facebook#1941 (in which RCTUIManager createView addUIBlock blocks were sometimes running after other blocks that depended on them) I'm a react-native/iOS/objc newbie, so please excuse any ignorance this commit may well contain :) Closes facebook#2488 Github Author: Ted Suzman <[email protected]>
Ok, i think i found answer why i had that crash: <ListView
dataSource={this.state.dataSource}
onEndReached={handleLoadMore}
onEndReachedThreshold={100}
renderRow={this.renderRow}
/> and simple loader after list: {isFetchingMore && this.renderLoading()} That work in "Container" with connect to Redux and other functions, but dosnt work in "Component" (I have no idea why). But (!) if wrap loader in ` <View>{isFetchingMore && this.renderLoading()}</View> That problem gone! I think react-native need know about elements after |
Hello,
Sometimes when I'm scrolling or doing some swipes I'm getting these kind of errors (crashing the app). The error can be thrown multiple time for a same scroll with a different tag for each of them :
This doesn't seem to happen in debug mode (it never happened until now).
The text was updated successfully, but these errors were encountered: