KOTB Posted September 5, 2025 Report Posted September 5, 2025 (edited) I’m able to sync using Wi-Fi between my iPhone and MacBook, but after a short while and then it stops!? I contacted support before, and they asked me to install the Discovery App to confirm that Wi-Fi sync is available, and it is (see details below). I sync at home so on the same Mac/iPhone network, no firewall, VPN..etc I’ve also attached iPhone/MAC screenshots to this post for reference. Thank You 5cd33998-1807-463f-a2f3-720f2ec13cc7._enpasswifisync._tcp.local. MBP-local.local:53042 192.168.4.125:53042 fe80::1c74:b3bb:3f5b:ac26%en0:53042 machine_name = MBP pinned_cert_hash = df2KccqdTvEClKcuMKWriqsNabwOoSwYpLvMmalrsC4= pinned_cert_hash_base32 = OX6YU4OKTVHPCAUUU4XDBJNLRKVQ22N4B2QSYGFEXPGJTKLLWAXA==== Edited September 5, 2025 by KOTB
KOTB Posted November 22, 2025 Author Report Posted November 22, 2025 I opened ticket number ECS-59044 a couple of months ago. Support reached out and asked for some data, and then I never heard back. I’m still experiencing the same issue, and the only temporary fix is to uninstall and reinstall the iPhone app. After a few days, the issue happens again.
Amandeep Kumar Posted November 24, 2025 Report Posted November 24, 2025 @KOTB Thank you for following up. We’ve reviewed the details of ticket ECS-59044, and I can confirm that this issue is already with our development team. They are actively working on a permanent fix. We did share a workaround earlier, but since it only helped temporarily in your case, the team is focusing on addressing the root cause. We truly appreciate your patience, and we will update you as soon as we have further progress or a fixed build available.
KOTB Posted December 4, 2025 Author Report Posted December 4, 2025 On 11/24/2025 at 7:36 AM, Amandeep Kumar said: @KOTB Thank you for following up. We’ve reviewed the details of ticket ECS-59044, and I can confirm that this issue is already with our development team. They are actively working on a permanent fix. We did share a workaround earlier, but since it only helped temporarily in your case, the team is focusing on addressing the root cause. We truly appreciate your patience, and we will update you as soon as we have further progress or a fixed build available. "We did share a workaround earlier!?" The last time this worked was in June and we are in Dec now.
Tarun Singh Rawat Posted December 4, 2025 Report Posted December 4, 2025 We apologize for the delay. The technical team is still investigating the issue, and we will get back to you as soon as we have an update. #SI-4472
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now