Same here in AU, this happened to me about 8 hours ago. Standard reset procedure worked.
Now when trying to configure a Recovery Key from my 2021 iPad Pro I’m told that I can’t do that from ‘this new device’ of mine. ¯\_(ツ)_/¯
And when I try it from my iPhone I have to wait an hour because of Stolen Device Protection. Apparently I’m not at a ‘familiar location’. I’m at home. I work from home. This phone is in this house for 99% of the time.
I loved Stolen Device Protection when I first heard about it. And now I've wasted hours of my life dealing with it as part of the "Daily Lockout".
And tech companies again demonstrate that they are "all about the user" by providing no clarity, acknowledgement, or empathy around the issue. It's depressing.
Perhaps this is real talent in tech: to make things seem rather than be, and to build ways to avoid service and accountability unless it leads to max profit.
I shouldn't be surprised each time this happens, but optimistically I still am.
Check if you have location services -> system services -> significant locations On. If it's disabled then effectively you have no "familiar location" as far as iOS is concerned
And SWT is built on calling system native components. Of course the “text editor” ends up being one large custom component that has nothing to gain from being in a “native” View.
All of that said, SWT and Eclipse do know that they are running on MacOS. It would be possible to mimic the same behavior, but that’s hard to do because there are so many minute details per platform.
Often you also have the CI system designed in a way to verify a “from scratch” build that avoids any issues with “works on my machine” scenarios due to things still being cached that shouldn’t be there anymore.
With SO you also have no guarantee that the person has the license to put that snippet. Even that could have been copied from somewhere else.
A customer was scanning for and banning SO, if that was the only determined source.
The amount of times I’ve put or seen @Transactional in the wrong place where it was never called and silently ignored is pretty high. It always led to very long debugging sessions. Especially if you touch that code once a year.
