Data Not Appearing in Adobe for iOS Using AEP Mobile SDK with React Native, but Works on Android

[jaishal]

We have integrated the Adobe Experience Platform (AEP) Mobile SDK into our React Native mobile application. Data is being successfully tracked and appears in Adobe for Android, but we are not seeing any data from iOS.

We're using processing rules with the prefix a.x to send data to Adobe. The SDK is initialized, and the same setup is being used for both platforms.

Here are some additional details:

• The AEP SDK and necessary extensions (Identity, Lifecycle, Signal, etc.) are registered in the React Native code.

[jaishal]

In addition to the above, I tested the app using project assurance and data is showing up there and it points to right report suite as well. 

[Vinay_Chauhan]

Hi @jaishal 

If data is flowing fine from Android but missing from iOS, even though Project Assurance shows hits going to the right report suite, the issue is most likely tied to either iOS-specific app permissions or data not being properly mapped in your processing rules.

A few things to check -

1. App Transport Security (ATS):
   Ensure your iOS app’s Info.plist has the correct exceptions or configurations to allow tracking calls to Adobe domains (https endpoints). Sometimes data hits are blocked silently due to ATS settings.
   
   

2. Processing Rules – Platform Filtering:
   Double-check if your processing rules are unintentionally filtering or excluding data from iOS. For example, if the rule logic includes a User-Agent or a.x.platform condition, ensure it's not scoped only to Android.
   
   

3. Lifecycle Events:
   Verify that the lifecycle module is actually triggering correctly on iOS. Unlike Android, iOS sometimes requires explicit calls or correct hook timing to fire lifecycle events from React Native.
   
   

4. Privacy Settings or Consent:
   Ensure there's no platform-specific difference in how consent or privacy settings are applied. If iOS is defaulting to opt-out, hits might be getting blocked before being sent.
   
   

Even though Project Assurance shows the data, if processing rules don’t handle iOS hits correctly or a report suite mismatch exists, data won’t appear in Adobe Analytics.

Hope that helps!

[jaishal]

Thanks @Vinay_Chauhan  for the response. 

Regarding the point number 1 and 3, we see data in assurance and in configuration viewer as well i see data is getting received in correct report suite, so that should eliminate the possibilities of both points 

[jaishal]

For point 4, where do we need to check? Is it from Adobe tool side or app code side? 

[Vinay_Chauhan]

Since data is showing in Assurance and going to the correct report suite, it’s safe to say the SDK and config basics are fine. The issue might be deeper likely with how the data is handled after it’s received.

First, double-check your processing rules. Sometimes they have platform-specific conditions (like user-agent or app type) that unintentionally filter out iOS hits. Make sure those rules aren’t scoped too narrowly.

Also, confirm that lifecycle events are firing as expected on iOS. In React Native, the behavior can differ slightly between platforms — especially in how the lifecycle module is triggered.

Regarding the consent or privacy setting (point 4), it’s something to check on the app code side.
Make sure iOS isn’t defaulting to a state like “opt-out” due to a missing or delayed consent signal.

If consent isn’t granted when the SDK starts, hits may not be sent at all even though Assurance sees them.

[jaishal]

1 more thing 1 noticed is that in android we are getting edge hit received and edge hit processed but for iOS we are not receiving it in Project Assurance. Please see attached screenshot.

[Vinay_Chauhan]

If you’re seeing “Edge Hit Received” and “Edge Hit Processed” for Android but not for iOS in Project Assurance, it usually means the iOS hits are not fully making it through the Adobe Experience Platform Edge Network.

Since you confirmed the SDK setup and report suite are correct, this could point to -

• iOS app network or permission issues blocking some calls

• Possible differences in how iOS sends data to the edge compared to Android

• Or the SDK version/config might be missing some Edge-specific modules or settings for iOS
  
  

Double-check the iOS app’s network permissions and SDK initialization to ensure Edge services are fully enabled. Also, review if any firewalls or proxies could be interfering.

If everything looks good on the app side, you may want to open a support ticket with Adobe to investigate the Edge processing for your iOS hits specifically.

[Jennifer_Dungan]

Hmm interesting...

Do you see any issues being flagged in the "Events" area of AEP Assurance (not just looking at the Analytics Events)

Compare the data here between iOS and Android and see if anything pops out....

[jaishal]

Hi jennifer,

Please see attached screenshot. All the highlighted in red are not showing up for iOS.

[jaishal]

Also @Jennifer_Dungan  and @Vinay_Chauhan  Does this consent extension needs to be installed from launch extensions. Please see attached screenshot. 

App developers are saying: if the Consent extension is not installed or not published in Adobe Launch:
• The SDK doesn’t know how to interpret or route the consent payload.

Is this correct?

[Jennifer_Dungan]

We are implementing the AEP SDK right now, we do not have any consent modelling... which means we also don't have that extension.. but we don't have any issue with iOS data....

Looking at your first screenshot, you have "datastream" highlighted as well... I am suspicious that the issue is really early on... as in, the SDK isn't properly connecting to your Launch Property which defines the datastream....

[Jennifer_Dungan]

Can you check the Edge > Event Transactions?

This should give you a visual breakdown of the flow of traffic... mine looks something like:

Compare Android and iOS... I suspect a lot of this will be missing... 

[jaishal]

Hi Team,

Just for an update the issue seems to be resolved after we enabled consent from extensions in Adobe launch. Can you please tell what does consent extension enable ? Like what it does? Please see attached screenshot

[Jennifer_Dungan]

As far as I am aware, the Consent extension is really just for integrating with opt-out models like OneTrust, etc....

If you don't allow people to opt-out, you shouldn't need that.

Even iOS's built-in, "allow tracking" is for advertisers 

In iOS, "Allow Apps to Request to Track" is a setting that controls whether apps can ask for permission to track your activity across other companies' apps and websites for advertising purposes

---

Specifically for "advertising purposes".. 

So for analytics, which is purely internal, we continue to track Adobe, while the advertisement tracking is removed... 

[gautham_madala]

I have seen issues on iOS and Android specifically has to do regarding configuration on codes 
Ensure the AEP SDK is properly initialized on iOS. Sometimes, initialization works fine on Android but may be missing or misconfigured on iOS.
If you've disabled auto lifecycle tracking (e.g. by disabling lifecycleAutoStart), you must manually call lifecycleStart() in React Native.