Cannot use hostname in Controller Settings

[Goose66]

The Local Connection Settings for my Polisy in UD Mobile was set to "http://polisy.local" and worked fine for literally years. After the 5.9.1 upgrade the Polisy is no longer responding to "polisy.local" so I substituted "http://polisy.lan" for the hostname in Local Connection settings. ".lan" is the default DNS extension on my local network and all devices that have a hostname respond to <devicename>.lan whether they have mDNS capability or not.

However, with "http://polisy.lan," it says "ERROR: Could not finish Synchronization. The resource could not be loaded because the App Transport Security policy requires the use of a secure connection." But if you try and set the hostname to "https://polisy.lan," it says "URL must be fully qualified starting with http:// for local connection (not https)." Simply using "http://<ip address>" works, but requires fixed or assigned IP addresses (like we are all college geeks running Ethernet between our dorm rooms in the 80s).

Is this the intended functionality or do I have something set incorrectly?

[Javi]

App Transport Security is Apples security layer, so Apple has deemed this unsafe. 

https://wiki.universal-devices.com/index.php?title=UD_Mobile#App_Transport_Security_(ATS)_iOS

[Goose66]

So IP address only? Polisy.local worked for years.

[brians]

According to the support thread for IoX 5.9.1, it seems that many are reporting they cannot access from a PC or anything using eisy.local or polisy.local after the update and have to instead use IP address instead. 

 

Is mDNS broken in latest IoX 5.9.1 ?

 

[Goose66]

I put in a ticket and UD confirmed it was a bug. They asked me to make an adjustment in a file to debug, but I haven't done it yet. I will try and get back to them today. But there is an easy workaround (IP address) so I imagine they will just wait to the next point release to address it.

My point in this post is, even if they fix mDNS in the Polisy/eisy, will UD Mobile no longer allow us to use hostnames in the connection, i.e., is the user interface (in conjunction with Apple Transport Security, evidently) limiting the value here to IP Address. I will note that the name of the field is, in fact, "IP Address." Don't know if it's always been that but in hindsight it's pretty clear that's what UD Mobile user interface wants in this field (albeit with an "http://" in front of it).

Edited February 13 by Goose66

[Javi]

Nothing has changed in UD Mobile. iOS allows .local for local loads, if bug is fixed in firmware then .local should still work.

I should have been more clear in my post, ATS was in regards to .lan