Closing the application when go to the chat from notifications

[Den4ik92]

Description:

On the Android version single-server, when you go to chat from notifications (clicking on a message in the notification shade), the application closes completely.

Environment Information:

• Rocket.Chat Server Version: 6.8.0
• Rocket.Chat App Version: 4.48.0.1 single-server
• Device Name: Motorola g84 (andoid 14), emulator pixel (android 14)
• OS Version: andoid 14

Steps to reproduce:

1. We receive a message notification
2. Go to the notification shade and click on the message
3. The RocketChat application tries to open and immediately closes.

[dnlsilva]

I tested it here and couldn't reproduce it.
Can you reproduce it by building directly from the single server branch? Or just from your custom app?

[Den4ik92]

Good evening, thanks for your answer. I collected the application from the single-server branch, and now I am using this application, the problem is constant for several users. I found out one more thing: the problems appeared after updating the push notification settings on the server side. пт, 7 июн. 2024 г. в 19:46, Gleidson Daniel Silva ***@***.***

…

: I tested it here and couldn't reproduce it. Can you reproduce it by building directly from the single server branch? Or just from your custom app? — Reply to this email directly, view it on GitHub <#5682 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6VMFBVHI35QEN7NY77QWALZGHPVJAVCNFSM6AAAAABII4UXN6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJVGE4DONJUHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[dnlsilva]

Which setting? video conference?

[mmaxgit]

No, where change settings Push fcm legacy API to HTTP v1 API

[sanyappc]

I have the same problem when using Google FCM API Credentials

[Denis-Kirichenko]

I have the same problem when using Google FCM API Credentials

And how did you fix it?

[sanyappc]

And how did you fix it?

Back to the old API

[AndrewChau]

Same issue for me. The "legacy notification provider" is officially downgraded as of today - https://firebase.google.com/support/faq#fcm-23-deprecation

Some references:
wix/react-native-notifications#835
wix/react-native-notifications#951

Stack trace:

Exception java.lang.RuntimeException:
  at android.app.ActivityThread.performLaunchActivity (ActivityThread.java:4164)
  at android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:4322)
  at android.app.servertransaction.LaunchActivityItem.execute (LaunchActivityItem.java:103)
  at android.app.servertransaction.TransactionExecutor.executeCallbacks (TransactionExecutor.java:139)
  at android.app.servertransaction.TransactionExecutor.execute (TransactionExecutor.java:96)
  at android.app.ActivityThread$H.handleMessage (ActivityThread.java:2685)
  at android.os.Handler.dispatchMessage (Handler.java:106)
  at android.os.Looper.loopOnce (Looper.java:230)
  at android.os.Looper.loop (Looper.java:319)
  at android.app.ActivityThread.main (ActivityThread.java:8919)
  at java.lang.reflect.Method.invoke
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:578)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1103)
Caused by java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.Object android.os.Bundle.clone()' on a null object reference
  at com.wix.reactnativenotifications.core.notification.PushNotificationProps.asBundle (PushNotificationProps.java:26)
  at chat.rocket.reactnative.CustomPushNotification.onOpened (CustomPushNotification.java:111)
  at com.wix.reactnativenotifications.RNNotificationsPackage.callOnOpenedIfNeed (RNNotificationsPackage.java:108)
  at com.wix.reactnativenotifications.RNNotificationsPackage.onActivityCreated (RNNotificationsPackage.java:65)
  at android.app.Application.dispatchActivityCreated (Application.java:387)
  at android.app.Activity.dispatchActivityCreated (Activity.java:1460)
  at android.app.Activity.onCreate (Activity.java:1770)
  at androidx.core.app.ComponentActivity.onCreate (ComponentActivity.java:86)
  at androidx.activity.ComponentActivity.onCreate (ComponentActivity.java:353)
  at androidx.fragment.app.FragmentActivity.onCreate (FragmentActivity.java:249)
  at com.facebook.react.ReactActivity.onCreate (ReactActivity.java:45)
  at chat.rocket.reactnative.MainActivity.onCreate (MainActivity.java:20)
  at android.app.Activity.performCreate (Activity.java:8975)
  at android.app.Activity.performCreate (Activity.java:8944)
  at android.app.Instrumentation.callActivityOnCreate (Instrumentation.java:1456)
  at android.app.ActivityThread.performLaunchActivity (ActivityThread.java:4146)

---

Side note: I notice that the notification has some visual differences with the legacy API notification. The legacy notifications also appear as a toast message at the top when the notification first arrives but the new one doesn't.

[diegolmello]

Does this happen on Rocket.Chat app from Google Play?
If it doesn't happen, it's a configuration issue on your side.

Pay attention to Site_Url setting on admin panel.
Make sure it's the correct url.

[Den4ik92]

@diegolmello I will check it

[Den4ik92]

@diegolmello
In the version from the GooglePlay, notifications do not arrive at all

[diegolmello]

Are you trying to send push notifications from your whitelabel workspace to our official app or you signed in on our cloud?
You'll have to use our gateway in order to use our official app's push notifications.

[diegolmello]

You can also create two users on https://open.rocket.chat and create a thread between them on #general

[Den4ik92]

@diegolmello Got it, then it’s clear why there are no push notifications in the official application) I will continue to look for a solution.

[dnlsilva]

I managed to replicate the error, I will work on a fix.

[dnlsilva]

#5753

The fix was updated in the single server branch, I will close the issue for now.
If the error occurs again, please report it here.

[Den4ik92]

@GleidsonDaniel Thank you very much, everything works great)