v0.3.0
Changed
- Persisted the same type of credential, to sign future JSON Web Tokens—even after invoking
updateUserEmail(in #134). Previously, if a user calledsetUserID, then updated a user's email withupdateUserEmail, future JWTs would be signed with the new email address even though the consumer code originally authorized with user ID.
Fixed
- Fixed an issue where calling
resumeMessageStreamshowed the next in-app message in the queue, even ifpauseMessageStreamwasn't called first (in #135)
Full Changelog: v0.2.1...v0.3.0