You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,6 +23,8 @@ The platform will be `GCM` (This also includes FCM since it runs off of the same
23
23
24
24

25
25
26
+
For more details, see our [setup guide](https://support.iterable.com/hc/en-us/articles/115000331943-Setting-up-Android-Push-Notifications) on Iterable support website.
27
+
26
28
Congratulations, you've configured your mobile application to receive push notifications! Now, let's set up the Iterable SDK...
27
29
28
30
# Installing the SDK
@@ -70,13 +72,12 @@ Note that `FirebaseInstanceIdService` is deprecated and replaced with `onNewToke
70
72
```
71
73
72
74
* The `apiKey` should correspond to the API key of your project in Iterable. If you'd like, you can specify a different `apiKey` depending on whether you're building in `DEBUG` or `PRODUCTION`, and point the SDK to the relevant Iterable project.
73
-
* It is possible to call this elsewhere but we strongly encourage initializing the SDK in `Application`'s `onCreate`. This will let the SDK automatically track a push open for you if the application was launched from a remote Iterable push notification.
75
+
> ⚠ Don't call `IterableApi.initialize` from `Activity#onCreate`; it is necessary for Iterable SDK to be initialized when the application is starting, to make sure everything is set up regardless of whether the app is launched to open an activity or is woken up in background as a result of an incoming push message.
74
76
75
77
2. Once you know the email *(Preferred)* or userId of the user, call `setEmail` or `setUserId`
* If you are setting a userId, an existing user must already exist for that userId
79
-
* It is preferred that you use Email since that doesn't require an additional lookup by userId call on the backend.
80
+
> ⚠ Don't specify both email and userId in the same session, as they will be treated as different users by the SDK. Only use one type of identifier, email or userId, to identify the user.
80
81
81
82
3.**Register for remote notifications**
82
83
On application launch (or whenever you want to register the token), call `registerForPush`:
0 commit comments