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

React Native App Crash when in Production #23258

Closed
peterfei opened this issue Feb 2, 2019 · 6 comments
Closed

React Native App Crash when in Production #23258

peterfei opened this issue Feb 2, 2019 · 6 comments
Labels
Bug Resolution: Locked This issue was locked by the bot.

Comments

@peterfei
Copy link

peterfei commented Feb 2, 2019

Description

When I'm testing my app on develop mode, everything is ok, Everything was running fine, however during the review, Apple rejected the update because the app crashed on boot. Here are the meaningful lines the report:

Last Exception Backtrace:
0   CoreFoundation                  0x1d3b30ec4 __exceptionPreprocess + 228
1   libobjc.A.dylib                 0x1d2d01a40 objc_exception_throw + 55
2   vesali_app                      0x101c9f478 RCTFatal + 447
3   vesali_app                      0x101c9cf20 -[RCTExceptionsManager reportFatalException:stack:exceptionId:] + 491
4   CoreFoundation                  0x1d3b38630 __invoking___ + 143
5   CoreFoundation                  0x1d3a16450 -[NSInvocation invoke] + 291
6   CoreFoundation                  0x1d3a17034 -[NSInvocation invokeWithTarget:] + 59
7   vesali_app                      0x101cb28f4 -[RCTModuleMethod invokeWithBridge:module:arguments:] + 491
8   vesali_app                      0x101cf6770 facebook::react::invokeInner+ 25552752 (RCTBridge*, RCTModuleData*, unsigned int, folly::dynamic const&) + 247
9   vesali_app                      0x101cf64d0 invocation function for block in facebook::react::RCTNativeModule::invoke+ 25552080 (unsigned int, folly::dynamic&&, int) + 87
10  libdispatch.dylib               0x1d35696c8 _dispatch_call_block_and_release + 23
11  libdispatch.dylib               0x1d356a484 _dispatch_client_callout + 15
12  libdispatch.dylib               0x1d3511bd0 _dispatch_lane_serial_drain$VARIANT$mp + 591
13  libdispatch.dylib               0x1d3512718 _dispatch_lane_invoke$VARIANT$mp + 431
14  libdispatch.dylib               0x1d351aeb8 _dispatch_workloop_worker_thread + 599
15  libsystem_pthread.dylib         0x1d374d0dc _pthread_wqthread + 311
16  libsystem_pthread.dylib         0x1d374fcec start_wqthread + 3

Environment

System:
      OS: macOS High Sierra 10.13.6
Binaries:
      Node: 10.15.0 - ~/.npm-global/bin/node
      npm: 6.4.1 - ~/.npm-global/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
      iOS SDK:
        Platforms: iOS 12.1, macOS 10.14
IDEs:
      Xcode: 10.1/10B61 - /usr/bin/xcodebuild
npmPackages:
      react: 16.6.3 => 16.6.3
      react-native: ^0.57.8 => 0.57.8
npmGlobalPackages:
      react-native-unity-view: 1.3.3
      react-native-video: 4.3.1

[skip envinfo]
Any tips/suggestions are greatly appreciated,thanks a lot !

@react-native-bot
Copy link
Collaborator

Can you run react-native info and edit your issue to include these results under the Environment section?

If you believe this information is irrelevant to the reported issue, you may write [skip envinfo] under Environment to let us know.

@andresmtz98
Copy link

Same issue here :(. With RN .57.1, .57.8. With latest version i'm another error with jsiexecutors :/

@andresmtz98
Copy link

@peterfei do you use Pods in your project?

@mtostenson
Copy link

I've had a similar issue, production only that crashes on launch. I have a workaround described in this issue, it might be worth trying.

@andresmtz98
Copy link

andresmtz98 commented Feb 14, 2019

Same issue here :(. With RN .57.1, .57.8. With latest version i'm another error with jsiexecutors :/

I had that issue. It was due Podfile: the dependiencies in Podfile already were in "Build Phases".

@hramos
Copy link
Contributor

hramos commented Feb 14, 2019

Just to set expectations, we rarely track individual crashes in this repository, with the exception of reports where there are clear repro steps (i.e. a small sample project that shows the crash). As it happens, debugging individual crashes in any particular application is something that is very likely out of reach for any one in this repo other than yourself.

@hramos hramos closed this as completed Feb 14, 2019
@facebook facebook locked as resolved and limited conversation to collaborators Feb 14, 2020
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Feb 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

6 participants