You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Short lived TextView causing error "Trying to set local data for view with unknown tag: 4" on Android in RN 0.50.3 #16821
Create a view with a TextInput, make sure this view is showing when app is loaded but hidden quickly after (due to asynchronous event).
2.
Let this app load in the android emulator
3.
Once in a while you get error "Trying to set local data for view with unknown tag: 4"
Expected Behavior
I expect removing the TextInput shortly after app loading to work every time on Android without any errors
Actual Behavior
There seems to be a race condition when starting up the app causing the error
Reproducible Demo
Run this demo in the simulator. I have not been able to reproduce this on a device
I'm developing a redux-react-native app and as a workaround I just delay the rendering by some milliseconds between two states changes using a simple setTimeout while dispatching the next action.
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.
we are using react version 0.50.4 version and facing the same issue and we can not update the react version because we are using Salesforce sdk in which 0.50.4 react version is used.
Is there any resolution for same version to fix this issue?
Activity
meros commentedon Nov 14, 2017
Please note that I can reproduce the error only maybe once/10 reloads or so.
matthamil commentedon Nov 14, 2017
I'm also experiencing this. I get it every time I render a TextInput and immediately hide or transition to another screen.
wangghon commentedon Nov 14, 2017
There is a change in 0.51.0-rc.1, no exception anymore.
f2c6877#diff-e40bcf61507821200dcf1f573eb717e3
matthamil commentedon Nov 14, 2017
That change isn't published to npm yet is it? Is the solution to compile RN from source? @wangghon
wangghon commentedon Nov 14, 2017
0.51.0-rc.1 is not published to npm yet. I think it would be soon. need to build react-native from source to make the change take effects
arashmilani commentedon Nov 15, 2017
Is there any other workaround other than compiling RN from source
yaohongkok commentedon Nov 20, 2017
@wangghon I am wondering when will '0.51.0' be available officially on NPM?
wangghon commentedon Nov 20, 2017
@yaohongkok I am waiting for the release as well. Hope it can be released soon.
phu-tang commentedon Nov 29, 2017
I faced this problem when upgrade to react-native 0.50 :( but a little bit ( ... tag: 20) not sure it's relative but stacktrace is the same
GitHubTracey commentedon Nov 30, 2017
working with RN 0.50.4 and experiencing the same issue.
ociata commentedon Dec 2, 2017
Any workaround at least until it is merged?
jerameel commentedon Dec 3, 2017
Having this issue on 50.4 using windows, error occured on both emulator and actual device
arashmilani commentedon Dec 3, 2017
I'm developing a redux-react-native app and as a workaround I just delay the rendering by some milliseconds between two states changes using a simple
setTimeoutwhile dispatching the next action.jerameel commentedon Dec 3, 2017
how would you know where to add the delay? I'm on redux now
arashmilani commentedon Dec 3, 2017
in my case it just happens in some particular action and specific scenario
so I just delay dispatching that specific action.
10 remaining items
challme28 commentedon Feb 19, 2018
At react native 0.53 it no longer shows me the
Trying to set local data for view with unknown tag: Xmessagereact-native-bot commentedon Feb 24, 2018
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 Contribute • What to Expect from Maintainers
KarthikBaleneni commentedon Mar 22, 2018
In RN 0.53 . The issue still exists. Happens one in case of 10 attempts.
GregorHorvatH commentedon Apr 2, 2018
"react-native": "0.54.4" - fixed
joshuapinter commentedon Jun 19, 2018
✅ Confirmed. Fixed in React Native 0.54.4.
ashishalgo commentedon Jul 16, 2018
we are using react version 0.50.4 version and facing the same issue and we can not update the react version because we are using Salesforce sdk in which 0.50.4 react version is used.
Is there any resolution for same version to fix this issue?
tal987 commentedon Feb 11, 2019
@ashishalgo Did you find solution?