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
Hello, I'm currently working on a feature involving Live Activities with iOS and noticed differences between how this project and the REST API work. I was referring to the Start Live Activity REST API documentation when I noticed them. They are as follows:
A push token is required in the Java API, the REST API does not have that requirement.
Only one subscription id can be provided with the Java API, the REST API can be provided multiple.
The activity type in the request URL sent from the Java API is always token, this can be set to whatever string is needed when using the REST API.
The URL used in the Java API differs from the REST API.
I'm currently writing my own wrapper code to get around these differences, but was wondering if the Start Live Activity functionality from the REST API would ever make it's way into this project?
Thanks!
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Hey @edrobotij and thanks for reporting this! I'm working on touching-up the upstream project which generates the code for this SDK so I will definitely investigate this further. Please bear with me as it may take some time but I hope to have updates for you soon.
How can we help?
Hello, I'm currently working on a feature involving Live Activities with iOS and noticed differences between how this project and the REST API work. I was referring to the Start Live Activity REST API documentation when I noticed them. They are as follows:
token
, this can be set to whatever string is needed when using the REST API.I'm currently writing my own wrapper code to get around these differences, but was wondering if the Start Live Activity functionality from the REST API would ever make it's way into this project?
Thanks!
Code of Conduct
The text was updated successfully, but these errors were encountered: