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
When an SDK goes down, it still has calls routed through it, which makes for a poor app experience and for any apps relying on it (i.e. livestreamer)
The goal would be to make sure the status is properly reflected for app users and then stop routing any new calls until the SDK is healthy again.
For users with wallets, we'll use the status call to show them a warning about some account related things not working. Something we noticed recently with KP is that single resolve calls (happen on content pages and a few other areas) always have wallet data appended to them, so those would always fail. We probably don't want to do that, and can add the additional params (include purchase receipt / include protobuf) only in specific cases . Don't recall what protobuf is used for.
The text was updated successfully, but these errors were encountered:
When an SDK goes down, it still has calls routed through it, which makes for a poor app experience and for any apps relying on it (i.e. livestreamer)
The goal would be to make sure the status is properly reflected for app users and then stop routing any new calls until the SDK is healthy again.
For users with wallets, we'll use the status call to show them a warning about some account related things not working. Something we noticed recently with KP is that single resolve calls (happen on content pages and a few other areas) always have wallet data appended to them, so those would always fail. We probably don't want to do that, and can add the additional params (include purchase receipt / include protobuf) only in specific cases . Don't recall what protobuf is used for.
The text was updated successfully, but these errors were encountered: