fix: expose getUserProperties() as a public function#85
Merged
Conversation
…nctionality of non-String type userProperties
bgiori
approved these changes
Feb 11, 2026
zhukaihan
approved these changes
Feb 11, 2026
kyeh-amp
force-pushed
the
expose-getProperties
branch
from
7444ea0 to
616dc53
Compare
This file contains hidden or 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
3 participants
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.
Summary
Expose ExperimentUser.getUserProperties() as a public function to provide read access for non-String type userProperties.
Current state allows for the writing of non-strings and there's even tests for this, but there's no way to read those properties back out. Reading
userPropertiesfrom the attribute is deprecated with a message to usegetUserProperties()in favor of the attribute:https://github.com/amplitude/experiment-ios-client/blob/main/Sources/Experiment/ExperimentUser.swift#L26
Checklist