Push notification questions, including deeplink

Mobile
1

Hi,

My basic notifications are effectively appearing fine, either from a webhook into a workflow or via a query directly in the app. However for some of them, the text of the message is larger than the 2 lines shown like this:

Screenshot_20241115_110750_Retool
Screenshot_20241115_110750_Retool1080×574 30.3 KB

If i tap on the arrow, or the ... the notificaiton just closes.

Question 1:is there a way to set it to expand to see the whole message? Highly likely that I have missed something somewhere.

The second question is about pages from a deeplink notification. Again in general it is working, as when the webhook triggers the workflow, I see the page appear. It appears as expected when the app is either open or closed, and if I am quick enough I can see the deep link parameters have been passed with the correct values. For now I am showing them in a key/value panel to check, but in the end they will be used to get more info and display it.

However, 9 times out of 10 (or probably more) the app resets - it effectively closes the page and goes back to the default page of the app. Is there a way to prevent this happening? I have checked most options I can see, but again may have missed something.

I have been tasked with adding the notifications to the app, I didn't write it from scratch, so it might be that we need to change something in the base config, but that's ok and I can do that.

Thanks for any advice,
Kev

Organizations and users quickstart

1 Like
2

Hey @kevin.hall! Welcome to the community. :slightly_smiling_face:

Not on the Retool side, as far as I know. There is probably a way to configure this for each device, but it would vary depending on the specific OS and version. For example, I'm running iOS version 18.1 and can see the entire notification with a long press.

I'm not able to replicate this behavior in my testing, whether the Retool app is open or closed when following the deeplink. The apps I'm testing with are very lightweight, though, which could potentially have an impact here. If you haven't already done so and have access to additional mobile devices, I'd recommend checking for the same issue on different hardware!