Stringee iOS SDK 2.2.0

What's new

• Access token renewal without reconnecting. The server warns about 60 seconds before the token expires through the optional StringeeConnectionDelegate callback tokenWillExpire:exp:expireInSeconds:. Renew on the open connection with updateToken:completionHandler:.
• Apps that don't implement tokenWillExpire: get requestAccessToken: instead. Calling connectWithAccessToken: with a new token for the same user then renews in place, so existing apps benefit without code changes.
• When a token expires without renewal, the server disconnects the client. The SDK reports didFailWithError: code 6 and requestAccessToken:, and no longer reconnects with the expired token. Call connectWithAccessToken: with a new token on the same StringeeClient to resume the session.
• Incoming calls are acknowledged to the server, so the same incoming call is no longer delivered twice.
• Fixed a crash when the server sends an expired-token notice without a request id.

Notes

• Your app must be able to fetch a fresh access token: with this version, servers that support token expiration disconnect clients whose token has expired.
• On servers without token expiration support, behavior is unchanged and updateToken:completionHandler: returns -5.

WebRTC stays at 137.0.0.