Connected Franchise: Ending a game and getting kicked to main menu on Xbox One

I am having the same problem.  Driving me crazy.  Is this doing it on the PS4 also?

I have not figured out a solution to this one yet, but it's happened to me 3 times over the course of my first season, and I've been playing 15 minute quarters, so yeah, I know your pain.

Spent an hour with EA support going thru a **bleep** load of steps, hoping it fixed it.  They said it was some bad data or some **bleep** like that.

What exactly did you have to do to fix it?

---

@Dmedicus13 wrote:

Spent an hour with EA support going thru a **bleep** load of steps, hoping it fixed it.  They said it was some bad data or some **bleep** like that.

---

Luckly i saved my chat.  Also you will loose anything you have played so be prepared.

Power Cycle your X box:

While the console is on, press and hold the console’s Xbox button for 5 seconds.
The console will power down.
Unplug the power cord.
Wait 30 seconds.
Plug the power cord back in then turn the console back on by touching the Xbox button
Note: If your console is set to the Instant-On power state, the above steps will shut the console completely off and will not enable Instant-On or the ability to turn on your console by saying ‘Xbox On’ until it reboots.

Clear your cloud saves:

Settings -> Network Settings
Advanced Settings
Alternative Mac Address
Clear

shut down the console.
disconnect the power cord from the back of the Xbox One and wait two minutes.

plug the power back in and wait for the power bricks light to go from White to Orange.

Settings ->Select Disc & Blu-Ray
Persistent Storage
Clear Persistent Storage

At last please uninstall and re install your game.

Just FYI it didn't work.  Not a happy camper right now.

Still having issues...

This is garbage.  I had the exact same issue last year.  I hadnt seen this problem this year until last weekend.  I have had 5 of the last 8 games i played do this. I think it may be time for me to move on to a different game

I honesty think it has something to do with the update/patch they did.  I didn't start having this problem till then.