Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Don't use idfv as deviceID if disabled #133

Merged
merged 1 commit into from
Mar 12, 2024
Merged

Conversation

crleona
Copy link
Collaborator

@crleona crleona commented Mar 12, 2024

Summary

Fix for #107. Note that users that have an existing deviceID set from IDFV will maintain their current deviceID.

Checklist

  • Does your PR title have the correct title format?
  • Does your PR have a breaking change?: no

@crleona crleona merged commit 76ef012 into main Mar 12, 2024
3 checks passed
@crleona crleona deleted the fix-idfv-device-id branch March 12, 2024 23:02
github-actions bot pushed a commit that referenced this pull request Mar 15, 2024
# [1.4.0](v1.3.6...v1.4.0) (2024-03-15)

### Bug Fixes

* Don't use idfv as deviceID if disabled. ([#133](#133)) ([76ef012](76ef012))
* Fixes for automatic screen tracking ([#137](#137)) ([55b2ca9](55b2ca9))
* tests on iOS 17 ([#136](#136)) ([04e5d03](04e5d03))

### Features

* migrate storage to for better thread safety ([#129](#129)) ([2bbe919](2bbe919))
Copy link

🎉 This PR is included in version 1.4.0 🎉

The release is available on:

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.

2 participants