macOS Sequoia
Comments
-
We've been testing with the betas, and no problems have been found. It's always a good idea to wait a couple of weeks after any major macOS release before upgrading your system, but we don't expect any issues with this one.
-
Thanks....well, Im a sucker for new software releases, so I probably cant wait that long, but thanks for your answer and advice :-)
-
I took a chance and updated to Sequoia the Mac Studio running SecuritySpy. (I made a TimeMachine backup first just in case.) Perhaps it was the reboot (the SecuritySpy system had not been rebooted for 171 days. I did skip some Mac updates, but not SecuritySpy, and have a power backup). But, SecuritySpy seems even faster and more responsive. It works on Sequoia perfectly. Thanks Ben and the team for having SecuritySpy ready to go.
This probably should be its own thread, but thanks for the great update to the iOS app. I love that I can now check video captures and the audio playing from another app keeps playing.
Marty
-
Been running the betas since July, no noticeable problems.
-
After upgrading to Sequoia, I notice strange bahaviour of SS v6.5 used for viewing only: FPS are dropping to low values resulting in distorted images. This seems to reflect only viewing, not the recorded clips.
-
@rapyt I've had to turn off my (Private Internet Access) VPN. It was messing with my network and I was seeing packet loss in SS. It appears to be a known problem that is affecting most -- maybe all -- VPNs with Sequoia.
Link to Apple Discussion forum: https://discussions.apple.com/thread/255761213?sortBy=oldest_first&page=1
The Messages app wasn't sending or receiving either.
-
Glad you sorted it. I found I had to turn off Little Snitch too! I run SS primarily on what I call my media Mac. I didn't realise my main life / work mac was similarly affected, the former being Intel and the latter an M2 Pro. So that's Little Snitch and Private Internet Access off everywhere.
Some have had to turn off the built in Mac Firewall too, but I've not been so affected.
-
The only issue that I came across after updating to Sequoia was that SS dod not have access to the local network after the install. All the cameras showed Color bars.
To fix this, go to:
Settings:Privacy & Security:Local Network
and enable the switch.
-
Thanks indeed @Robbie for that heads up.
Boy Howdy, Sequoia is looking farther and farther down the road for me.
-
Normally I wait till the new year to install the latest Mac OS, but this time I jumped the gun. I wouldn't go so far as saying I "regret" installing Sequoia ... but I should have waited awhile. 😀
-
The main issue we have seen with Sequoia is the one that @HPeet has referred to - there is a new "Local Network" permission option under System Settings > Privacy & Security, which needs to be turned on for SecuritySpy. However, this permission setting seems buggy.
macOS should ask you to allow permission the first time you open SecuritySpy under Sequoia, however some users are reporting that this did not happen. And, some users are reporting that even with this permission apparently enabled, SecuritySpy is blocked.
If you see a "no route to host" error in SecuritySpy's video windows, this may indicate that macOS is blocking connections due to this issue. In this case, try turning this permission setting off/on a few times, and/or delete and re-download/install a fresh copy of SecuritySpy (this won't affect your settings).
Other than this not-insignificant issue, Sequoia seems to be quite solid release thus far.
-
I am having the local Network permission bug and toggling fixes it but it does it every few days. I'm assuming it's a OS bug but it's quite annoying. Hopefully Apple patches soon.
-
It is - I think it's this bug has caused me a huge number of problems with my ChannelsDVR set-up, as well as Security Spy - my previously stable and fast response camera system on my warehouse has become quite buggy and unreliable, with all kinds of delays, errors about "no key frames recently" or "no valid frames recently" or just "timeout" = then everything works again for a bit, then various cameras go back to "connecting . . " and then it all starts again. With 7 cameras setup, I'm generally lucky to have 4 viewable at any time, and even then, it may be a stuck fixed image from a few minutes ago -
-
Things I've gleaned on my travels: Turn off these app/services if you use them: VPN, Firewall, LittleSnitch.
With LittleSnitch, go to Settings>Network>Filters> and disable it.
For WiFi, Settings>WiFi>Details>Private Wi-Fi address: Fixed (or off)
Since doing the above a few weeks' ago, SecuritySpy has been 100% stable. As has Messages and networking to my NAS.
Allegedly, Sequoia 15.1 due next week, has fixed the network issues. Of course, we will have to see.
Edited to add: I run Emby on the Mac, saving to a NAS. And been recording and playing fine with the above turned off.
-
I'm encountering this problem also.
If the Mac mini restarts then the cameras have a "no route to host" error in SecuritySpy.
Only way to resolve it is by closing SecuritySpy and then turning Local Network permission off and then on again.
Any better workaround than this?
-
I’ll give it a try waiting for the 2-3 mins and see how it goes.
-
Same issue here and, for me, it does not resolve itself over time. I have to go through the quit and toggle the setting routine which makes the system less robust since it requires intervention after a reboot.
Anything further on this?
-
We have been in touch with Apple engineering about this. The information we have received is that:
- Bugs have been found and fixed related to this permission item, but there are still some known unresolved macOS bugs related to it that will be fixed in future macOS updates.
- The main issue they are aware of is caused by having multiple instances of the same application installed on the Mac. In this case, macOS gets confused about which application has which permission, and can block local network access unexpectedly. Therefore, make sure that there is only one copy of SecuritySpy, of any version, anywhere, on your Mac.
- They are not aware of an issue whereby network access is spontaneously blocked after some time of working correctly, as long as there is only one instance of the application installed, and macOS 15.2 is in use.
If you are still seeing issues after double-checking the above items, I think the best course of action at this time is to wait for further macOS updates, which will make this permission item more stable and reliable. Unfortunately there is nothing we can in SecuritySpy about this problem - it's a macOS issue.
-
Any update on this? How safe to upgrade to Sequoia at this time?
-
Hi @QFive the main problem we saw with earlier versions of Sequoia is the new "Local Network" permission option blocking SecuritySpy's access, even when access has been granted. However, this isn't being reported much anymore, so it seems that this issue has been resolved with newer system updates, at least for the majority of users. No other problem specific to Sequoia is being reported.
-
Good to hear. Thanks Ben.
-
Hey Ben - installed 15.5 and no longer seem to be able to reach security-spy via safari browser internal to my network - any ideas ? App works fine.
-
Hi @FlipperMan sometimes when you update macOS it can reset custom network settings to default values. If you are using an IP address to connect, it's possible that this address has changed. The best address to use to connect from Safari on a different device is the Bonjour address that is displayed via Settings > Web > Access Info (this is the one ending ".local").
If you continue to have problems, please email us and include a debug file (SecuritySpy menu > Debug > Create Debug File On Desktop) along with a screenshot of the Safari window that shows the connection attempt and associated error message.
-
Hi Ben, bit more info for you - the SecuritySpy apps on both iPad and iPhone were working fine when on local network, I’m now remote from my network and neither devices are connecting now…..which makes me think its not a change in IP address as the app seems to store the .local address ?
-
I actually have had this same issue for a while now. Only through Safari. Apps also work fine on local network and off through my domain name but when I am on the local network on Safari, I have to use the ip address, the domain name never connects. Outside the network, it works just fine.
-
@FlipperMan - in that case, this sounds like an issue with remote access specifically. Try a reboot of your router, and if that doesn't do it, try following these instructions.
@bstep - from another device on your local network (e.g. Safari running on another Mac), it's normally best to use the ".local" address. This is what the iOS app uses to connect over the local network, so this local address must be functional. Alternatively, you could simply continue to use the IP address, however in this case, make sure this IP address is either manually-assigned on the Mac, or reserved for the Mac in the router (via a DHCP reservation), so that it doesn't change. Note that the "name.viewcam.me" DDNS address (which is used for access over the Internet) may not work from within your local network (this requires a specific router feature called "loopback" or "hairpinning", which not all routers support).
