iPhone应用程序可完美地与任何模拟器配合使用，但是一旦我将插入的iPhone设为目标设备，该应用程序便以白屏开始，然后迅速进入黑屏。该应用程序永远不会崩溃。 下面是日志
2019-11-30 01:11:47.497215-0500 Chain[239:4370] - <AppMeasurement>[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-11-30 01:11:47.626693-0500 Chain[239:4172] [framework] CUIThemeStore: No theme registered with id=0
2019-11-30 01:11:47.750818-0500 Chain[239:4172] [Application] The app delegate must implement the window property if it wants to use a main storyboard file.
2019-11-30 01:11:48.231797-0500 Chain[239:4370] 5.15.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-11-30 01:11:48.269345-0500 Chain[239:4372] 5.15.0 - [Firebase/Analytics][I-ACS023007] Analytics v.50400000 started
2019-11-30 01:11:48.270071-0500 Chain[239:4372] 5.15.0 - [Firebase/Analytics][I-ACS023008] To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled (see )
2019-11-30 01:11:48.412172-0500 Chain[239:4377] [BoringSSL] nw_protocol_boringssl_get_output_frames(1301) [C1.1:2][0x104e20490] get output frames failed, state 8196
2019-11-30 01:11:48.412911-0500 Chain[239:4377] [BoringSSL] nw_protocol_boringssl_get_output_frames(1301) [C1.1:2][0x104e20490] get output frames failed, state 8196
2019-11-30 01:11:48.414254-0500 Chain[239:4377] TIC Read Status [1:0x0]: 1:57
2019-11-30 01:11:48.414434-0500 Chain[239:4377] TIC Read Status [1:0x0]: 1:57