Description of problem:
Geo location isn't working in F37 Anaconda for me:
always defaults to en_US (ie English (United States))
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. boot F37 Live image outside USA
2. check detected default language locale
English (United States)
Geo location to work like for F36 (eg anaconda-36.16.5-2.fc36)
In my case it should be English (Singapore).
The geo location doesn't seem to always kick in, but I just tested with Fedora-Workstation-Live-x86_64-37_Beta-1.5.iso and I was correctly detected to be in the Czech Republic.
This is unfortunate, but not unexpected. Geolocation was recently modularized and we dropped some waiting, as it did not make any difference during initial testing. Looks like that does matter elsewhere :(
This fixes the problem, enough for f37. https://github.com/rhinstaller/anaconda/pull/4328
For rawhide we'll want to refactor more which isn't needed in f37.
Beta is signed off, so this can't go into it. Moving to proposed Final FE, though of course it can go in before the Final freeze with no FE status needed.
FEDORA-2022-68907aa5e8 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-68907aa5e8
Discussed during the 2022-09-19 blocker review meeting: 
The decision to classify this bug as an "AcceptedFreezeException (Final)" was made as it is a noticeable issue that cannot be fixed with an update.
FEDORA-2022-68907aa5e8 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-68907aa5e8`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-68907aa5e8
See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Confirming this looks fixed indeed in anaconda-37.12.5-1.fc37
FEDORA-2022-68907aa5e8 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.