Re: AjaxError/Error code 400 when attempting to use the Team Builder website

All these steps don't work for me. Can EA please investigate this more and come out with some sort of official statement please? I'm literally not even playing the game because I can't create my team for dynasty. I NEED my own team to play with.

Not sure if being reported anwhere else, but additioanlly now when I try to delete the teams that have been bricked by the 400 error I cant delete them either. So I have three teams with the same name, cant edit them, cant submit them, cant save them. When I start another team I get through so far and blam same error

So annoying, I know its probably hard to diagnose but I havent even played the game yet just trying to get this sorted out

None of this helped.  Still doesn't work.  Either the 404 error or just spins on uploading images.  Even using just the base EA logo didn't make a difference. 

And this is what it's all come down to. Why not tell us what's happening EA?

As much as I've been enjoying the game, I can't help but be candid in my honesty by saying this is drawing people.

I can't even hit the save button without this popping up. Is this just a wait and see if they fix it type situation?

I just finished my team after creating and importing a custom logo, spent 40 minutes customizing 3 uniforms sets. And making a custom field. For some reason it won’t let me submit my team. I’m on Mac I don’t now if could cause any issues.

It's now January days away from the NC game and this game still has this error and EA has never even addressed it.  I've been able to create a number of teams on the teambuilder site but the site itself has a number of crazy bugs and issues.  

I had a team I create a few months ago and couldn't remember why I never used it.  I tried editing over the team to create a new team.  I was able to edit everything and save it with no issues, however once I finished (after hours of work) I tried to submit the team and boom got hit with the team submission error bug.  It had been so long since I had seen it that I thought it was just crazy for me to still be seeing this bug months later.  I can't see how they refuse to fix bugs for the life of a title iteration.