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
Calling Iterable.updateSubscriptions during app init after initializing Iterable
Iterable.initialize(apiKey,config);// new userId that creates a new userIterable.setUserId(anonymousId);
can fail silently if done too quick in succession, XCode will only log:
.9520:0x280d29500:RequestProcessorUtil:sendRequest(requestProvider:successHandler:failureHandler:authManager:requestIdentifier:):32: No user exists with userId
13:26:56.9530:0x280d29500:RequestProcessorUtil:defaultOnFailure(_:):112: updateSubscriptions failed:, No user exists with userId
even calling await Iterable.getUserId() will return the userId but the call will fail still.
but the function itself is not a Promise that returns any value indicating if it succeeded or not. meaning there is no way to know if we should try again in a different session or not.
Ideally Iterable.updateSubscriptions should be a promise that returns it's status.
Tested on
iOS 17
"@iterable/react-native-sdk": "1.3.17"
The text was updated successfully, but these errors were encountered:
Calling
Iterable.updateSubscriptions
during app init after initializing Iterablecan fail silently if done too quick in succession, XCode will only log:
even calling
await Iterable.getUserId()
will return the userId but the call will fail still.but the function itself is not a Promise that returns any value indicating if it succeeded or not. meaning there is no way to know if we should try again in a different session or not.
Ideally
Iterable.updateSubscriptions
should be a promise that returns it's status.Tested on
The text was updated successfully, but these errors were encountered: