Skip to content

fix: idfa not populating for initial events#198

Open
sunitaprajapati89 wants to merge 3 commits intomainfrom
fix-idfa-not-populating
Open

fix: idfa not populating for initial events#198
sunitaprajapati89 wants to merge 3 commits intomainfrom
fix-idfa-not-populating

Conversation

@sunitaprajapati89
Copy link
Copy Markdown

Bug 1 - Application Installed / Application Opened missing IDFA (race condition)
getTrackingStatus() was called fire-and-forget in the constructor. The ATT dialog is async (user must tap), so those lifecycle events fired before the future resolved.
Fix: Stored the future in_ trackingStatusFuture and overrode execute() to await it before forwarding each event.
the first two lifervale ones — nowa
All events - including the first two lifecycle ones - now wait for the ATT response before proceeding through the pipeline.

Bug 2 - trackingStatus: denied
but real IDFA UUID in advertisingId
When not authorized, the Swift code fell back to self.fallbackValue which returns the real IDFV (Identifier for Vendor) UUID. Apple's privacy model requires returning the all-zeros string when tracking is not authorized.
Fix (PluginIdfaPlugin.swift:10): Changed the fallback from self.fallbackValue (real IDFV) to the literal
"00000000-0000-0000-0000-0000000000 for all non-authorized states (denied, notDetermined, restricted).

@sunitaprajapati89 sunitaprajapati89 changed the title fix: idfa not population for initial events fix: idfa not populating for initial events Apr 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant