Skip to main content

In the Person_Mobile table, the device OS version is stored (we are using iOS). However, we have seen where the mobile device has had recent iOS updates in the field but the iOS version is not updating in the tables. Is anyone aware of any iOS issues with FSM6 after a certain iOS update? We are in FSM 6u26.

This is low hanging fruit here but we do use this data in a report to stay in compliance with our Mobile Device audits.

 

Thanks,

Daniel

I do not know the official answer to this question, but we have witnessed this as well.  This does not only apply to iOS, but it also appears that any app that gets auto updated by the app stores have this issue.

The only way we have found to get it to sync the versions across the server and the device is on the device, to logoff, disconnect, then log back on which starts an initialization.  After that, the versions will update.

We have not tied it directly to this yet, but we have noticed that when we have this version mismatch between the device and the server, that the device tends to have more sync issues.

Hi ​@DanielBlake 

iOS mobile updates the OS version in two instances:

  1. When you initialize the mobile device.
  2. When you change the password.

If there's a mismatch between the OS version on the server and the mobile device, you’ll need to initialize the mobile device. This will ensure that the current mobile OS version is updated in the system.

​@shalikakk, Initialization did not update the data. Only during a full delete and reinstall of the application were we able to match the iOS version in the Person_Mobile table to the iOS version on the actual device.

​@DanielBlake  Initialization means you need to activate the mobile after entering the correct service URL and credentials. The OS version update function is not triggered when you initialize the mobile from the admin screen.

Reply


Terms & ConditionsCookie settings