Skip to content

fix: assign correct IDFV instead of random UUID#350

Merged
BrandonStalnaker merged 1 commit intomParticle:developmentfrom
mmustafa-tse:fix/randomIDFV
May 2, 2025
Merged

fix: assign correct IDFV instead of random UUID#350
BrandonStalnaker merged 1 commit intomParticle:developmentfrom
mmustafa-tse:fix/randomIDFV

Conversation

@mmustafa-tse
Copy link
Copy Markdown
Contributor

Summary

  • A customer reported that the IDFV comes in as a random UUID every time the mParticle SDK is initialized, I was able to reproduce and confirm the behavior and applied the fix below

Testing Plan

  • Was this tested locally? If not, explain why.
  • E2E tested

Reference Issue (For mParticle employees only. Ignore if you are an outside contributor)

} else {
_vendorId = UUID().uuidString
_vendorId = UIDevice.current.identifierForVendor?.uuidString
userDefaults[Device.kMPDeviceAppVendorIdKey] = _vendorId
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Heres the old functionality to compare this more easily. I think this is the correct fix comparing these

@BrandonStalnaker BrandonStalnaker merged commit c18b063 into mParticle:development May 2, 2025
12 checks passed
mparticle-automation added a commit that referenced this pull request May 2, 2025
## [8.30.3](v8.30.2...v8.30.3) (2025-05-02)

### Bug Fixes

* Assign correct IDFV instead of random UUID ([#350](#350)) ([c18b063](c18b063))
@mparticle-automation
Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 8.30.3 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants