If I understood correctly, I was told that a change was being made that would allow iOS ATS to bypassed for companion fetch() calls in the event that you were communicating with an intranet device (in my case, via an REST HTTP API) -- with that being said, I'm trying to find out whether or not this exception was added in 2.42 (or 2.42.1) or is still pending.
Here is the thread: https://community.fitbit.com/t5/SDK-Development/Is-Fetch-limited-to-https/m-p/2225573/highlight/true... (Note: I am only posting a new thread since I didn't hear anything back on my reply to that message)
Can anyone on the app/dev team confirm? I have an app which is nearly 90% of the way to the finish line, however, I'm not going to publish something in which I'll have to exclude iOS users from being able to use.
Since the device is closed firmware, I have no ability to install an HTTPS certificate on it, so unfortunately, I'm trying to work around some technical limitations on the manufacturers end -- if possible.
