I'm posting here for general trouble shooting. I am not sure if this is an issue with Apex, or my home network. Everything was working normally up until the most recent update (Upheaval Patch) but now only one of the Xbox's in my home will connect in a match. We are on the same network, using separate profiles on each device, and we use the home sharing of Xbox live. We can join the same lobby but once the game launches only one of us makes it to the character select screen, and then into the match. When this happens, there is no error code, and the person who did not connect experiences a game freeze that often requires them to reboot the game.The confounding factor is that we tried to connect using separate Wifi networks and were able to enter the same match. We used a hotspot for one device, so the game experience was far from ideal. The fact that two networks were able to connect makes me think it may be an issue with our network, but we have not changed a single thing from when it was working normally. The only new addition is the Upheaval Patch. This is only happening with Apex. We've tested on other games (Xdefiant, & COD) and are able to join matches together normally. I cannot find any info about problems like this. Any insight would be extremely valuable as I'm kind of at a loss as to how to resolve this.Thank you all!

@BeastinRicky Yeah our third is on a separate network and always gets in. The two of us on the same network are always the ones who cannot load in. We have seen the "persistence transfer" a couple of times, but it's not an every time thing. Wildly frustrating.

@BeastinRicky We use T-mobile and it's the stock router they provided. We're considering getting a compatible third party router with more customization options. Don't really want to since it worked find prior to the Upheaval update, and have a similar hope to your that this problem disappears as randomly as it showed up.

@HammerStrike815 Not sure if you're still having the issue, but things worked fine for us for about a week and then on this past Friday, July 19, things stopped working again.The behavior is always the same. We get about 2-3 good games in, then after one game, our third player who is on a different network is hit with the "Persistence Transfer Cancelled" or whatever that is, and then after that one of the 2 of us on the same network always gets kicked loading into the game.@EA_Aljo We have a gaming router, uPnP, and again, I can't stress this enough, everything worked with our setup just fine for 2.5 years. This issue is perfectly correlated in time with the split 2 update.

My group is also affected by this. It's been accompanied by the persistence transfer cancelled error as well, and I saw today a thread implying that that has been patched and fixed for most users. https://answers.ea.com/t5/Technical-Issues/Disconnect-persistance-transfer-canceled/m-p/13896839/highlight/true#M204066Unfortunately, we tried to play today and immediately couldn't load into Firing Range together. We couldn't even play a single game today.@EA_Aljo: It's the same for us. Gaming router, uPnP set appropriately. Not a single setting changed from before the mid-season update and after. This literally only started with the mid-season update. What do we need to do to get this escalated? I've seen others on reddit also mention similar symptoms starting on the same timeline. It's not just us. Should we file a bug report?

Hi there, @HammerStrike815 I'd like you to go into the network settings on each console and check the NAT. It should be open or moderate. Also, check the UPnP setting on your router. That should be enabled.

Two Xbox Series X, Two Profiles, Same Network, and Only One Will Join a Game

11 Replies

EA_Aljo
Community Manager
2 years ago
Hi there, @HammerStrike815

I'd like you to go into the network settings on each console and check the NAT. It should be open or moderate. Also, check the UPnP setting on your router. That should be enabled.
HammerStrike815
2 years ago
@EA_Aljo Thank you for getting back to me!

My router does not have UPnP, and the settings are very limited. This historically has not been an issue. Both consoles NAT are Moderate.
BeastinRicky
2 years ago
I've been having the exact same issue. It will occasionally work for us for a few games, then the third person we play with (NOT on the same network) will get hit with the "persistence transfer" message and then every game we try after that finds that one of us on the same network gets kicked.
We've tried many many things, and haven't found a solution. It seems extremely tied to one of the recent updates as things worked fine for 2 years with the exact same setup until that point.
HammerStrike815
2 years ago
@BeastinRicky Yeah our third is on a separate network and always gets in. The two of us on the same network are always the ones who cannot load in. We have seen the "persistence transfer" a couple of times, but it's not an every time thing. Wildly frustrating.
BeastinRicky
2 years ago
Well, I'm glad to know we can commiserate in company. I'll let you know if we find anything that works, although I'm hesitant to waste too much time on this as it was exactly correlated in time with the latest update, and as I mentioned, the exact same setup worked without issue for 2 years.
If you don't mind saying, what router are you guys using? And do you happen to have Verizon as your ISP?
HammerStrike815
2 years ago
@BeastinRicky We use T-mobile and it's the stock router they provided. We're considering getting a compatible third party router with more customization options. Don't really want to since it worked find prior to the Upheaval update, and have a similar hope to your that this problem disappears as randomly as it showed up.
BeastinRicky
2 years ago
@HammerStrike815 We're on a netgear nighthawk and verizon, so I guess it's not an issue with some particular router or ISP.

We did just get to play like 6 games in a row and never ran into the issue. I don't know if it means that it is fixed, but you could maybe give it a go and see if we just got lucky. Maybe restart your router first for the good vibes.
EA_Aljo
Community Manager
2 years ago
@HammerStrike815

UPnP is a very basic feature that I've never heard of not being on a router. Try contacting your ISP to see if they can adjust this setting for you. This looks to be a network issue since both of you can be on different networks and still play. I also recommend getting a router with gaming features. Routers supplied by ISPs tend to be very light on those features as they are intended for basic web surfing.
BeastinRicky
12 months ago
@HammerStrike815 Not sure if you're still having the issue, but things worked fine for us for about a week and then on this past Friday, July 19, things stopped working again.
The behavior is always the same. We get about 2-3 good games in, then after one game, our third player who is on a different network is hit with the "Persistence Transfer Cancelled" or whatever that is, and then after that one of the 2 of us on the same network always gets kicked loading into the game.
@EA_Aljo We have a gaming router, uPnP, and again, I can't stress this enough, everything worked with our setup just fine for 2.5 years. This issue is perfectly correlated in time with the split 2 update.
ameske
12 months ago
My group is also affected by this. It's been accompanied by the persistence transfer cancelled error as well, and I saw today a thread implying that that has been patched and fixed for most users. https://answers.ea.com/t5/Technical-Issues/Disconnect-persistance-transfer-canceled/m-p/13896839/highlight/true#M204066
Unfortunately, we tried to play today and immediately couldn't load into Firing Range together. We couldn't even play a single game today.

@EA_Aljo: It's the same for us. Gaming router, uPnP set appropriately. Not a single setting changed from before the mid-season update and after. This literally only started with the mid-season update. What do we need to do to get this escalated? I've seen others on reddit also mention similar symptoms starting on the same timeline. It's not just us. Should we file a bug report?