-
Notifications
You must be signed in to change notification settings - Fork 24.5k
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
Release build crashes on Android & iOS (On Launch) #18121
Comments
@YogeshYo are you able to provide us a reproducible demo? |
@joshyhargreaves, Thanks for your reply. |
Ideally we’d have a project you’ve uploaded which exhibits this crash; maybe you can reproduce with your depdencies and a new project. However, when I’ve seen crashes that happen on both iOS and Android at startup, it usually points to a problem that only occurs when building the jsbundle in release mode. To test this theory, modify your JSCodeCodeLocation on Android or iOS to point to: http://localhost:8081/index.bundle?platform=ios&dev=false&minify=false and see if the stack trace is any more informative. |
@joshyhargreaves, I tried above for android |
The actual point is finding the cause of the crash! |
@joshyhargreaves, anything else I can try? Release build was working fine until last week. I tried a release build with removed lib added since then but same error on release build. "App crashes after splash screen on both Android & iOS" |
@yogesho, the thing I might suggest, is if you can keep your native dependencies, remove any application code that you don’t want to upload, and create a repro project, then that’s be easier for one of us to take a look. |
@joshyhargreaves, i have shared repository details to you at [email protected] |
@joshyhargreaves, can you please look into this? I tried to reach you on Gmail. Thanks |
Hi Yogesh,
I’m a bit caught up at work at the moment and I haven’t had the time to
look, and it’s unlikely I will be able to tomorrow or over the weekend.
Your best bet is to try and create a reproducible sample project that
demonstrates this crash and upload this to the GitHub issue. Even if it
means keeping your same native decencies, it’s just a lot easier for people
to help you if they can try and find out the problem without downloading
your production app.
Thanks
Josh
…On Thu, Mar 8, 2018 at 2:28 PM Yogesh Lolusare ***@***.***> wrote:
@joshyhargreaves <https://github.com/joshyhargreaves>, can you please
look into this? I tried to reach you on Gmail. Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#18121 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABuTZzgw9D9n_8Ujzb79Y2Uy0EaShzGpks5tcYZSgaJpZM4SVC8T>
.
|
Hi @joshyhargreaves , I will do this still, I think if you have a chance to have at least one look then I am sure you can at least give me hint to move ahead on this. Believe me, I tried everything I can & now I am stuck. Thanks |
HI @joshyhargreaves, reproducible demo added |
@YogeshYo I have similar issue and it start happening after upgrade to react-native 0.50.4. I'm told the cause could be a that a dependency violates things that became invalid in react 16.0.0. |
@testshallpass, I went line by line & found two culprits for this issue (i.e only in release build). Platform.select({ Still, i think for the 1st; either the issue should be rectified in debug build or at least get a proper error message in the crash log. |
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as "For Discussion" or "Good first issue" and I will leave it open. Thank you for your contributions. |
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information. |
Is this a bug report?
Yes
Have you read the Contributing Guidelines?
Yes
Environment
Packages: (wanted => installed)
react-native: 0.52.0 => 0.52.0
react: 16.2.0 => 16.2.0
Target Platform: iOS (10.3, Android 7.1.2
Steps to Reproduce
(Write your steps here:)
iOS & Android release build crashes on application launch, debug build works fine.

Log
02-27 21:41:13.822 8695 8754 E AndroidRuntime: FATAL EXCEPTION: mqt_native_modules
02-27 21:41:13.822 8695 8754 E AndroidRuntime: Process: com.reactwork, PID: 8695
02-27 21:41:13.822 8695 8754 E AndroidRuntime: com.facebook.react.common.JavascriptException: undefined is not a function (evaluating '(void 0)()'), stack:
02-27 21:41:13.822 8695 8754 E AndroidRuntime: @531:415
02-27 21:41:13.822 8695 8754 E AndroidRuntime: c@2:837
02-27 21:41:13.822 8695 8754 E AndroidRuntime: n@2:409
02-27 21:41:13.822 8695 8754 E AndroidRuntime: t@2:262
02-27 21:41:13.822 8695 8754 E AndroidRuntime: @402:1044
02-27 21:41:13.822 8695 8754 E AndroidRuntime: c@2:837
02-27 21:41:13.822 8695 8754 E AndroidRuntime: n@2:409
02-27 21:41:13.822 8695 8754 E AndroidRuntime: t@2:262
02-27 21:41:13.822 8695 8754 E AndroidRuntime: @336:133
02-27 21:41:13.822 8695 8754 E AndroidRuntime: c@2:837
02-27 21:41:13.822 8695 8754 E AndroidRuntime: n@2:409
02-27 21:41:13.822 8695 8754 E AndroidRuntime: t@2:262
02-27 21:41:13.822 8695 8754 E AndroidRuntime: @303:161
02-27 21:41:13.822 8695 8754 E AndroidRuntime: c@2:837
02-27 21:41:13.822 8695 8754 E AndroidRuntime: n@2:409
02-27 21:41:13.822 8695 8754 E AndroidRuntime: t@2:262
Expected Behavior
The release build should not crash.
Actual Behavior
The debug build working fine.
The release build crashes on launch after displaying native splash screen.
Reproducible Demo
https://github.com/Tradesmen/CRASH/tree/master.
(Paste the link to an example project and exact instructions to reproduce the issue.)
The text was updated successfully, but these errors were encountered: