App is failing to launch

[rshaikhcornerstone]

React Native version:

0.59.9

Steps To Reproduce

1. When we are installing the app in the iPhone 6 (12.3.1), app is working properly on the first launch. But we close it and reopen it does not launch and it shows up in the tray as an active app.
2. If we close it and open it again same thing happens but we are not able to use the app. It just shows up in the tray.

Describe what you expected to happen:
The app should launch normally as it does on the first time.

Snack, code example, or link to a repository:

Console output -

2019-07-10 17:19:13.842669+0530 AppName[7829:2290393] - [I-ACS036002] Analytics screen reporting is enabled. Call +[FIRAnalytics setScreenName:setScreenClass:] to set the screen name or override the default screen class name. To disable screen reporting, set the flag FirebaseScreenReportingEnabled to NO (boolean) in the Info.plist
2019-07-10 17:19:14.360500+0530 AppName[7829:2290396] 6.3.0 - [Firebase/Analytics][I-ACS023007] Analytics v.60002000 started
2019-07-10 17:19:14.403169+0530 AppName[7829:2290395] 6.3.0 - [Firebase/Analytics][I-ACS023008] To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled (see http://goo.gl/RfcP7r)
2019-07-10 17:19:14.671917+0530 AppName[7829:2290397] 6.3.0 - [Firebase/Messaging][I-FCM001000] FIRMessaging Remote Notifications proxy enabled, will swizzle remote notification receiver handlers. If you'd prefer to manually integrate Firebase Messaging, add "FirebaseAppDelegateProxyEnabled" to your Info.plist, and set it to NO. Follow the instructions at:
https://firebase.google.com/docs/cloud-messaging/ios/client#method_swizzling_in_firebase_messaging
to ensure proper integration.
2019-07-10 17:19:14.674752+0530 AppName[7829:2290307] -[RNFirebaseNotifications init] [Line 46] Setting up RNFirebaseNotifications instance
2019-07-10 17:19:25.094653+0530 AppName[7829:2290397] [BoringSSL] nw_protocol_boringssl_input_finished(1543) [C3.1:2][0x1019191f0] Peer disconnected during the middle of a handshake. Sending errSSLClosedNoNotify(-9816) alert
2019-07-10 17:19:25.122485+0530 AppName[7829:2290397] TIC TCP Conn Failed [3:0x2836bef40]: 3:-9816 Err(-9816)
2019-07-10 17:19:35.433926+0530 AppName[7829:2290421] [BoringSSL] nw_protocol_boringssl_input_finished(1543) [C4.1:2][0x10192bf00] Peer disconnected during the middle of a handshake. Sending errSSLClosedNoNotify(-9816) alert
2019-07-10 17:19:35.436145+0530 AppName[7829:2290421] TIC TCP Conn Failed [4:0x2836b4f00]: 3:-9816 Err(-9816)
2019-07-10 17:19:35.506915+0530 AppName[7829:2290421] [BoringSSL] boringssl_context_alert_callback_handler(3724) [C5.1:2][0x101826390] Alert level: fatal, description: inappropriate fallback
2019-07-10 17:19:35.507113+0530 AppName[7829:2290421] [BoringSSL] boringssl_session_errorlog(224) [C5.1:2][0x101826390] [boringssl_session_handshake_incomplete] SSL_ERROR_SSL(1): operation failed within the library
2019-07-10 17:19:35.508381+0530 AppName[7829:2290421] [BoringSSL] boringssl_session_handshake_error_print(205) [C5.1:2][0x101826390] 4321294088:error:1000043e:SSL routines:OPENSSL_internal:TLSV1_ALERT_INAPPROPRIATE_FALLBACK:/BuildRoot/Library/Caches/com.apple.xbs/Sources/boringssl/boringssl-109.250.2/ssl/tls_record.cc:586:SSL alert number 86
2019-07-10 17:19:35.509010+0530 AppName[7829:2290421] [BoringSSL] boringssl_context_get_error_code(3617) [C5.1:2][0x101826390] SSL_AD_INAPPROPRIATE_FALLBACK
2019-07-10 17:19:35.513114+0530 AppName[7829:2290421] TIC TCP Conn Failed [5:0x2836b5e00]: 3:-9860 Err(-9860)
2019-07-10 17:19:35.514880+0530 AppName[7829:2290421] NSURLSession/NSURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9860)
2019-07-10 17:19:35.514964+0530 AppName[7829:2290421] Task <7D486CE3-EF13-4511-8BC6-D1D617DC98D0>.<1> HTTP load failed (error code: -1200 [3:-9860])
2019-07-10 17:19:35.515311+0530 AppName[7829:2290422] Task <7D486CE3-EF13-4511-8BC6-D1D617DC98D0>.<1> finished with error - code: -1200

[victoriris]

Having the exact same issue, any updates?

[stale]

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 a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.

[builtbyproxy]

Gday
If this is still an issue could you try running it with yarn react-native start --reset-cache and let me know the result? It sounds like its broken from the get-go but you first load a cached version, then when you reload, it loads your broken version

Also, what's the result of adding these lines to your info.plist

<key>NSAppTransportSecurity</key>
<dict>
 <key>NSAllowsArbitraryLoads</key>
 <true/>
</dict>

Just a hunch based on your NSURLSession/NSURLConnection HTTP load failed line in the log you pasted.

[stale]

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 a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.

[stale]

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.