-
Bug
-
Resolution: Fixed
-
Minor
-
3.8.5, 3.9.2, 3.10, 4.0
-
MOODLE_310_STABLE, MOODLE_38_STABLE, MOODLE_39_STABLE, MOODLE_400_STABLE
-
MOODLE_38_STABLE, MOODLE_39_STABLE
-
MDL-70081-master -
Previously we were able to detect the device type just by checking the length of the device token (64 bits for iOS, otherwise it was Android). The type of device is necessary to correctly prepare the payload format of a Push notification.
Since we starting using Firebase Cloud Messaging, the device tokens for Android and iOS have the same format, so it is not possible to detect the type of the device as we did before.
This has not been a major problem because of as part of the Push Notification payload that comes from Moodle to Airnotifier we always include the device type, but, it could happen that the first time a use device is registered in Airnotifier is not via a Push Notification. In that case, the device type is incorrectly stored in the Airnotifier database (it will be fixed later after the user receive a Push notification).
So, basically, the main issue here is data inconsistencies between Airnotifier and Moodle list of devices.