From d027998ed6bcb27ee40b4bab3e472697563374ca Mon Sep 17 00:00:00 2001 From: Shepherd Date: Wed, 16 Aug 2023 19:12:21 -0400 Subject: [PATCH] Update migration guide --- MIGRATION_GUIDE_v3_to_v5.md | 9 +++++---- .../Assets/OneSignal/MIGRATION_GUIDE_v3_to_v5.md | 9 +++++---- 2 files changed, 10 insertions(+), 8 deletions(-) diff --git a/MIGRATION_GUIDE_v3_to_v5.md b/MIGRATION_GUIDE_v3_to_v5.md index e603dd09f..df798703f 100644 --- a/MIGRATION_GUIDE_v3_to_v5.md +++ b/MIGRATION_GUIDE_v3_to_v5.md @@ -1,4 +1,4 @@ -# Unity v5.0.0-beta.3 Migration Guide +# Unity v5.0.0 Migration Guide In this release, we are making a significant shift from a device-centered model to a user-centered model. A user-centered model allows for more powerful omni-channel integrations within the OneSignal platform. This migration guide will walk you through the Unity SDK v5.0.0 changes as a result of this shift. @@ -241,12 +241,13 @@ The debug namespace is accessible via `OneSignal.Debug` and provides access to d # Limitations -- Recommend using only in development and staging environments for Beta releases. -- Outcomes will be available in a future release +- 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. # Known issues - Identity Verification - - We will be introducing JWT in follow up Beta release + - We will be introducing JWT in a follow up release # Troubleshooting diff --git a/OneSignalExample/Assets/OneSignal/MIGRATION_GUIDE_v3_to_v5.md b/OneSignalExample/Assets/OneSignal/MIGRATION_GUIDE_v3_to_v5.md index e603dd09f..df798703f 100644 --- a/OneSignalExample/Assets/OneSignal/MIGRATION_GUIDE_v3_to_v5.md +++ b/OneSignalExample/Assets/OneSignal/MIGRATION_GUIDE_v3_to_v5.md @@ -1,4 +1,4 @@ -# Unity v5.0.0-beta.3 Migration Guide +# Unity v5.0.0 Migration Guide In this release, we are making a significant shift from a device-centered model to a user-centered model. A user-centered model allows for more powerful omni-channel integrations within the OneSignal platform. This migration guide will walk you through the Unity SDK v5.0.0 changes as a result of this shift. @@ -241,12 +241,13 @@ The debug namespace is accessible via `OneSignal.Debug` and provides access to d # Limitations -- Recommend using only in development and staging environments for Beta releases. -- Outcomes will be available in a future release +- 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. # Known issues - Identity Verification - - We will be introducing JWT in follow up Beta release + - We will be introducing JWT in a follow up release # Troubleshooting