[BUG] : ATT not collected anymore in 5.5.0

[jbdb]

Hi
After updating our Adjust SDK to your 5.5.0 ReactNative version, we lost the IDFA value in the parameters collected on iOS devices in the SDK attribution event, after opening our app for the 1st time, and without any change to methods or anything in the SDK Adjust code.
We also noticed also that the attribution event were previously collected on the consent.adjust.com domain, and now in the v5.5.0 it's on analytics.adjust.com domain.
Could some changes in the 5.5.0 version have affected the way Apple ATT answer is managed with your SDK ?
And does this issue raise some points of interests from you to tell us in order to focus so we can fix this on our side ?
Thanks !

[jbdb]

Some additional infos here to add more content :
We never used the ATT authorization wrapper (see your doc here : https://dev.adjust.com/en/sdk/react-native/v4/features/att)
And when we updated the Adjust SDK version to 5.1.0, Adjust SDK was collecting the IDFA using consent.adjust.com domain.
But now we updated to v5.5.0, it's analytics.adjust.com that's used and no IDFA is collected anymore, while ATT answer is consented.
Is it coming from a missing link between ATT answer and our SDK setup we should add now ?
And if true, why do you impose this without mentionning as a major update ?
Thanks

[Aditi3]

Hi @jbdb,

Thanks for the additional context.

We checked on our end and confirmed that the IDFA parameter is included in attribution and event requests when ATT authorization is granted. It appears to be working as expected.

Here are a few important points:

• About the ATT authorization wrapper: This is not a new requirement in React Native SDK 5.5.0. Both the React Native v4 documentation you mentioned and the current docs explain that to collect the IDFA, your app must show Apple’s ATT prompt and get user authorization. The Adjust ATT wrapper is optional and just makes it easier to use Apple’s ATT API. You can still use your own or native ATT handling, but ATT authorization is always needed for the IDFA to be available.

• About the domain change: This is also not something new in React Native SDK 5.5.0. Our documentation for iOS 17 explains that non-consented traffic goes to analytics.adjust.com without IDFA, while ATT-authorized traffic goes to consent.adjust.com with IDFA.

Based on what you described, the first thing to check is whether the ATT prompt is actually shown for your app and if the device reaches Authorized ATT status.

To help us look into this further, could you please provide the following:

• Verbose SDK logs from a fresh install or first app open. Please share these to our support team at support@adjust.com.
• A short description of how your app requests ATT.

Once we have this information, we’ll be able to help you resolve the issue more quickly. Thank you in advance for providing the details.

[jbdb]

Hi Aditi and thanks for your answer.
To let you know, we are already in speak with adjust support as we were trying every option in order to move faster ^^
Support also asked for the verbose logs but we are only able to provide from a simulator device which is not relevant as it hasn't any IDFA value available by design.
We asked them to install the app (https://apps.apple.com/fr/app/pmu-fr-pari-hippique-turf/id369344998?l=en-GB) but appearently they don't have the possibility to use a VPN as app usage is geo-blocked if not in France, so they can't reproduce unfortunately, althought we receive logs from them showing that even if we consent to ATT popin we receive null values (not even 0,1,2 or 3 as expected).
To add more details, here in France/EuropeanUnion we have to use a consent management platform (Axeptio) in addition to the ATT, and if (and only if) the user accept both (CMP+ATT), then we init Adjust SDK.
What is weird here is that everything was working fine (att_status grabbed correctly) before we update your SDK from 5.1 to 5.5.0, so we're kind of confused.
Maybe you could explain us how technically the att_status answer is passed to your SDK and with which reactNative method ?
Thanks a lot for your help !