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
Describe the bug
The script is failing to get the time from the API.
To Reproduce
Steps to reproduce the behavior:
Make RealTimeSync true in config.
Start or Restart server.
Check Server Console.
Expected behavior
Real time should be synced from API and not have to fall back to local.
Screenshots
Questions (please complete the following information):
When you last updated: Fresh install of latest release.
Are you using custom resource? All default from a fresh qb-core install.
Have you renamed qb- to something custom? No.
Additional context
This issue is here:
Should be "https://".
EDIT:
After more testing, and changing this to https I found that the error would still occur at random, just not after every restart, as in the results before the change.
I added to the failedCount and Wait because it seems the actual deeper issue stems from the API that is being used, as it sometimes randomly can have a longer than usual delay to load the location and time information. The fix is in pull requests.
The text was updated successfully, but these errors were encountered:
Describe the bug
The script is failing to get the time from the API.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Real time should be synced from API and not have to fall back to local.
Screenshots
Questions (please complete the following information):
qb-
to something custom? No.Additional context
This issue is here:
Should be "https://".
EDIT:
After more testing, and changing this to https I found that the error would still occur at random, just not after every restart, as in the results before the change.
I added to the failedCount and Wait because it seems the actual deeper issue stems from the API that is being used, as it sometimes randomly can have a longer than usual delay to load the location and time information. The fix is in pull requests.
The text was updated successfully, but these errors were encountered: