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
Hello I am looking at using Discovery for a personal app I have been working on and I am also investigating the use of React Native.
However something is breaking whilst using it with React Native. It discovers my other device multiple times but the block to do something with the username is only called once until I close the app and reopen it, once I reopen it the block is called multiple times. Once I shut down my other device, the block carries on being executed but no name is received.
I understand you might not want to take interest in this issue as it could be caused by React Native but whats interesting is the checkList method isn't called on first initialisation. I think something to do with the NSTimer is broken but can't figure out what.
Have you seen this behaviour whilst developing?
The text was updated successfully, but these errors were encountered:
mintuz
changed the title
Cross Post from React Native
Cross Post from React Native - Bug with calling the block.
May 10, 2015
Hello I am looking at using Discovery for a personal app I have been working on and I am also investigating the use of React Native.
However something is breaking whilst using it with React Native. It discovers my other device multiple times but the block to do something with the username is only called once until I close the app and reopen it, once I reopen it the block is called multiple times. Once I shut down my other device, the block carries on being executed but no name is received.
Example of my implementation can be seen here facebook/react-native#1218
I understand you might not want to take interest in this issue as it could be caused by React Native but whats interesting is the checkList method isn't called on first initialisation. I think something to do with the NSTimer is broken but can't figure out what.
Have you seen this behaviour whilst developing?
The text was updated successfully, but these errors were encountered: