[iOS SDK] Missing Adjust ADID for specific users preventing S2S subscription event tracking #784
Description
Description We are experiencing an issue where a subset of our iOS users does not have an Adjust ADID assigned, even though they are active users with confirmed subscriptions.
This issue was identified through our App Store Server-to-Server (S2S) notifications. While our server confirms these users have purchased a subscription, we cannot send the corresponding subscription events to Adjust because the adid field is missing in our user database.
Technical Details & Implementation
Retry Logic: Our client-side implementation is designed to fetch the adid from the Adjust SDK and sync it to our backend. If the adid is null or empty, the app is programmed to periodically retry the request until a valid adid is retrieved.
The Problem: Despite the repeated attempts, the adid is never populated for these specific users. This prevents us from mapping their subscription actions to their attribution data.
Scope: This is not happening to all users, but to a specific group/subset.
Questions for the Adjust Team We would like to understand if there are any specific conditions on iOS where an Adjust ADID cannot be generated or retrieved, such as:
Device-Level Restrictions: Does a specific ATTrackingManagerAuthorizationStatus (e.g., .restricted for minors or educational devices) prevent the SDK from receiving an ADID from the server?
Network Conditions: Are there known cases where specific ISPs, VPNs, or firewalls (especially in regions like South Korea or the US) block the initial handshake required for the Adjust server to issue an ADID?
Initialization Failures: Are there any scenarios where [Adjust adid] will permanently return nil despite the SDK being successfully initialized?
Hardware/OS Limitations: Are there any hardware-specific conditions or iOS privacy features (like "Hide IP Address") that might interfere with the ADID assignment process?