Geo-location API acting up

man, i'm pulling my hair out with this. been trying to fix our 'what is my location?' tool for hours now and this geolocation feature is just driving me nuts.

the browser's navigator.geolocation.getCurrentPosition is either timing out constantly or giving wildly inaccurate coordinates, like miles off. it was working fine last week, but since yesterday, it's been a complete mess, especially on some mobile browsers. we rely on accurate location data, so this is a huge problem.

i've checked all the usual suspects: browser permissions are granted, network conditions seem okay, basic console logging just shows timeouts or weird numbers. tried increasing the timeout option, fiddling with maximumAge, even tried some IP fallback services, but the core browser geolocation API is just being super flaky. nothing seems to make it consistently work. here's what i'm often seeing:

// Scenario 1: Frequent timeout
GeolocationPositionError {code: 3, message: "Timeout expired."}

// Scenario 2: Wildly inaccurate data sometimes, even after a 'success'
GeolocationPosition {
  coords: GeolocationCoordinates {
    latitude: 0.00000,
    longitude: 0.00000,
    accuracy: 100000, // crazy high inaccuracy
    altitude: null,
    altitudeAccuracy: null,
    heading: null,
    speed: null
  },
  timestamp: 1678886400000
}

// Scenario 3: Occasionally just hangs and never resolves

what am i missing here? are there any super specific debugging steps or common pitfalls with browser geolocation APIs that cause such intermittent, frustrating failures? i'm desperate for any insights.