Nothing, yet.Any update on this? Nothing on Apple's website.
Nothing, yet.Any update on this? Nothing on Apple's website.
Any update on this? Nothing on Apple's website.
Any update on this? Nothing on Apple's website.
Would be crazy to think the reason Apple hasn't responded about this issue is if they actually don't know the cause...
Maybe?? There's been plenty of long-standing bugs Apple is either incapable or unwilling to fix. Not saying they're not aware, but maybe they're still trying to figure out RCAUnlikely, I think.
Maybe?? There's been plenty of long-standing bugs Apple is either incapable or unwilling to fix. Not saying they're not aware, but maybe they're still trying to figure out RCA
Maybe? It honestly depends on how many people were genuinely impacted by this, and yes, 19 pages on a Mac Forum is a lot! But in the grand scheme of things, to Apple, is it a lot? I look at all sorts of different issues with ongoing bugs that have been happening for years, been reporting them in the Feedback app, and some don't even get acknowledged at all, while some say "more than 10" and have been open for 2+ years with no resolution.Maybe they’re still figuring it out, but I seriously doubt they’re unaware of it.
It hard to know how many are seeing this. I’m watching the thread to see what’s going on but no one I know of has had this happen to them so far. (Crossing fingers)Maybe? It honestly depends on how many people were genuinely impacted by this, and yes, 19 pages on a Mac Forum is a lot! But in the grand scheme of things, to Apple, is it a lot? I look at all sorts of different issues with ongoing bugs that have been happening for years, been reporting them in the Feedback app, and some don't even get acknowledged at all, while some say "more than 10" and have been open for 2+ years with no resolution.
I'm just saying with this, and seeing that there truly is no rhyme or reason to WHY this is happening, just that people are inconvenienced and still able to "resolve their problem", I wouldn't hold out hope as to why this has happened.
Same! Just like many others here, I have a super old @Mac.com account setup with 5 Devices on my end along with Family Sharing. Folks kept claiming THAT was the reason why or whatever.. But I'm totally fine!It hard to know how many are seeing this. I’m watching the thread to see what’s going on but no one I know of has had this happen to them so far. (Crossing fingers)
Maybe? It honestly depends on how many people were genuinely impacted by this, and yes, 19 pages on a Mac Forum is a lot! But in the grand scheme of things, to Apple, is it a lot? I look at all sorts of different issues with ongoing bugs that have been happening for years, been reporting them in the Feedback app, and some don't even get acknowledged at all, while some say "more than 10" and have been open for 2+ years with no resolution.
I'm just saying with this, and seeing that there truly is no rhyme or reason to WHY this is happening, just that people are inconvenienced and still able to "resolve their problem", I wouldn't hold out hope as to why this has happened.
I voluntarily changed mine in January, January 2024..Same! Just like many others here, I have a super old @Mac.com account setup with 5 Devices on my end along with Family Sharing. Folks kept claiming THAT was the reason why or whatever.. But I'm totally fine!
If you sign in at the Apple IT Security Page, there's a card that says when the Password was last changed, and in my case it was roughly 2 years ago. Not sure if there's a limit now on Passwords before they're set to expire, if that's now a thing?
I realised nearly 10 days later that my app-secific IMAP password died with this BS.
And I believe Apple has kept its silence on the topic.....
Interesting point of view.I wonder if having "app-specific" passwords set on your account could be the trigger?
These "app-specific" passwords are not particularly safe as they bypass a lot of security provisions to allow third-party apps to access your data. The passwords are not app specific either, any of these passwords can be used by any app to pull in emails, contacts, calendars when setup - without requiring 2FA.
I'm amazed Apple hasn't implemented an alternative authentication solution that negates the need for these passwords.
Folks kept claiming THAT was the reason why or whatever.. But I'm totally fine!
Interesting point of view.
This could explain why I had to change the password but wasn't required for my husband and other members of my family who I know don't have app-specific passwords. Though the next day my husband had a prompt [a window asking allow or cancel] but it was too similar to the March phishing attack and restarting the phone made the prompt disappear and never come back again, so far.
This made me think that there was another phishing attack and Apple, being aware of that, forced a lot of users to change their passwords. Lots of questions and alas no answers.
Anyhow if it was because of a specific app why did we need to get a new password for those too?
If it is risky they would have changed something...you wish..
For basic security reasons most of us who use app specific passwords generate a unique one for each application. So when this event happened we had to make new ones for each application, not a single one to deploy many times.Your so-called specific app password can be used in any app, anytime, as long as the password is known and not disabled. Generate a password and try using it in ten different email clients. All ten email clients will have full access to your email, without needing any kind of 2FA intervention.
Resetting the master Apple ID password wipes them out so that no app can use that app-specific password anymore.
If Apple decided they didn't want to make a big song and dance about whatever has happened, for whatever reason, this more covert approach would make sense.
...and it isn’t a sustainable strategy.
You would think not, expect Apple has a very large number of hardcore disciples who would find a way to defend them even if they kidnapped their first born. For every customer Apple loses, they'll recoup from the faithful by charging even more for even less.
For basic security reasons most of us who use app specific passwords generate a unique one for each application. So when this event happened we had to make new ones for each application, not a single one to deploy many times.
I have five app-specific passwords and have not encountered the issues discussed here. My wife has no app-specific passwords but her account was affected.Has anyone WITH app-specific passwords NOT encountered the issues discussed in this thread?
I have five app-specific passwords and have not encountered the issues discussed here. My wife has no app-specific passwords but her account was affected.