Since over a week now I am not able to update the Aqara home app on my MacBook Pro M4 laptop, there is a new version out but it now says its not compatible with this device.
it has been fine updating with all the previous versions.
The Aqara App technically isn’t verified for MacOS on the App Store, as its support is for iPad, but I am happy to say that it’s working on the Beta build of MacOS (Golden Gate). I (and Apple) will never recommend running a beta build, as it’s not an official/stable release and is meant for developers. If you do wish to try it out, it will need to be done at your own risk.
Yeah and you do know you have Apple home app witch also can let you see on the camera right?I have an iMac too but I do not see the point having aqara app on it since Apple home works and also aqara devices are exposed to HomeKit
Yes I know it works in Apple home and do you know the resolution is limited by Apple to 1080 so the quality of my 2.5k outdoor camera is much reduced and no way as clear and defined as when using the dedicated Aqara app.
I think your missing the point here, I was only reporting that the non technically supported Aqara app on the Mac no longer functions, and prior to 3 weeks ago it always worked and always updated fine.
We’ll update you Mac to the beta of the new MacOS and you will get those 2k resolution ether way this is not something aqara officially support.even the iOS app needs update for ios27.
Hi everyone, Aqara Support is already on the case.
Just to clear up the comments about it being an iPad app and not being compatible with Mac – that’s not really the issue here. Apple Silicon Macs can run iPad apps straight away, and Aqara has been doing this for ages. The app didn’t suddenly become permanently incompatible; it’s just a simple coding oversight introduced in version 6.3.3.
I had a look at the macOS crash report, and it seems the app is crashing straight away when it’s launched because it tries to call a specific new HomeKit tool (HMAccessorySetupManager). This tool works fine on iOS/iPadOS, but it doesn’t exist (or is restricted) in the macOS environment.
The developers forgot to add a basic platform check before calling this tool, so macOS panics and instantly kills the process.
It’s a piece of cake for their iOS team (they just need to add a couple of lines of code to check if the device is a Mac before running that specific function). I’ve sent them the exact stack trace showing the missing symbol, so they know exactly where the bug is.
Hopefully, they’ll push a hotfix update very soon.