Anyone have any updates on this? I played all day on launch with no errors and as of this morning I have been seeing this nonstop upon getting past the queue. Have tried pretty much every suggestion that i have found through google and these forums.
I don't think you would need to buy the game again on EA. Just create new accounts on both EA and Steam and link those. I'm not sure if the game you purchased would transfer to the new accounts though which is kind of another issue. So you might have to refund on old Steam account an repurchase on new account. Also these errors seem really weird so I wasn't even sure if it would work. That was why they suggested testing with EA play pro for less money then if it didn't work try and refund that. Very frustrating issue all around.
Im afraid that didnt fix it for me, I made a new ea account and got ea play, there is something else going on here
I've been aggressively trying to tackle this issue for the past few days spending close to 10-hours in various streams of EA tech support channels, and I think I'm getting close to finding the cause.
As you may read in other posts relating to this 'unknown issue', there is suspicion that the issue sits somewhere around account authentication.
My current theory is that after logging into Battlefield 6 on launch day (which would have used my account credentials to generate an authentication token), I changed my account details. Which was fine while my authentication token was valid.
Once that token expired however (potentially 24 hours later), Battlefield 6 was no longer able to create a valid authentication token which is leading to the error you're seeing.
You might ask "But why is it not using my current account credentials to generate the auth-token?"
I dug deeper, and found that multiple iterations of my EA ID were able to log into my account using my current password.
I suspect this is a back-end bug that could be causing all kinds of authentication troubles internally.
Unfortunately, EA doesn't seem to want to take this legitimate cyber-security risk seriously... So here we are. Public forums.
Check out the forum post below:
https://forums.ea.com/discussions/ea-app-technical-issues-en/security-vulnerability---multiple-ea-ids/12763070
I've been aggressively trying to tackle this issue for the past few days spending close to 10-hours in various streams of EA tech support channels, and I think I'm getting close to finding the cause.
As you may read in other posts relating to this 'unknown issue', there is suspicion that the issue sits somewhere around account authentication.
My current theory is that after logging into Battlefield 6 on launch day (which would have used my account credentials to generate an authentication token), I changed my account details. Which was fine while my authentication token was valid.
Once that token expired however (potentially 24 hours later), Battlefield 6 was no longer able to create a valid authentication token which is leading to the error you're seeing.
You might ask "But why is it not using my current account credentials to generate the auth-token?"
I dug deeper, and found that multiple iterations of my EA ID were able to log into my account using my current password.
I suspect this is a back-end bug that could be causing all kinds of authentication troubles internally.
Unfortunately, EA doesn't seem to want to take this legitimate cyber-security risk seriously... So here we are. Public forums.
Check out the forum post below:
https://forums.ea.com/discussions/ea-app-technical-issues-en/security-vulnerability---multiple-ea-ids/12763070
Great shout on this! Sent me off on a hunt looking into EA ID's and how they're associated to your account... Horrific findings 😅
Support team seemed interested in what I found, but was unable to escalate the matter (straight-forward answers all the way through, but dodged my questions regarding internal policies preventing them from escalating technical problems)
I spent yesterday doing the same thing, researching how ID'S work. At least someone on another thread got confirmation 13 hours ago that its an issue with EAs authentication and they are aware of it but that's all we got.
Yeah, it's pretty shocking.
I've been aggressively trying to tackle this issue for the past few days spending close to 10-hours in various streams of EA tech support channels, and I think I'm getting close to finding the cause.
My current theory is that after logging into Battlefield 6 on launch day (which would have used my account credentials to generate an authentication token), I changed my account details. Which was fine while my authentication token was valid.
Once that token expired however (potentially 24 hours later), Battlefield 6 was no longer able to create a valid authentication token which is leading to the error you're seeing.
You might ask "But why is it not using my current account credentials to generate the auth-token?"
I dug deeper, and found that multiple iterations of my EA ID were able to log into my account using my current password.
I suspect this is a back-end bug that could be causing all kinds of authentication troubles internally.
Unfortunately, EA doesn't seem to want to take this legitimate cyber-security risk seriously... So here we are. Public forums.
Check out the forum post below:
https://forums.ea.com/discussions/ea-app-technical-issues-en/security-vulnerability---multiple-ea-ids/12763070
Bumpinggggg. Got some good info below from some dedicated people that would like to play your game, in case anyone from EA wants to acknowledge that we have had $100 virtual paperweights for 4 consecutive days since release now
Anotha bump, another morning waiting for answers of any sort
The audacity to merge my thread without responding is absolutely unreal.
