You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Modify create user operation to send less associated info
* Let's send less data into a create user request to minimize changes that other information in the request payload causes the create user request to fail.
* At time of writing, common failure cases are subscriptions over limit or tags over limit.
* We won't combine alias, tags, and properties operations to the create user operation.
* Ideally we only want to combine the push subscription operations and not any sms or email operations to the create user operation, but it will require more changes to the SDK.
* For now, we will send any subscription operations with the create user operation, but no tags, aliases, or properties.
* @param appId The ID of the OneSignal application this user will be created under.
13
13
* @param identities The identities to retrieve/modify this user in subsequent requests. Each identity key/value pair must be unique within
14
14
* the application.
15
-
* @param properties The properties for this user.
16
15
* @param subscriptions The subscriptions that should also be created and associated with the user. If subscriptions are already owned by a different user
Copy file name to clipboardExpand all lines: OneSignalSDK/onesignal/core/src/main/java/com/onesignal/user/internal/operations/impl/executors/LoginUserOperationExecutor.kt
0 commit comments