Get 'hashedDefaultUser' working even without a custom user set #214
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes #190.
But please note that this adds a
@MainActorrequirement to thehashedDefaultUserbecause accessing theidentifierForVendoron iOS needs access toUIDevice.current, which is only accessible on the main thread. Technically speaking, this is a breaking change, as users who migrated to Swift 6 may no longer be able to accesshashedDefaultUserfrom a background thread without adding concurrency to their code.Having that said, since the original PR states that this field was added to report the user ID to other systems, that kind of code should be done in concurrent contexts anyways and therefore for most users the fix would be as simple as adding the
awaitkeyword.