-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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 App crash when click on to notification (Push notification from firebase-cloud-message) #3413
Comments
Update
|
Now, Im using both version
and
|
You shouldn't be mixing v5 & v6, this is going to cause a lot more problems than it's worth. Can you provide the stack trace of the error message, it should show the stack trace on the left of Xcode when it crashes - can't really tell where this is coming from otherwise. |
this is stack screen
I not really good about Xcode much. |
closed. This one make this work |
Issue
Android version is working fine
iOS App crash after Splash screen when click on to notification ( from background and closed State)
I have tried to downgrade to @react-native-firebase/app|messaging 6.4.0-rc4 version, it doesn't get this error but getInitialNotification () doesn't fire.
Temporary I will try to downgrade back to ver 5 for release Our app
Project Files
``
Click to expand
#N/A
Javascript
Click To Expand
package.json
:firebase.json
for react-native-firebase v6:# N/A
iOS
Click to expand
2020-04-08 10:56:11.622664+0700 viettimes[743:144382] [] nw_socket_get_input_frames recvmsg(fd 4, 1024 bytes): [57] Socket is not connected 2020-04-08 10:56:11.623715+0700 viettimes[743:144382] [] nw_socket_get_input_frames recvmsg(fd 12, 1024 bytes): [57] Socket is not connected 2020-04-08 10:56:11.626 [info][tid:com.facebook.react.WebSocketExecutor][RCTInspectorPackagerConnection.m:309] Error occurred, shutting down websocket connection: Websocket exception Error Domain=NSPOSIXErrorDomain Code=57 "Socket is not connected" UserInfo={_kCFStreamErrorCodeKey=57, _kCFStreamErrorDomainKey=1} 2020-04-08 10:56:11.626759+0700 viettimes[743:145124] [] nw_endpoint_handler_add_write_request [13.1 74.125.24.95:443 failed socket-flow (satisfied)] cannot accept write requests 2020-04-08 10:56:11.631865+0700 viettimes[743:143054] [] tcp_connection_write_eof_block_invoke Write close callback received error: [22] Invalid argument 2020-04-08 10:56:11.731280+0700 viettimes[743:142670] -[__NSCFNumber isEqualToString:]: unrecognized selector sent to instance 0xb000000000000015 2020-04-08 10:56:11.734428+0700 viettimes[743:142670] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFNumber isEqualToString:]: unrecognized selector sent to instance 0xb000000000000015' *** First throw call stack: (0x184592fe0 0x182ff4538 0x184599ef4 0x184596f54 0x184492d4c 0x100280290 0x10027c4fc 0x100146f00 0x100145180 0x18a958294 0x18a95c634 0x18a95ba90 0x18a9470ec 0x18a946d68 0x18ac81360 0x18610f22c 0x18613c884 0x18613c6f0 0x18613caa0 0x18454142c 0x184540d9c 0x18453e9a8 0x18446eda4 0x185ed9074 0x18a729c9c 0x10009f7c0 0x18347d59c) libc++abi.dylib: terminating with uncaught exception of type NSException (lldb)
AppDelegate.m
:react-native info
output:react-native-firebase
version you're using that has this issue:6.4.0
Firebase
module(s) you're using that has the issue:@react-native-firebase/messaging
TypeScript
?N
React Native Firebase
andInvertase
on Twitter for updates on the library.The text was updated successfully, but these errors were encountered: