Push Token not being sent to Real Time CDP from Mobile SDK | Community
Skip to main content
E
ExeK
Level 2
January 27, 2026
Solved

Push Token not being sent to Real Time CDP from Mobile SDK

  • January 27, 2026
  • 1 reply
  • 34 views

Hi Community,

We’ve implemented Mobile SDK in React Native app connected to AEP dataset.

Issue: From 20,000 profiles sending events, only 250 have push tokens registered (~1.25% success) from both iOS and Android.

What we have:

  • Firebase Messaging configured ✓

  • MobileCore.setPushIdentifier(token) called ✓

  • Events arriving to dataset ✓

  • Permissions requested ✓

Any debugging tips or similar experiences?

Thanks!

Best answer by ExeK

@Tof_Jossic 

I'll leave the solution here, as support informed us it's a known issue that's not yet documented.

The weird token behavior was due to an optimization introduced to prevent duplicate push token sync requests when the token hasn't changed. There's a bug where the push token can be mistakenly recorded as sent, preventing future push identifier requests until the token changes.

Resolution: The customer had to disable the "Optimize Push Identifier Update" option in the Adobe Journey Optimizer extension within Data Collection.

 

 

1 reply

Tof_Jossic
Adobe Employee
Tof_JossicAdobe Employee
Adobe Employee
January 27, 2026

​@ExeK not used this myself but it looks like the Assurance Push Debug view might be a good tool to start with: See https://experienceleague.adobe.com/en/docs/experience-platform/assurance/view/push-debug-view

    E
    ExeKAuthor
    Level 2
    January 27, 2026

    Thanks!
    Unfortunately, we’ve already used the Push Debug View and it didn’t help :( 

    Tof_Jossic
    Adobe Employee
    Tof_JossicAdobe Employee
    Adobe Employee
    January 27, 2026

    ​@ExeK It works for some so I’m thinking this could be a consent issue of some sort. You may want to raise a Support ticket with a recorded assurance session and / or ECID profiles you know for a fact don’t have the push token. The team should be able to do a more in-depth investigation looking at your specifics.

      Terms & ConditionsAccessibility statement

      Loading footer...