Does anyone else have trouble getting the Wyze app to quit on the M1 Mac? Love that it works but I have to use the Force Quit every time.
I just had to go to the applications folder, remove the Wyze app manually, then reinstall it, and everything is back to normal, maybe even better. Seems more responsive.
Moderator Note: Personal information has been manually removed from this post. Such information often gets included inadvertently in an email signature block when replying by email. The forum software attempts to automatically remove email signatures but it is not always successful. When replying to the forum by email, it is best to remove the signature block yourself before sending.
1 Like
Whao!
Thank you!
1 Like
Iāve been playing with this. Seems like I do have to force quit if I actually want to kill the app. āQuit Wyzeā just closes the main window. Not a big deal for me, but I do see it.
1 Like
Hey there
as it seems with the latest version I canāt open the wyze app on my M1.
macOS Monerey
Version 12.4 (21F79)
anybody else got the same issue?
I bought a MacBook Pro in Dec 2022 because I saw this Wyze thread. The MacBook came with a version of Monterey installed (canāt remember what versions initially), and the Wyze app ran like a champ. I also installed a couple of other iOS apps that ran ok also.
I hadnāt run the Wyze for a while, but I noticed that neither the Wyze app nor a couple of other apps would run after I installed a particular version of Ventura. I would click on them and NOTHING happened. Looked in system log to no avail.
I opened tickets with Wyze and Apple to no avail. Finger Pointing at its finest. Iām a retired IT professional with hard core debugging experience on numerous platforms going back to the 80ās. The amount of support you get these day is dismal at best everywhere which is frustrating. (Note: I donāt consider a polite conversation with a Level 1 vendor specialist who canāt offer any real support but who answers the phone and creates a ticket quickly good support. I consider the satisfactory recognition of problems passed to a higher level of expertise good support)
I came up with the idea of trying to open the iOS apps from the terminal prompt to see if any errors popped up. I did get the same error on all iOS apps about a function in the SDK that was deprecated at one point across the board. Passed that info on but NOBODY cared as far as the vendors were concerned. I suspect that info was never passed on to competent technical professionals and I was corresponding with āHuman Botsā whose job was to read items off a checklist and try to blow me off and send me on nonsensical tangents.
I have seen VERY FEW posts on this. There were posts about a year and a half go talking about apps not running when SIP (System Integrity Protection - restricting apps from modifying systems control blocks), and those folks indicated that when they turned off SIP using the ācsrutilā command things stopped running, and they had to turn it back on.
When I noticed my iOS not loading, I noted that SIP was on, as it should be, I thought about turning it off and back on, but the posts I saw appeared to very terse and cursory in that they did not really offer any expanded explanations ( I hate going down rabbit holes based on terse information).
So yes, there are others of us out there suffering from this problem but it hasnāt caused enough of any uproar to get the attention of the vendors!
I know this wonāt be a satisfying response, but Wyze only works towards compatibility with two operating systems: iOS and Android.
They only support pure versions of those OSās, so for something like Android, compatibility with something like a Fire tablet is not guaranteed, nor supported if it is broke.
Same for iOS ā if an operating system or app is emulating either Android or iOS, then compatibility isnāt guaranteed. The M(x) series of Macs are emulating iOS. Therefore, the emulator needs to get the emulation right.
Now, if you have the same problem on a pure iOS or Android device, please report it. Unfortunately I donāt think they have the manpower to chase emulations where it isnāt broke on a pure version of the original OS running on a proper device.
Pretty much dismissing your premise for a couple of reasons.
-
iOS apps are designed to run natively on Apple Silicon. Apple Silicon is the custom system-on-a-chip (SoC) architecture developed by Apple, So the app object code is not really emulated.
-
I believe the vendor, however, has to prepare the apps to run on Apple Silicon before they can be loaded on MacOS as you canāt willy nilly load any iOS app on MacOS as the aps store differentiates between iOS apos that should be able to run and that apps that will not runā¦ There are tools built into Xcode to allow for this preparation.
-
With this being said, a vendor/developer makes a decision to either allow or disallow the iOS app to be loaded from the aps to an MacBook with a supported Apple Silicon process which supports the same object code an an iPhone or iPad. Keep in mind that while the Apple Silicon processors license ARM technology, they are proprietary in design to alliw for this type of interoperability.
-
Also, assuming the app could somehow be loaded against a vendorās wish, the vendor should be able to block it from running by throwing an exception and providing a coherent error message indicating the app shouldnāt be run on an Apple Silicon processor.
āAppleās framework allows you to detect if the app is running as an iOS app on Mac by using the process info flag isiOSAppOnMac ā
- WYZE needs to either block their app from being loaded an M1 mac or support it. They need to make their policy on that clear. I was under the impression from Level 1 support that it was supported and that it was an Apple issue.
Regarding having the manpower debugging product issues:
- Wyze is marketing so many products that they are way past the mantra of ādo a few things and do it wellā. Support for their initial core products becomes dismal at that point.
My previous dialog pretty much throws blame in Appleās corner, as ALL iOS Based APPS would NOT Execute after installed. That means that the entry point to the Wyze app code was more than likely not entered, just like the other apps, and was not even given a chance to run.
I think Wyze allows loading everywhere, but otherwise ignores it ā up to the emulators to do what a pure iOS device (or Android) does for them.
I disagree with your re-write. While that would be wonderful, then there would be no space between running on an iOS device and an emulation, which is really what running on the the M(x) series is. The hardware for one is not the same, so a translation would need to be written.
Ran across this today:
A direct hit on my issue. Iāve been searching on this for a long using my error message below with no luck.
Hit paydirt on my last search
Last login: Wed Apr 19 11:03:11 on ttys000
~ % sudo open /Applications/Wyze.app/
_LSOpenURLsWithCompletionHandler() failed with error -10671.
f~ % sudo open /Applications/VOA.app/
_LSOpenURLsWithCompletionHandler() failed with error -10671.
So did changing āStartup Security Policyā from āPermissiveā to āReducedā fix the issue? If so explain the mechanics of that for others. 
1 Like
Didnāt work but led me down a new path which Iāll be happy to share if I get any response at all to my new Wyze ticket. Not holding my breath with these folks
[Wyze Ticket xxxxxxx] Weāre working on your request: Wyze ios app Widget and Fairplay Decryption failing xpcproxy startup on macos m1 Ventura