mirror of
https://github.com/nickustinov/itsyhome-macos.git
synced 2026-04-26 04:15:56 +03:00
[GH-ISSUE #57] Issue: App Transport Security prevents local insecure connections on the App Store version #56
Labels
No labels
bug
enhancement
pending release
pull-request
wip
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/itsyhome-macos#56
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @TheWojtek on GitHub (Feb 19, 2026).
Original GitHub issue: https://github.com/nickustinov/itsyhome-macos/issues/57
As I mentioned it on Reddit, the app (downloaded from the App Store, I am too lazy to check for updates manually) prevents local connections using unsecure http as per Apples App Transport Security which is mandatory for apps distributed via Apple App Store.
This prevents an insecure connection to a local HA server.
Possibly may be overridden by NSAllowsLocalNetworking or NSAllowsArbitraryLoads (which seems just too open for me). The documentation is unfortunately rather vague about "local networking", since it does not say if it is the subnet of the local machine or all subnets using common external IP (which in my case would definitely work, as my whole HA setup including my Zigbee coordinator and wifi-connected IoT runs on a dedicated subnet different from "regular" devices, computers, phones etc.)
I worked my way around by connecting to my secure outside world URL, however it would be great to keep the communication local.
@nickustinov commented on GitHub (Feb 23, 2026):
Hi! Could you please try installing build 229 from TF and let me know if the issue is fixed.
@nickustinov commented on GitHub (Feb 23, 2026):
https://testflight.apple.com/join/aMweYMF5
@TheWojtek commented on GitHub (Feb 24, 2026):
I am away (and without my computer) so will check it in March ;)
@nickustinov commented on GitHub (Feb 24, 2026):
To be released in 2.1.0
@TheWojtek commented on GitHub (Mar 2, 2026):
Confirmed working.