-
Notifications
You must be signed in to change notification settings - Fork 263
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.
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
[Looking for Feedback] OneSignal SDK 5.0.0-beta-02 Released! #1208
Comments
1 - In the previous SDK, we could get email and sms data like email address/phone number, email/sms player_id and email/sms subscription status: https://documentation.onesignal.com/docs/sdk-reference#email-user-properties Does the new SDK not provide these options? Just adding emails and phone numbers? 2 - What happens if UserA adds EmailA and UserB adds EmailA, what happens in this scenario? 3 - setExternalUserId is now replaced by login. What happens if the device is offline? How are tags and other properties handled in this case since there are no callbacks like setExternalUserId had? 4 - Alias is a neat feature, is there a way to list all associated aliases assigned to the current User? 5 - Similar question to 3 above, what happens if you call addEmail, addTags, addSMSNumber, addAlias if the device is offline or what if this fails to update within OneSignal due to API errors? 6 - Is there a replacement for getTags method? There needs to be a way to delete multiple tags but unclear which are set on the user. 7 - is postNotification method being deprecated? |
@jfishman1 These are really good points. Overall, one of the intentions with this release is for OneSignal to serve less as a data store for app developers. The main responsibility will be on the app developer to know the state of their users. For example, the Another side effect is that information is separated. For example, whether the app has system-level push notification permission or not can be retrieved by Another change is eventual consistency. On previous releases, many methods invoke immediate server calls to update device information. Now, the SDK batches updates and sends them on a regular interval (the specifics of which may still change, and may be modified by some parameter, but currently at every 5 seconds). Then, on app cold start and on every new session (app backgrounded for 30 seconds), the SDK fetches from the server to update the local state. Questions
True, in the alpha, app developers are not able to get the
The subscription for EmailA is removed from UserA and transferred to userB once UserB adds that email. As mentioned above, the main responsibility will still be on the app developer to manage adding emails to their users.
That is a good point and something we should try to address. Currently in the alpha, the SDK keep any updates queued in the device if they can't be sent due to not having a
There is no SDK API to get aliases for the user as the app developer should know the aliases they have added to users. However, information about a specific user can be retrieved with the Fetch User endpoint through the REST API.
See no.3 above about device offline. For other errors, the SDK will try to handle them, but we are open to feedback from OneSignal users on our removal of callbacks.
There is no replacement for
Yes, it is being deprecated since this seems mostly used for testing and developers can use the REST API instead. |
📌 5.0.0-beta-01 has been released 📌 |
📌 5.0.0-beta-02 has been released 📌 |
I'm not sure what to use instead of OneSignal.postNotification |
Why "postNotification" method is removed from SDK? |
📌 Latest beta release: 5.0.0-beta-02 📌
In this major version beta release for the OneSignal SDK, 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.
For information please see the migration guide.
🚧 Beta release. Please test thoroughly prior to production use 🚧
Please post any feedback related to the beta under this issue.
The text was updated successfully, but these errors were encountered: