@EA APEX Invalid Token Solution

@EA

These Apex Invalid Token errors are because ISPs are using 464 translation and you don't support IP changing or IPV6 native.

I'm the owner of one such ISP and we use 464XLAT. (also called PLAT and CLAT. We specifically use a software called Jool that runs on Linux)

To understand the problem you need to understand how most ISPs in 2020+ do their networks. Typically we give each user a block of IPV6 addresses and no IPV4 public address. This is because the IPV4 pool is depleted. We then have a block of IPV4 that gets used when a customer hits a website that doesn't support IPV6 with their server, software, website or tool. That causes users to pull different ipv4 addresses from the pool, kind of at random.

The problem your users are facing is caused by the fact that your servers are hosting everything on ipv4, or the customers using them are on ipv4 primarily and you have no built-in way to allow this 464 translation because the IP address of the user is changing because of the number of servers you're having them go through. This is why a static IP address works and this is why a VPN works. 

There's probably very little you can do about the issue except quit using networking practices from 2005 and learn how to support ipv6 better. 

As stated before, a user can work around this a number of ways:

1. They can manually set the APN if they're using a cellular-based internet service provider. 

2. Their ISP can provide a static IPV4 address

3. They can use a VPN to circumvent the changing IPV4 address. 

But these are work arounds that are only necessary because you built-in code that prevents IP changes while connecting to game lobbies and you provide little to no support for IPV6. 

If you want to fix these errors, you need to get your developers on board with how a large percentage of the internet is running right now and how the internet will continue to evolve and move towards IPV6 in the future.