Rocket.Chat.ReactNative: Secured Push Notifications not loading content on ios
Description:
Having installed a trial version of Rocket.Chat enterprise in order to test the ‘Secured Push Notifications’ feature. It appears this does not work as expected. My android client works well and the notification loads the content (by message ID) as expected. For ios however, the notification content does not load and the notification shows a generic ‘You have a new message’ message.
Debugging shows that
- the call from the ios app to /api/v1/push.get?id=… gets a 401. It tries 5 times to load the notification but then gives up and displays the generic message. Further investigation shows that the ios app does not include a
x-auth-tokenheader. - The call from the android app to /api/v1/push.get?id= does include a
x-auth-tokenheader and returns successfully with a HTTP 200 response
Environment Information:
- Rocket.Chat Server Version: 4.7.0
- Rocket.Chat App Version: 4.27.1 (ios app)
- Device Name: Iphone 12
- OS Version: 15.4.1
Steps to reproduce:
- Installed Rocket.Chat using docker-compose
- Registered the installation and enabled a trial version of Enterprise Edition
- Create admin user user1
- Create user2 on browser client
- Log in to ios app as user2 and close the app
- Log in to browser client as user1
- send a message in the browser client as user1, tagging user 2, e.g.
@user2 test1 - Observe that after a delay a Push notification is received in the ios app, however only a generic ‘you have a new message’
Expected behavior:
ios should display a push notification with the content ‘test1’
Actual behavior:
ios (After a delay) displays a push notification with generic content of ‘you have a new message’
Additional context:
as mentioned above, use tcpdump and analyse to show that the call to load the notification by ID from the ios app did not include a x-auth-token and resulted in a 401 (Unauthorized). This happens 5 times before the app displays the generic notification text.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 3
- Comments: 39 (31 by maintainers)
Commits related to this issue
- Rewrite the label/description of the Push_request_content_from_server setting The label for this option was clear enough if you already knew what it was referring to, but as an admin reading through ... — committed to seekingalpha/Rocket.Chat by nmagedman 2 years ago
- Rewrite the label/description of the Push_request_content_from_server setting The label for this option was clear enough if you already knew what it was referring to, but as an admin reading through ... — committed to seekingalpha/Rocket.Chat by nmagedman 2 years ago
- Rewrite the label/description of the Push_request_content_from_server setting The label for this option was clear enough if you already knew what it was referring to, but as an admin reading through ... — committed to seekingalpha/Rocket.Chat by nmagedman 2 years ago
@ansiwen It actually fixed it! We’re going to make a release later this week. Thanks for your help!
Ok, I’m going to give it a try then.
@ankar84 You’re right. I’ve been testing secured push on the last days and it’s working all the time. Let’s make the release and you can try it on your side.
Thank you, @diegolmello. I appreciate you being on top of this issue! We’d like to re-enable this feature once it’s fixed.
This is affecting our instance as well after enabling the enterprise license.
Well it does make no sense, but disabling the option “Fetch full message content from the server on receipt” under “Push -> Privacy” fixed all our problems while still getting all of the message content.
@james-surevine agree with Diego, great investigation!
With Secure Push feature a have a bit different experience. Most of mobile clients are works perfect, they show message content in Secured Push. But there is some clients (a lot of them actually) that shows generic message. Majority of clients with that issue is definitely iOS clients. But I have users reports about same generic message on Android too! Here is a screen:
Here is an iOS screen
There is a temporary workaround - delete app and then install it again. That manipulation fixes Secured Push for some time, but not permanently - it will broke again. And I definitely saw when user first gets generic push message, but then after some time and without re-install of mobile application that same user gets proper message content.
So, my guess is not the only mobile client issue, it could be some server related issue too, or even both. @sampaiodiego agreed with me.
In fact that wonderful feature should be polished to bright like a diamond.