[NT-814] Partition key value precedence #1044
Merged
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.
π² What
Updates the value of
partition-key
in the record dictionary for our DataLake tracking client.π€ Why
Instead of just using a random UUID for this value we would like to use the user's ID (when available), the device identifier if the user's ID is not available, and a random UUID as a fail-safe value.
Note: As per the Apple docs, the
identifierForVendor
can only sometimes benil
if the device has not yet been unlocked. This probably only affects apps that access this value in the background but seeing as this can potentially benil
we coalesce using a non-nilUUID
string.π How
Updated the partition key value to coalesce from user ID through to
identifierForVendor
and lastlyUUID().uuidString
.β Acceptance criteria
partition-key
value should be that of the User's ID.identifierForVendor
value.