TeamBuilder Error 105
I am unable to submit teams in EA SPORTS College Football 27 TeamBuilder.
Submission hangs during "Compositing Uniforms" and eventually returns:
[105]: An error occurred during team submit.
I inspected the TeamBuilder network requests using Chrome Developer Tools.
Helmet, Jersey, and Pants assets are successfully being created by EA and assigned asset IDs, but all of them remain in the following status:
profanityStatus: "PROFANITY_PENDING"
This does not appear to be specific to one custom team, logo, uniform, or uploaded asset.
Testing performed:
- Existing custom team, Hartwell Greyhounds: Error 105
- Newly created test team using essentially default EA content: same result
- Test team only has Home and Away uniforms: same result
- Normal Google Chrome session: same result
- Chrome Incognito session: same result
- Helmet assets remain PROFANITY_PENDING
- Jersey assets remain PROFANITY_PENDING
- Pants assets remain PROFANITY_PENDING
- EA backend successfully returns an assetId for the generated assets
- EA backend successfully returns a nonce identifying Helmet, Jersey, or Pants
- Submission remains at "Compositing Uniforms" before eventually failing
Error Code:
105
Date:
September 9, 2026
Approximate Time:
6:40 PM to 7:00 PM Central Time
Platform Used for TeamBuilder:
Windows PC
Browser:
Google Chrome
EA ID:
grunt11b_vandy
Additional Information:
Because this issue reproduces on a newly created test team using default EA content and only Home/Away uniforms, it does not appear to be caused by the original team's custom logos, uniforms, apparel brand, roster, or other team-specific content.
The same issue also occurs in Chrome Incognito mode, which makes a browser cache, cookie, or extension problem much less likely.
During submission, EA's asset service creates the Helmet, Jersey, and Pants assets and returns asset IDs, but the profanityStatus for every uniform component remains PROFANITY_PENDING.
Please escalate this report to the TeamBuilder engineering team and investigate whether the TeamBuilder asset moderation, uniform compositing, or submission service is failing to transition generated uniform assets out of PROFANITY_PENDING.
I can provide screenshots from Chrome Developer Tools showing the EA API responses and the PROFANITY_PENDING status.