I had an issue a few days ago with a Schlage Encode Plus lock. Apparently, it had tried to update the firmware and encountered an issue. It dropped off the network with "not responding." I factory reset the lock and reset it back up, but when I try to add it to HomeKit, nothing works. It seems the "add accessory" piece of HomeKit is "stuck." The camera will no longer scan the QR code and when I try to add the device manually, I just get a spinning circle and I'm never given the opportunity to add it.
I do see some data in console.log regarding HomeKit:
cannot add handler to 3 from 3 - dropping
There is another error message but it just says so I'm not sure what that could be.
This has been reported in Feedback Manager. Any tips on how to clear this apparent logjam?
Post
Replies
Boosts
Views
Activity
I'm having an issue with Sonoma beta 4. It's been present in all of the Sonoma betas thus far, but it seems to be getting worse.
The "searchpartyd" process keeps spinning up and taking an enormous amount of CPU and energy. This happens while on battery and also on power.
I've collected spindumps and all the data I can and filed a bug report with Apple. So far, no response.
Has anyone else experienced this?
In console.log, I see that it is complaining quite vividly about "BeaconStoreActor" issues:
No BeaconStoreActor available!
Unable to get BeaconStoreActor!
I suspect it is an issue with FindMy and possibly an AirTag, but there's quite little to go on.
I'm developing an iMessage extension that makes some ASCII art out of text entered by the user. It needs to set the message text to a fixed-width font to look correctly. Does anyone know how to get MSConversation (insertText) or MSMessage to utilize a fixed-width font with a string?
Thanks.
This has happened on my previous XS Max running 14.1 and is now occurring with my iPhone 12 Pro Max on 14.2.1.
If I enable or disable wifi calling on the phone, I can receive phone calls for about 30 minutes. Afterwards, all remaining calls will go straight to voice mail. Toggle wifi calling on or off again and it will work again for another 30 minutes.
I have tried:
Reset network settings
Wipe and reload
Toggle airplane mode
Toggle cell
Turn roaming on or off
The only thing that seems to impact this is toggling wifi calling.
From searches on the net, this has been going on for quite some time. Did anyone ever pin this down?