iOS Push Notification Exclusion: pushNoTokenFoundInProfile After Profile Unification (Android Works)

Forum|Forum|8 months ago
May 9, 2025
4 replies
657 views

Hello,
I’m encountering an issue with push notifications. For Android devices, push notifications are working as expected on the same day the profile is unified with the ECID and push token.
However, for iOS devices, even after the profile is updated and unified with both the ECID and push token, the journey is excluding these profiles with the feedback message: pushNoTokenFoundInProfile.
Interestingly, after waiting 24 hours and running the journey again for the same iOS profiles, the push notifications worked as expected.
Has anyone experienced similar behavior where Android push works immediately after unification, but iOS does not, despite the profile showing the ECID and push token?
Are there any iOS-specific considerations, processing delays, or unification timing issues that could explain this?
Any tips or insights would be helpful?

Thanks

AJODev

Journey Optimizer

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

C

ChristianAb3

Adobe Employee

We're actually experiencing the same issue here. We'll keep an eye on the response.

S

SilvioAr2

Adobe Employee

Same issue here. Waiting response. Thanks.

P

phuo

Adobe Employee

Hi, there should not be any significant delay in iOS. May I ask if Android and iOS ECID/tokens belong to the same profile. When the journey is triggered, did you see the Android ECIDs work but iOS ECIDs excluded from the same profile and same push action?

A

AJODevAuthor

Level 4

Hi @phuo ,

No, Andriod/IOS ECID/tokens doesnt belong to same profile. i used two profiles with andriod & ios.
Yes, IOS ECID is excluded with message exclusion reason as "pushNoTokenFoundInProfile".

Thanks

AJODev