You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When vpn region list is updated, browser should get latest one.
We have background update logic for it but we found that it's triggered 5h later after launching.
That means user should use more than 5h to get update.
We should try to update region data 5h later from the last update check.
It's difficult to have STR because region data is updated from guardian. #29719 is another related issue.
Steps to Reproduce
Launch brave with existing profile that has already purchased state
Relaunching again before 5h passed
Use more than 5h from launching
Actual result:
Region data is not updated - BR region is not visible from vpn panel
Expected result:
Region data is updated - BR region is visible from vpn panel
Reproduces how often:
Brave version (brave://version info)
Version/Channel Information:
Can you reproduce this issue with the current release?
Can you reproduce this issue with the beta channel?
Can you reproduce this issue with the nightly channel?
Other Additional Information:
Does the issue resolve itself when disabling Brave Shields?
Does the issue resolve itself when disabling Brave Rewards?
Is the issue reproducible on the latest version of Chrome?
Miscellaneous Information:
The text was updated successfully, but these errors were encountered:
launched Brave using --vmodule=*/vpn/*=2 --enable-logging=stderr --v=2
purchased, configured, and connected to Brave VPN
shut down Brave (and disconnected from Brave VPN)
advanced system clock by 6 hours
relaunched Brave
checked the server-region list
connected to various regions
Confirmed initial and subsequent retrievals of the supported region-list entries were downloaded successfully
US (West)
Brazil
Japan
Singapore
Initial connection/download:
[11618:259:0503/122619.691845:VERBOSE2:brave_vpn_region_data_manager.cc(263)] FetchRegionDataIfNeeded : Start fetching region data
[11625:19715:0503/122619.692017:VERBOSE1:network_delegate.cc(35)] NetworkDelegate::NotifyBeforeURLRequest: https://connect-api.guardianapp.com/api/v1/servers/all-server-regions
After 5 hours:
[11720:259:0503/182741.174268:VERBOSE2:brave_vpn_region_data_manager.cc(300)] ParseAndCacheRegionList : has regionlist: 1
[11720:259:0503/182741.174307:VERBOSE2:brave_vpn_region_data_manager.cc(215)] LoadCachedRegionData : Loaded cached region list
[11720:28675:0503/182741.174324:VERBOSE1:command_storage_backend.cc(852)] Current session files:
[11720:259:0503/182741.174388:VERBOSE2:brave_vpn_service.cc(621)] Schedule subscriber credential fetching after 49262.8 s
[11720:259:0503/182741.174974:VERBOSE2:brave_vpn_region_data_manager.cc(263)] FetchRegionDataIfNeeded : Start fetching region data
[11720:259:0503/182741.174974:VERBOSE2:brave_vpn_region_data_manager.cc(263)] FetchRegionDataIfNeeded : Start fetching region data
[11720:259:0503/182741.175299:VERBOSE1:profile_manager.cc(1286)] AddKeepAlive(Default, kBrowserWindow). keep_alives=[kBrowserWindow (2)]
[11729:20227:0503/182741.176130:VERBOSE1:network_delegate.cc(35)] NetworkDelegate::NotifyBeforeURLRequest: https://connect-api.guardianapp.com/api/v1/servers/all-server-regions
Description
When vpn region list is updated, browser should get latest one.
We have background update logic for it but we found that it's triggered 5h later after launching.
That means user should use more than 5h to get update.
We should try to update region data 5h later from the last update check.
It's difficult to have STR because region data is updated from guardian.
#29719 is another related issue.
Steps to Reproduce
Actual result:
Region data is not updated - BR region is not visible from vpn panel
Expected result:
Region data is updated - BR region is visible from vpn panel
Reproduces how often:
Brave version (brave://version info)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
The text was updated successfully, but these errors were encountered: