Skip to content

Commit da08182

Browse files
committed
note setLaunchURLsInApp removal in migration guide.
Fix grammar.
1 parent 21c52c1 commit da08182

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

MIGRATION_GUIDE.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -99,7 +99,7 @@ Replace the following:
9999
OneSignal.initWithLaunchOptions(launchOptions)
100100
OneSignal.setAppId("YOUR_ONESIGNAL_APP_ID")
101101
```
102-
To the match the new initialization:
102+
To match the new initialization:
103103

104104
**Objective-C**
105105
```objc
@@ -109,6 +109,8 @@ To the match the new initialization:
109109
```swift
110110
OneSignal.initialize("YOUR_ONESIGNAL_APP_ID", withLaunchOptions: launchOptions)
111111
```
112+
Remove any usages of `setLaunchURLsInApp` as the method and functionality has been removed.
113+
112114
If your integration is **not** user-centric, there is no additional startup code required. A device-scoped user *(please see definition of “**device-scoped user**” below in Glossary)* is automatically created as part of the push subscription creation, both of which are only accessible from the current device or through the OneSignal dashboard.
113115

114116
If your integration is user-centric, or you want the ability to identify the user beyond the current device, the `login` method should be called to identify the user:
@@ -227,7 +229,7 @@ The SDK is still accessible via a `OneSignal` static class. It provides access t
227229
| `OneSignal.logout()` | `[OneSignal logout]` | *Logout the user previously logged in via [login]. The [user] property now references a new device-scoped user. A device-scoped user has no user identity that can later be retrieved, except through this device as long as the app remains installed and the app data is not cleared. Note that if the current user is already a device-scoped user at the time `logout` is called, this will result in a no-op and the SDK will continue using the same device-scoped user. Any state that exists on this device-scoped user will be kept. This also means that calling `logout` multiple times will have no effect.* |
228230
| `OneSignal.setConsentGiven(true)` | `[OneSignal setConsentGiven:true]` | *Indicates whether privacy consent has been granted. This field is only relevant when the application has opted into data privacy protections. See [setConsentRequired].* |
229231
| `OneSignal.setConsentRequired(true)` | `[OneSignal setConsentRequired:true]` | *Determines whether a user must consent to privacy prior to their user data being sent up to OneSignal. This should be set to `true` prior to the invocation of `initialize` to ensure compliance.* |
230-
| `OneSignal.setLaunchURLsInApp(true)` | `[OneSignal setLaunchURLsInApp:true]` | *This method can be used to set if launch URLs should be opened in safari or within the application. Set to `true` to launch all notifications with a URL in the app instead of the default web browser. Make sure to call `setLaunchURLsInApp` before the `initialize` call.* |
232+
231233

232234

233235
## Live Activities

0 commit comments

Comments
 (0)