Tizen穿戴式Web应用模拟器获取地理位置无回调响应问题

I’ve run into similar issues with the Tizen Wearable Simulator’s geolocation API before, so let’s walk through why your callbacks aren’t firing (you’re seeing "HERE" and "1" but no "Success"/"Error") and how to fix it.

Common Causes & Solutions #

1. The Simulator Needs Mock Location Data #

The Tizen Simulator doesn’t pull real GPS data—it relies on you setting up mock location coordinates manually. If no location is configured, the getCurrentPosition call might hang instead of triggering a callback.

Here’s how to set it up:

• Open your Tizen Simulator window.
• Look for the Emulator Control panel (usually on the right side; if it’s hidden, go to Window > Show View > Emulator Control).
• Switch to the Location tab.
• You have a few options:
  • Type specific latitude/longitude values and click Set
  • Use the interactive map to click a location
  • Load a GPX file to simulate movement over time
• After setting a location, restart your app and test the geolocation function again.

2. Double-Check Your Privilege Configuration #

Even if you think you’ve added the location privilege, it’s worth verifying your config.xml to make sure it’s correctly declared:

<tizen:privilege name="http://tizen.org/privilege/location"/>

Also, ensure your app’s target Tizen version matches the simulator’s version—mismatches can cause unexpected API behavior.

3. Simplify Your Callbacks to Rule Out Scope Issues #

Your current callback functions are minimal, but let’s expand them to get more context and rule out any hidden scope problems. Replace your getCurrentPosition call with this:

navigator.geolocation.getCurrentPosition(
  function(position) {
    console.log("Success! Lat: ", position.coords.latitude, " Lon: ", position.coords.longitude);
  },
  function(error) {
    console.log("Error Details: Code ", error.code, ", Message: ", error.message);
  },
  { maximumAge: 60000 }
);

This will give you detailed logs if the callback does fire, which helps confirm whether the issue is with the simulator or your callback logic.

4. Check for Background Restrictions #

If your app is trying to fetch location while in the background, Tizen Wearable has strict limitations here. Make sure your app is in the foreground when testing—background location access requires extra setup like declaring the http://tizen.org/privilege/background privilege and configuring background modes in config.xml.

Quick Test Tip #

After making any changes, restart both the simulator and your app. The simulator sometimes caches old settings, so a fresh start ensures your updates take effect.

内容的提问来源于stack exchange，提问作者Scott Foster