-
Notifications
You must be signed in to change notification settings - Fork 320
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
Push Notifications Not Working in Custom Mobile App with Self-Hosted Server #778
Comments
Same problem here |
+1 |
its started working fine after I did then its started working fine. but now FCM was deprecated so need to upgrade 3.10.0. will have to check again anyhow |
If you're using the official mobile app, push notifications should function without problems. Be sure that the environment variable ENABLE_PUSH_RELAY_SERVER is set to true. In the latest version 3.10, we've included FCM HTTP v1 updates. Additionally please upgrade the mobile app to version 1.0.41. |
Hi! In version 3.10 and mobile app 1.0.41, do I just need to set ENABLE_PUSH_RELAY_SERVER to true? Or do I need do add FCM_SERVER_KEY and ANDROID_BUNDLE_ID too? Where can I get this ids/keys?
|
@laianeramos FCM changes are only necessary for users who have a custom-branded mobile app. A detailed guide for this will be created soon. |
@muhsin-k I'm using the official mobile app, the environment variable ENABLE_PUSH_RELAY_SERVER is set to true, i'm using the latest versions of chatwoot web and mobile app, but push notifications are not working. I'm waiting for the guide to see if i'm doing anything wrong |
@laianeramos https://www.chatwoot.com/docs/contributing-guide/mobile-app/custom-release-guide#setup-firebase-for-push-notification Please check whether you have enabled the notification preferences in profile settings. |
Closing this issue, for now. Please feel free to reopen this if it is still an issue. |
Hey @muhsin-k After debugging we encountered these errors 1st error - After removing sound, collapse_key parameters from https://hub.2.chatwoot.com/send_push API. We got another error - |
Same problem here. No notifications using the oficial mobile app with self host installation. |
@mayank-gc It seems you're using an old version of Chatwoot. You need to upgrade to Chatwoot version 3.10.0. Push notifications won't work for earlier versions due to Firebase's API level changes. |
@muhsin-k I have the 3.12.0 version and the problem persists. |
@mayank-gc Did you make the changes? |
@mastermailgeral Please check you have followed this guide properly or not. |
@muhsin-k Yes, i follow the guide and i declare the variable ENABLE_PUSH_RELAY_SERVER=true, but only when i open the oficial mobile app, the app refresh and i see the new messages. I have installed Chatwood on docker. |
I have the same problem, chatwoot self hosted and official app, variable set to true and push notifications don't work, has anyone solved it? |
I have the same problem, chatwoot self hosted and official app, variable set to true and push notifications don't work, has anyone solved it? Chatwoot v4 |
I have exactly the same issue. |
Describe the Bug
Push notifications are not working in our custom Chatwoot mobile app connected to a self-hosted Chatwoot server. Despite updating the
ANDROID_BUNDLE_ID
, setting theENABLE_PUSH_RELAY_SERVER
environment variable to true/false, and updating theFCM_SERVER_KEY
and Google services JSON for Android, push notifications fail to be received.To Reproduce
Steps to reproduce the behavior:
FCM_SERVER_KEY
,ANDROID_BUNDLE_ID
, and setENABLE_PUSH_RELAY_SERVER
to true.Expected Behavior
Expected that the push notifications would be received on the device whenever a new message is sent or received in the app.
Observed Behavior
No push notifications are received on the device. No relevant error messages appear in the server logs, indicating a silent failure or misconfiguration.
Environment
Additional Context
All required configurations and environmental variables have been updated as per the documentation.
The text was updated successfully, but these errors were encountered: