Edit March 27th.Hello folks, we've seen this thread blow up quite dramatically recently, and thank you to everyone for the info you've provided.However, we want to keep thing focused on the appropriate issues as much as possible. This thread is for gathering information from players whose accounts are currently unable to play. An easy way to check this is to have another account attempt to play on your system. If that one works without issue, you likely have what we're looking for. As noted in the tweet from Respawn, this affects just under 450 players: LinkHowever we're seeing a large influx of posts that appear to be about different issues related to connectivity. As the code:net error message can appear for a number of different connectivity issues, it's all too easy to get issues mixed up. In many cases standard connectivity troubleshooting can help, you can see our EA Help guide here. There's also an in-depth Community Troubleshooting guide here. We also are seeing players with long loading times on Steam. This is being looked into, we'll update this thread when we have info. If you encountered a "persistenceReadComplete" error message can you post here. If none of these address your issue, please post on an existing thread or create a new one if no appropriate one exists. You can use our Search function to search for existing threads that match your issue. Thanks. Original message:Hello folks, we're still looking into folks who are unable to log into specific accounts and receive Code:Net errors when they try to do so..If you're still affected by this, can you post your system and the relevant account name.System:Username:We know some of you have given this information previously, but it may help to get it again, and it's ok to have duplicates.

Hello all. This thread was created to gather information from players affected by a very particular type of account-specific issue, affecting around 450 players. Thanks again to everyone who provided info.The core cause of this issue appears to have been found and addressed at this point, and we have confirmations from those using the appropriate account. Those affected have now had their issue addressed, so we'll close this thread out now. Thank you again to everyone for their contributions. However we're still seeing a lot of posts about code:nets from accounts that are not locked out. The code:net error message is a generic one and can appear for many of reasons, and in short it just means that you have disconnected from the server. This can be due to server-side issues, but it can also be due to infrastructural or local issues. If you get a code:net you can often just reconnect, but if you frequently get them, it may be best to troubleshoot for any potential local issues. In many cases standard connectivity troubleshooting can help, you can see our EA Help guide here. There's also an in-depth Community Troubleshooting guide here. We also see that a number of players are indeed locked out with the following error message: "There was a problem processing game logic. Please try again. ui/social_event_popup.nut #145[UI] Bad hardware Type"This is being investigated and we will post on this thread when we have an update. If none of these address your issue, please use our Search function at the top of the page to search for existing threads that match your issue where you can post.If there are no existing threads that match your issue, feel free to create a new discussion!Thanks.

EA_David

Community Admin

4 years ago

Solved

Code:Net info gathering

Edit March 27th.

Hello folks, we've seen this thread blow up quite dramatically recently, and thank you to everyone for the info you've provided.

However, we want to keep thing focused on the appropriate issues as much as possible.

This thread is for gathering information from players whose accounts are currently unable to play. An easy way to check this is to have another account attempt to play on your system. If that one works without issue, you likely have what we're looking for.

As noted in the tweet from Respawn, this affects just under 450 players: Link

However we're seeing a large influx of posts that appear to be about different issues related to connectivity. As the code:net error message can appear for a number of different connectivity issues, it's all too easy to get issues mixed up.

In many cases standard connectivity troubleshooting can help, you can see our EA Help guide here.
There's also an in-depth Community Troubleshooting guide here.

We also are seeing players with long loading times on Steam. This is being looked into, we'll update this thread when we have info.
If you encountered a "persistenceReadComplete" error message can you post here.

If none of these address your issue, please post on an existing thread or create a new one if no appropriate one exists.
You can use our Search function to search for existing threads that match your issue.

Thanks.

Original message:

Hello folks, we're still looking into folks who are unable to log into specific accounts and receive Code:Net errors when they try to do so..

If you're still affected by this, can you post your system and the relevant account name.

System:
Username:

We know some of you have given this information previously, but it may help to get it again, and it's ok to have duplicates.

EA_David
4 years ago
Hello all.

This thread was created to gather information from players affected by a very particular type of account-specific issue, affecting around 450 players. Thanks again to everyone who provided info.

The core cause of this issue appears to have been found and addressed at this point, and we have confirmations from those using the appropriate account. Those affected have now had their issue addressed, so we'll close this thread out now. Thank you again to everyone for their contributions.

However we're still seeing a lot of posts about code:nets from accounts that are not locked out.

The code:net error message is a generic one and can appear for many of reasons, and in short it just means that you have disconnected from the server. This can be due to server-side issues, but it can also be due to infrastructural or local issues. If you get a code:net you can often just reconnect, but if you frequently get them, it may be best to troubleshoot for any potential local issues.

In many cases standard connectivity troubleshooting can help, you can see our EA Help guide here.

There's also an in-depth Community Troubleshooting guide here.

We also see that a number of players are indeed locked out with the following error message:

"There was a problem processing game logic. Please try again.
ui/social_event_popup.nut #145
[UI] Bad hardware Type"

This is being investigated and we will post on this thread when we have an update.

If none of these address your issue, please use our Search function at the top of the page to search for existing threads that match your issue where you can post.

If there are no existing threads that match your issue, feel free to create a new discussion!

Thanks.

7,547 Replies

Replies have been turned off for this discussion

Parrotox-Youtub
4 years ago
You guys are absolutely horrendous with your customers. I've been unable to get into my account for 5 weeks, 2 days ago I get a "suspension" for 72 hours, for something that happened in early February. Are you actually serious with your customer service? I get a suspension on top of code:net?! Despicable treatment of your customers. I lost 5 weeks on leveling the battle pass I paid for, missed out on 2 events I wanted to get the heirlooms for, like many others... how are you going to compensate us for this? Giving us 25 bp levels like with the other issues isn't going to cut it.
But since you are still investigating.
PC (origin)
parrotox-youtube
Thanks for your help, if it's coming.
viscalling
4 years ago
@EA_David Thanks for the new topic, David.

System: PS4
Username: viscalling
kittyakaidon
4 years ago
System: PS4
username: big_ShvwN

acc has two heirlooms been playing since season 0

CM Edit: Removed Spoiler tag.
ikia9595
4 years ago
System: PS5
Username: I-KIA

Edit: Please read my text. I’ve been playing since week 1 and I’ve got more than 450 Legendary skins, all Legends’ Heirlooms and 1000+ kills on every legend (excluding Fuze). I don’t want to miss Chaos Theory Collection Event cosmetics and Banglore’s Heirloom. I’ve been paying on this game alot and gave it a huge support, even I have a fan page for the game. Please don’t put me down, I’ve been facing this issue since the 6th of January, 2021. Its been more than two months already of being patient and waiting for the fix to be implemented. I really appreciate your hard work on this game and trying your best to fix these issues.
So can you please do me a favor and fix this issue ASAP because I don’t want to miss this event. I already missed two events.
Thanks again for you hard work.
fivebrendan10
4 years ago
@EA_David
System is Xbox Series X
Username for xbox is FiveBrendan
If not my console username it is tied to this account.
I know I've voiced this In the other channel, I sincerely hope that we can get everything we missed unlocked on our accounts, including the events to the accounts that have out a decent amount of money into the game.
Apologizes for the double post, but I know I wouldve purchased the anniversary event and all so I'm quite upset I missed out on that, the weapon skins that came in rotation, specifically the hemlock variant. Badges/trwckers/limited skins.
CM Edit: Merged posts.
Edit: Had this error since about 2-3 weeks prior to s8
IVIadman413
4 years ago
System: xbox series X
Username: FAMILIAR W0LF
RadioactiveLoli
4 years ago
System: PC
Username: RadioactiveLolis
I have not been able to play since February 10th, ever since the Hotfix patch.
kittyakaidon
4 years ago
system: PS4
username: big_ShvwN
acc has two heirlooms, i have been playing since season 0
OlimpioBoss
4 years ago
System Xbox one S
Username i SkillzZ L
JasperrNL
4 years ago
SYSTEM: PS4
USERNAME: jmaroos

This EA account I'm using now is the one connected to my locked Apex account/game.

To give you extra information on when the problem started, if it helps to troubleshoot, this is what happened:

Last match I played was on Thursday night March 11. Started a game in trios, but did not get any teammates. I did not want to play alone, and I was tired, so I closed the game directly using 'Close Application' in the Quick Menu, turned off my PS4 and went to bed.

Friday morning, March 12, I started the game. I reached the 'continue' screen and clicked X. The game appeared to attempt to reconnect me to the match (because I had not used 'Leave Match' the night before, but closed the game directly). That's when the infinity loading screen started. The screen goes black with the red loading icon for a good 30-45 seconds, then I get code:net. I have not been able to access the game since this started.

I'm a week 1 player, with thousands of matches played, as Apex quickly became the only game I've played over the past two years. I have supported this game at every step. I have three heirlooms, maxed out all the battle passes and have completed every single event. The game has basically helped me through a year of covid lockdown.

The absolute least I'm hoping you will do for all affected players is that we receive the rewards we missed out on during our time being locked out, based on how long it was. Most people I've spoken to about this bug say they have invested a lot of money in this game, as have I. That's okay, because I love the game, but if I cannot play, it's a different story. Hearing lots of stories of people having been locked out up to four months. That is a scary thought.

Thank you. Please fix this..