Skip to content

[5.0.0] beta-02 update migration guide to clarify migration limitation #1231

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 23, 2023
Merged

[5.0.0] beta-02 update migration guide to clarify migration limitation #1231

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions MIGRATION_GUIDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -732,10 +732,8 @@ The Debug namespace is accessible via `OneSignal.Debug` and provide access to de
- Changing app IDs is not supported.
- Any `User` namespace calls must be invoked **after** initialization. Example: `OneSignal.User.addTag("tag", "2")`
- In the SDK, the user state is only refreshed from the server when a new session is started (cold start or backgrounded for over 30 seconds) or when the user is logged in. This is by design.
- Limited support for migrating from `3.x.x` of the SDK. Currently recommend using for new app installs only.
- Limited support for migrating cached data in an existing app installation from `3.x.x` of the SDK to `5.x.x`. Currently, we recommend using this release in **fresh app installations** only.

# Known issues
- User properties may not update correctly when Subscriptions are transferred
- Please report any issues you find with this
- Identity Verification
- We will be introducing JWT in a follow up Beta release