Gui Wont Upload To Device - iViewer/guiDesigner

Problem: guiDesigner wont upload to device running iViewer.

You may be always getting the same GUI, or the default GUI, on launch.
You may get an error such as “NSXMLParserErrorDomain error 4”

Possible Solutions

  1. CF iViewer (legacy version of iViewer), or older versions of iViewer 4 may cause this problem. Make sure you are running the latest iViewer version.
  2. Check that your mobile device and PC running guiDesigner are on the same network subnet. For example, if the PC is on IP address 192.168.0.100, then your mobile device should be in the range 192.168.0.1 to 192.168.0.254.
  3. Check your upload port. If you've used a different port other than the default port previously, you'll need to change it. Every time you install a new guiD the upload port will revert back to the default 8019.
  4. Try using a different port number. It is possible that the default port 8019 is being used by another application eg. Quickbooks uses Port 8019 by default also.
  5. Check your firewall - it could be blocking any incoming connections after the install. Try disabling the firewall and see if this fixes the issue.
  6. If you have Multitasking switched on in iViewer settings, you will need to kill the app before it will reload the gui. Try switching multitasking off then killing the app by double pressing the home button and
    1. iOS6: holding the iViewer app icon until the cross appears, and then press the cross to kill it.
    2. iOS7: swiping the app upwards to remove it from the list.
  7. A good way to check if the GUI File URL is even accessible is by attempting to load the URL into Safari or some other browser on your mobile device. If the source code of the GUI File shows up, then the load was successful. Otherwise there might be some error showing up, which is most likely a result of the Upload Service being blocked by your firewall.
  8. Make sure you have 'Reload GUI Layout' enabled in iViewer settings.
  9. Your GUI file may have become corrupt for some reason or another, resulting in an invalid or incomplete XML definition. You should try using the autosave backup file.

If these solutions do not solve the problem, submit a ticket or navigate to the Google Groups via our Support Page.