Mobile app no longer syncing Eisy before and after update? Already sent it to Mobile crash report. 
Polisys work however Eisy does not?

Hi @sjpbailey,

As the author of the very misleading error message, I can say the error originates from code which was catching a bug in early 5.x 994 systems. This bug showed itself when 994 would return empty XML after  multiple successful (200) response for data.

With that said UD Mobile may catch other errors here also, such as files with empty XML.  So, it is very possible this error is triggered by a Node Server.

Please open a ticket and we can try remote diagnostic.

No need for a ticket. Must be a node that was pulled by UDI...

Javier,

 I did a power reboot and it finally synced!

Did this last updated do anything for UOM 25 indexed text to work from a node server on here?

Thank you for your Time!

Edited September 2, 20232 yr by sjpbailey

11 hours ago, sjpbailey said:

Did this last updated do anything for UOM 25 indexed text to work from a node server on here?

The issue is the ISY (not Admin Console) could not get or parse the NLS file.  For historical reasons the Admin Console has its own NLS parser.  It appears the Admin Console was able to get and parse the NLS file.  While UD Mobile also parses the NLS file it relies on ISY for formatted values when a status value changes which is the reason we know the ISY could not get or parse the NLS file.

As far as we know this is not an issue with current firmware or UD Mobile.  The same issue may be caused by an earlier ISY994 firmware which could have migrated. It may also be caused by Node Servers not updating profile files properly.

To check if this is caused by a migrated file please post or send me the response to /rest/profiles/family/10/files (i.e. http://192.168.X.X:8080/rest/profiles/family/10/files) ? . Also let me know the slot number for the node with the issue.

If the issue is not due to a migrated file other debugging steps are needed.