When registering a Device there is a default Expiration date on console, and I know we can change it. My question is: what happens when the expired data overdue?
I want to send notifications to all devices registered in my app, and im not sure if I should worry about this Expire date (and set in to 2030, for example) or if it won’t break notification system.
I don’t want to renew the expire date overtime user starts the app, because he might open the app once a week, and it might expire after 1 or 2 days.
Question 1: What does the expire date imply?
Question 2: Whats the best approach for the use of in notifications?
My question is: what happens when the expired data overdue?
If your question means what happens when the expiration date is before the current time, then in that case the server will return error 5004.
Question 1: What does the expire date imply?
The expiration date sets a point in time when Backendless will remove device registration from its system. Setting it far into the future is not a good idea, because in addition to Backendless, device is also registered with Google or Apple servers, which will also expire the registration at some point (it is less predictable there). If device registration with Google/Apple expires, then the registration with Backendless will do no good since any push notifications will not arrive.
Question 2: Whats the best approach for the use of in notifications?
Do not set expiration for far into the future. Try to register more often to “refresh” registrations.