Android Mobile SDK to easily integrate communication features (WebRTC, messaging, presence, voice, video, screensharing) based on RestComm into native Mobile Applications
1st time app starts after being completely removed configuration of push is good. Then sometimes when app is restarted/resumed push notification configuration fails with 'Failed to register/update for push notification; Binding cannot be found'. Doesn’t seem to mess with actual push notifications delivery but we need to investigate what is wrong configuration wise.
1st time app starts after being completely removed, while still in the signin screen I see in the logs:
12-19 10:33:05.173 18785-18858/org.restcomm.android.olympus.debug D/FcmInstanceIDService: >>> Refreshed token: dpjf1IAo-z0:APA91bH_j7Zgo0amj5xGXa8pO_mn02R9n5zB-yFWGjZ3DIXKOfz1ZD4lQMS3CqCeRTWf9fxbD1Lu7oDpc7UYS7qjYAKITKkXBOj0VgjcPJuFOFlDC7m-yp0m375Z4NrZ1ieF-QjrXbXE
12-19 10:33:05.173 18785-18858/org.restcomm.android.olympus.debug D/FcmInstanceIDService: >>> Updating server
12-19 10:33:05.183 18785-18785/org.restcomm.android.olympus.debug E/FcmConfigurationHandler: Push notifications configuration failed, status: Failed to register/update for push notification; Binding cannot be found
Does it make sense to update the server before configuration data is given by the user? Can we avoid it?
Generally, registerForPush() seems to be called even in cases where nothing changed, like leaving and re-entering App (check at the end of this log for such a case). This might cause confusion as we’ll be getting callbacks at times when user did nothing and there was not FCM token update. Also it makes the App take longer time to connect in those cases. Can we make sure that it is only called when something has actually changed either through initialize() or updateParams(), or if FCM token has been updated?
Can we issue an error if the FCM SERVER KEY is missing? It's a typical mistake to do and there's no feedback to figure out what is going on, so we end up spending time to figure it out.
When receiving a push notification for an incoming call and answering it as audio only, when application is opened I’m asked to give permission for both audio and video.
Does it make sense to update the server before configuration data is given by the user? Can we avoid it?
Generally, registerForPush() seems to be called even in cases where nothing changed, like leaving and re-entering App (check at the end of this log for such a case). This might cause confusion as we’ll be getting callbacks at times when user did nothing and there was not FCM token update. Also it makes the App take longer time to connect in those cases. Can we make sure that it is only called when something has actually changed either through initialize() or updateParams(), or if FCM token has been updated?