Timeout resolving device scoped access token

Me and Our Team has some problem about account.

It's very similar to this case : https://communityforums.atmeta.com/t5/Get-Help/Timeout-when-resolving-device-scoped-access-token/m-p/1034267

I developing with Meta Quest2 and I use recent OS

These are the lists I've done.

• Quest2 FactoryReset(Twice)
• Mobile App(Data Clear & Cellphone restart)
• Router restart
• Check my Account(My account in Meta)

This is my CompanionService dumpsys

------------------------ BEGIN SERVER STATE ------------------------
------------------------ BEGIN COMPANION STATE ------------------------
Battery Level: 100
Charging: true
Fast Charging: false
Wifi enabled: true
Wifi configured: true
Wifi connected: true
Wifi server reachable: true
Wifi IP address:
Wifi device name:
Controller primary configured: true
Controller primary connected: true
Controller secondary configured: true
Controller secondary connected: false
Controller other configured: false
Controller other connected: false
OTA available: false
OTA ready: false
HMD Update percentage: 0
PIN configured: false
PIN locked: false
Horizon logged in: true
Horizon Meta logged in: true
Developer mode: false
ADB: true
HSW complete: true
NUX complete: true
NUX State: NUX_COMPLETE
Headset State: STANDBY
Provision type: FACTORY_PROVISIONED
Provisioned serial:
------------------------- END COMPANION STATE -------------------------
------------------------- END SERVER STATE -------------------------

This is a reference video I took.

https://youtube.com/shorts/H11RP6gGJ9U
(I replaced it with a link because the image is short.)

In addition, Some of our users are also experiencing this symptom.

But when I used my personal hotspot instead of my company's Wi-Fi, it worked fine for a while.

Is there a separate router setting for Meta api reception?

I hope we can get an answer to this problem A.S.A.P because the users are experiencing the same problem.

Thanks for read!