And nothing couldn’t get ruled out on safe mode right, bruv?Admin.
So it seems like it’ll be a bug fix on macOS 26.2 public release. Hopefully that fix happens in that update.Ok, so I have an update.
Spoke with advisor, and she said that other people are calling about this issue. She said that when this happens, the engineers get on the case, and they actively work on a fix.
She said we have done everything we can do, so now we just have to wait for the engineers to rectify it.
She said usually a fix comes with a software update, or it is addressed at the server end.
She said it shouldn't take long, now.
She is calling me on Tuesday afternoon, with an update.
Hope this puts other people's minds at rest.
Thanks, mate 👍🏼.And nothing couldn’t get ruled out on safe mode right, bruv?
So it seems like it’ll be a bug fix on macOS 26.2 public release. Hopefully that fix happens in that update.
No problem 😉 glad to help you out with it.Thanks, mate 👍🏼.
I’m not interested in buying straps, anymore.No problem 😉 glad to help you out with it.
What strap do you have on your Apple Watch right now? I haven’t seen you active as much on the Apple Watch threads, had you slowed down on collecting straps? Same with me as there wasn’t any good holiday deals on it
I have too many too. And I have been wearing my plum strap a lot.I’m not interested in buying straps, anymore.
I have 90, and that is more than enough.
I could happily stick with about 10 of my straps. Most were bought out of addition. Anyway, never mind.
At the moment, I’m wearing the pomelo/tan sport loop. It’s one of the straps I was going to send to you.
So the key question is: have they identified the root cause? Once they have, they can develop a fix.Ok, so I have an update.
Spoke with advisor, and she said that other people are calling about this issue. She said that when this happens, the engineers get on the case, and they actively work on a fix.
She said we have done everything we can do, so now we just have to wait for the engineers to rectify it.
She said usually a fix comes with a software update, or it is addressed at the server end.
She said it shouldn't take long, now.
She is calling me on Tuesday afternoon, with an update.
Hope this puts other people's minds at rest.
One senior adviser told me he has a “carbon copy” of the issue with another customer, which happens to be with an iMac.So the key question is: have they identified the root cause? Once they have, they can develop a fix.
If it's client side, don't expect it til26.3 as .2 is done, if it's server side, we'll, can happen anytime.
You might also ask if it affects iMac only or all Macs?
Today, I noticed activation lock was enabled (idk when to exact)without any changes on my part, so it seems to be a server issue.Pleased for you, mate.
This gives me hope that it's simply a glitch, and nothing more serious.
Keep us updated, please, and I'll do the same.
Just checked mine, and it's still off.Today, I noticed activation lock was enabled (idk when to exact)without any changes on my part, so it seems to be a server issue.
The find my is working fine on my MacBook Pro. It still also gives location when I travel with my MacOne senior adviser told me he has a “carbon copy” of the issue with another customer, which happens to be with an iMac.
However, in this thread I believe others have the issue on MacBooks.