Open umangloria opened 1 month ago
Hi @umangloria
I am sorry to hear that you’re facing issues.
Could you please confirm if:
Regarding deep links, they can be set up directly from your JS/TS code. When configured properly, the deep links should be handled by your navigation library itself, such as @react-navigation
. The showPushAppInForeground
configuration provides a workaround to handle deep links when the app is in a killed state, which is due to lifecycle differences.
However, in most cases, your navigation library should be able to manage the deep link navigation based on the configurations you have set.
Please feel free to reach out if you have any other questions.
Hi @ami-aman , Here are the things which is what could help with the issue, Also, I only tried this issue in iOS, I am not sure about android though:
showPushAppInForeground
is already true as you can see in the above snippet. and it is only responsible to display push notifications when the app is not in killed state.ios.handleDeeplinkInKilledState
which enables the notification deeplink handling when the app is in killed state but there is no property like handleDeeplinkInActiveState
which should enable deeplink handing from push notifications when the app is not in killed state!!Thanks for your response, @umangloria ! Appreciate it !
To clarify, the configuration showPushAppInForeground
, when set to true
, handles push notifications sent by Customer.io and ensures they are shown when the app is in the foreground. It’s unrelated to handling deep links in a killed state.
You’re correct in saying that ios.handleDeeplinkInKilledState
is responsible for handling push notifications with deep links when the app is in a killed state. We do not have a property to handle deep links in an active state, as that’s managed by app's navigation handler. Also, using expo-notifications
depends on your app's requirements and is not required for handling deep links when the app is in the foreground or killed state.
I appreciate you sharing the configurations you’ve set in app.config.js
. To help us assist you further, we recommend sharing a code snippet with your navigation logic. Please ensure you remove any sensitive information like siteId
or keys before sharing. You can also send the code directly to win@customer.io
and reference this issue so our team can connect internally.
@ami-aman , Sent you the linking configuration code in the mail, However I think that the issue might be when the app is active and user get's the push, that PN is visible to user after we added this flag: showPushAppInForeground
Similarly, I think that to send the URL from the PN I think that there should be some code added from Customer.io side ? I am not sure but just thinking about possible solutions,
Thank you, @umangloria, for sharing the details. Our team will review it and get back to you with an update on this issue.
@ami-aman Any update on the same ?
Hi @umangloria
Thank you for your patience. Now that we are connected on an internal ticket, you’ll receive updates directly as we work on resolving this issue. We will keep you informed of any progress or developments on our end, so you’ll be fully up to date without needing to check back here.
If you have any additional details or questions in the meantime, please feel free to reach out on the ticket. We are here to ensure everything is addressed as smoothly as possible for you!
The issue: Deeplink/Universal Link is not working from push notifications if the app is not in killed state.
What is working: UniversalLink/Deeplink is working fine when the app is in killed state. that is when the app is not in running state and if user tap on the notification, it is opening the app and navigating the user to the respective screen.
Expected behaviour: Taping on push notification should open the app and move user to the respective screen according to the url when the app is opened and when the app is closed.
Configuration: this is what we have currently in app.config.js inside plugins:
versions: