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

iOS release build stops work after upgrading from 0.39.2 to 0.42.0 #12858

Closed
lucianomlima opened this issue Mar 10, 2017 · 2 comments
Closed
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@lucianomlima
Copy link
Contributor

lucianomlima commented Mar 10, 2017

Description

After upgrade from 0.39.2 to 0.42.0 I can't run release build in iOS through CLI or in Xcode.
Doesn't generate errors or warnings. Build is succeed but app freezes on splash screen. On 0.39.2 works fine.

Reproduction

react-native run-ios --configuration Release or change scheme to Release on Xcode.

Additional Information

  • React Native version: 0.42.0
  • React version: 15.4.2
  • Platform: iOS 9.x and 10.x
  • Operating System: MacOS Sierra with Xcode 8.2.1

My AppDelegate.m

  NSURL *jsCodeLocation;

  #ifdef DEBUG
    NSLog(@"Debug");
    jsCodeLocation = [[RCTBundleURLProvider sharedSettings] jsBundleURLForBundleRoot:@"index.ios" fallbackResource:nil];
  #else
    NSLog(@"Production");
    jsCodeLocation = [[NSBundle mainBundle] URLForResource:@"main" withExtension:@"jsbundle"];
  #endif

  NSLog(@"=========> jsCodeLocation: %@", [jsCodeLocation absoluteURL]);

I try to generate bundle with react-native bundle --platform ios --dev false --entry-file index.ios.js --bundle-output ios/main.jsbundle --assets-dest ./ios/main.jsbundle but not works.

On debug build, works fine and jsCodeLocation is http://localhost:8081/index.ios.bundle?platform=ios&dev=true&minify=false

On production build jsCodeLocation is file:///Users/lucianolima/Library/Developer/CoreSimulator/Devices/124E4686-6239-4A51-9A69-84942077CE9A/data/Containers/Bundle/Application/C3829A0A-511C-4203-9DA2-59C81948ABFB/carnaval24h.app/main.jsbundle

Again, this works before upgrading to 0.42.0.

Xcode log

objc[434]: Class PLBuildVersion is implemented in both /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator.sdk/System/Library/PrivateFrameworks/AssetsLibraryServices.framework/AssetsLibraryServices (0x120c52998) and /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator.sdk/System/Library/PrivateFrameworks/PhotoLibraryServices.framework/PhotoLibraryServices (0x120a74880). One of the two will be used. Which one is undefined.
2017-03-10 12:30:33.137 carnaval24h[434:20256331] initialize
2017-03-10 12:30:33.283 carnaval24h[434:20256331] Production
2017-03-10 12:30:33.284 carnaval24h[434:20256331] =========> jsCodeLocation: file:///Users/lucianolima/Library/Developer/CoreSimulator/Devices/124E4686-6239-4A51-9A69-84942077CE9A/data/Containers/Bundle/Application/C3829A0A-511C-4203-9DA2-59C81948ABFB/carnaval24h.app/main.jsbundle
2017-03-10 12:30:33.325 carnaval24h[434:20256331] [Crashlytics] Version 3.8.4 (121)
2017-03-10 12:30:33.357603 carnaval24h[434:20256331] [MC] System group container for systemgroup.com.apple.configurationprofiles path is /Users/lucianolima/Library/Developer/CoreSimulator/Devices/124E4686-6239-4A51-9A69-84942077CE9A/data/Containers/Shared/SystemGroup/systemgroup.com.apple.configurationprofiles
2017-03-10 12:30:33.359910 carnaval24h[434:20256331] [MC] Reading from private effective user settings.
2017-03-10 12:30:33.420 carnaval24h[434:20256331] Falling back to loading access token from NSUserDefaults because of simulator bug
2017-03-10 12:30:33.422 carnaval24h[434:20256331] Falling back to storing access token in NSUserDefaults because of simulator bug
2017-03-10 12:30:33.429 carnaval24h[434:20256331] Falling back to loading access token from NSUserDefaults because of simulator bug
2017-03-10 12:30:33.432 carnaval24h[434:20256331] Falling back to storing access token in NSUserDefaults because of simulator bug
2017-03-10 12:30:33.439 carnaval24h[434:20256331] Falling back to loading access token from NSUserDefaults because of simulator bug
2017-03-10 12:30:33.442 carnaval24h[434:20256331] Falling back to storing access token in NSUserDefaults because of simulator bug
2017-03-10 12:30:33.579 carnaval24h[434] <Notice> [Firebase/Analytics][I-ACS023007] Firebase Analytics v.3700000 started
2017-03-10 12:30:33.581 carnaval24h[434] <Notice> [Firebase/Analytics][I-ACS023008] To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled (see http://goo.gl/RfcP7r)
2017-03-10 12:30:33.602 carnaval24h[434] <Notice> [Firebase/Analytics][I-ACS003007] Successfully created Firebase Analytics App Delegate Proxy automatically. To disable the proxy, set the flag FirebaseAppDelegateProxyEnabled to NO in the Info.plist
2017-03-10 12:30:33.858 carnaval24h[434:20256331] ERROR: Error! iOS Simulator does not support push! Please test on a real iOS device. Error: Error Domain=NSCocoaErrorDomain Code=3010 "remote notifications are not supported in the simulator" UserInfo={NSLocalizedDescription=remote notifications are not supported in the simulator}
2017-03-10 12:30:34.600 carnaval24h[434] <Notice> [Firebase/Analytics][I-ACS023012] Firebase Analytics enabled
@Naoto-Ida
Copy link

Do you happen to be using GraphQL for your data needs?
I had issues that popped up when upgrading from 0.39 to 0.42 too. See here if interested.

@lucianomlima
Copy link
Contributor Author

Thank you @Naoto-Ida.
I'm not using GraphQL.
My problems disappeared after I generated a new clean application with React Native 0.42.0, moved all the files to the new clean version and reconfigured all JS modules.

React Native's upgrade is a trouble task yet.

@facebook facebook locked as resolved and limited conversation to collaborators May 24, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

3 participants