The current implementation attempts to track user location on the server-side using the fetch API. This causes errors because:
The server environment does not have direct access to browser APIs like navigator.geolocation.
Using fetch on the backend for location tracking is unreliable and often fails.
Impact:
User location data cannot be fetched correctly.
Some features relying on geolocation (e.g., personalization, analytics, or logging) may not work as expected.
Steps to Reproduce:
Run the backend service.
Trigger the location tracking functionality.
Observe the error from the fetch API in logs.
Expected Behavior:
User location should be fetched reliably and without server-side errors.