bug: Tapping a secured push notification doesn't deep link correctly

[diegolmello]

Describe the Bug

Below

Steps to Reproduce

• Enable "Hide message content from Apple and Google (and the Gateway, if enabled)" (screenshot below)
• Receive a push notification
• (Message was decrypted correctly by the and the content is shown properly on Notification Center)
• Tap the notification

Expected Behavior

• App redirects to the message and highlight it

Actual Behavior

• App is only able to redirect to the room

Rocket.Chat Server Version

any

Rocket.Chat App Version

4.59.0

Device Name

any

OS Version

any

Additional Context

No response

[jjinendra3]

Hey @diegolmello ,

The bug seems to be that when tapping on a push notification for an E2EE message, the app only redirects to the room instead of directly to the specific message and highlighting it. Since the message is correctly decrypted and displayed in the Notification Center, I'll check why the app isn't handling deep linking properly to navigate to the exact message.

Let me know if there are any specific edge cases I should consider!

[diegolmello]

@jjinendra3 You should go ahead and open a PR.
Leaving a comment with the exact same description of the issue is going to give the rest of the community the impression this issue is assigned to you.
That's not the case!

[jjinendra3]

Hey @diegolmello, got it! I’ll go ahead and open a PR for this. Will keep this in mind for future issues. 🚀

[diegolmello]

@jjinendra3 Updates?

[JASIM0021]

@diegolmello, is this issue occurring on both Android and iOS devices?

[diegolmello]

@JASIM0021 Not sure, but probably on both

[jjinendra3]

@jjinendra3 Updates?

Apologies @diegolmello , was a lil busy, will look into this and update you asap, thanks.

[b90g]

When i tap on the notification it just opens the app but not the channel/message i tapped. On a regular non encrypted direct message. Client is apple Tablet 26.0.1 with RC4.65 , server is 7.1

notification preview is displayed correctly. - should i open a separate issue?

[diegolmello]

@b90g that's exactly this issue I described :)
I think it's iOS only (not sure), but it involves push notification on iOS (Apple certificates, profiles, etc), so it's not easy for a community contributor to fix it.

[deepak0x]

Hey @diegolmello @Rohit3523 — went through the notification deep linking flow and this looks resolved.

onNotification in notifications/index.ts extracts messageId from the EJSON payload (line 52) and includes it in the params dispatched to the deep linking saga (line 69). The saga picks it up as jumpToMessageId (deepLinking.js:79) and passes it through to goRoom(), which hands it off to RoomView. RoomView then calls jumpToMessage() on mount to scroll to and highlight the message.

This works for secured notifications since the server includes messageId in the EJSON payload regardless of whether message content is hidden. Think this one can be closed.