react-native run ios won't start application after re-init with 0.49, XCode works

[DavideValdo]

Is this a bug report?

Yes

Have you read the Contributing Guidelines?

Yes

Environment

Environment:
OS: macOS Sierra 10.12.6
Node: 8.7.0
Yarn: 1.2.1
npm: 5.4.2
Watchman: 4.7.0
Xcode: Xcode 9.0 Build version 9A235
Android Studio: 2.3 AI-162.4069837

Packages: (wanted => installed)
react: 16.0.0-beta.5 => 16.0.0-beta.5
react-native: 0.49.3 => 0.49.3

Steps to Reproduce

Initing a new project works fine.

Expected Behavior

react-native run ios starts the application on the Simulator

Actual Behavior

react-native run ios starts the application on the Simulator, which crashes after splash screen, packager keeps running. Starting from XCode works.

[hramos]

Do you see anything in the console when the app crashes? It might help debug this.

[DavideValdo]

Hello,
I see nothing in the console, build correctly succeeds even from command line, but application crashes after the splash screen.

I'm now experiencing problems with react-native-fetch-blob which seem to be 'solved' by stopping and running the app again without me really understanding what's going on, this give you any hints?

[DavideValdo]

Missed this warning:

RCTLog.js:48 Module RNFetchBlob requires main queue setup since it overrides constantsToExport but doesn't implement `requiresMainQueueSetup. In a future release React Native will default to initializing all native modules on a background thread unless explicitly opted-out of.

[vichetuc]

I also got problem. react-native run-ios not work OS: macOS Sierra 10.12.6 Node: 8.7.0 Yarn: 1.2.1 npm: 5.4.2 Watchman: 4.9.0 Xcode: 9.0 Build version 9A235 Android Studio: 2.3 AI-162.4069837 However it work with react-native version 0.44.0

…

On Fri, Oct 20, 2017 at 3:27 AM, DaveDanuve ***@***.***> wrote: Missed this warning: *RCTLog.js:48 Module RNFetchBlob requires main queue setup since it overrides constantsToExport but doesn't implement `requiresMainQueueSetup. In a future release React Native will default to initializing all native modules on a background thread unless explicitly opted-out of.* — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#16447 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADkhQHxzhNV1oRdht_LTD8N-3zKrA4p2ks5st7CVgaJpZM4P9vNG> .

-- Your faithfully, ------------------ *Sath Vichet* *IM *: vichet.sath

[DavideValdo]

run ios works with with version 0.48.3

[thejacobseely]

I had the same problem after upgrading to 0.48.0 using react-native-git-upgrade...

I did the following 3 things and when I had finished it worked again. I don't know which one solved the problem, so I will list all 3, in hopes that one of them will help:

1. I followed the instructions at https://stackoverflow.com/questions/45434420/react-native-project-i-follow-the-guide-of-facebook-but-it-did-not-work#45435518 and reconfigured Glog.
2. I deleted the cache by deleting the folder /ios/build/ModuleCache.
3. I continued upgrading by project from there.

Oh, and it almost goes without saying that after doing that I restarted the packager and reran react-native run-ios.

It well be upgrading again what fixed it, in which case this post won't be of much help, but given that we have the same issue after upgrading to different versions, I think there is a good chance that it is related to the setup and caches, so hopefully that helps.

[kozillla]

have the same issue , react-native 0.49 XCode 9.0.1 , @thejacobseely steps didnt work for me.

[DavideValdo]

@hramos The only idea I have so far would be sharing the project. I'm worried something bigger might be broken behind the scenes.

[Macstyg]

I have the same problem with android build, after react-native upgrade from version 46.3 to 49.3. Application just hangs on the white screen right after start. The build is successful without errors.

[NunoCardoso]

Upgraded ExpoKit sdk 21 to sdk22, along with React, and my app stopped working.
I have a detached app that compiles OK, but when running in a iOS simulator, it throws several warning such as:

hunnor[8308:234987] 2017-11-03 13:27:26.397 [warn][tid:main][RCTModuleData.mm:69] Module SQLite requires main queue setup since it overrides init but doesn't implement `requiresMainQueueSetup. In a future release React Native will default to initializing all native modules on a background thread unless explicitly opted-out of.

and the last entry is a:

libc++abi.dylib: terminating with uncaught exception of type NSException

Needless to say, same crash behavior on a real iOS device.

[codinsonn]

@NunoCardoso Exact same issue here. Any success yet?

[sksingh1]

same issue here. Any success yet?

[NunoCardoso]

Tried with another project. Same crash. Waiting for a fix.

[NunoCardoso]

will recuse from this thread, as I reattached my react native app, therefore I don't need XCode to compile, not I need 3rd party libraries. Good luck.

[asgeo1]

I'm having this exact same issue that @NunoCardoso describes.

I updated from

Expo 20.0.0 => 23.0.0
Expo Kit 1.19.0 => 2.1.1
React 16.0.0-alpha.12 => 16.0.0
React Native to 0.50

I created some breakpoints in XCode and saw that the app would crash after this line:

So looks like an ExpoKit issue. I'll try and chase it up further with them.

[stale]

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.