Acknowledged
CIQQA-3741

[BUG] [Fenix8Pro] [Fr965] Waypoint intent broken

Problem: When using the PersistedContent Monkey C API to launch an activity enriched with one waypoint navigation information from within a Widget, the activity gets started, but no navigation information is taken over.

Same behaviour does work for Courses or when the same Waypoint (Location/Favorite) is selected from an activity navigation menu manually.

Precondition: widget did download a fit file with locations and content type Fit using the Webrequest API to a http webserver

Further observations:

  • Works on Edge830: Feature is working as expected on the Edge830 device (9.75 firmware)
  • Not a name/id matching issue: The bug does not target to address the issue of name/id matching
  • Same behaviour does work for Course type
  • Works when the same Waypoint (Location/Favorite) is selected from an activity navigation menu manually.

Code:

function launchWaypointByName(waypointName as String) as Boolean {
  if (!(Toybox has :PersistedContent) || !(PersistedContent has :getAppWaypoints)) {
    return false;
  }

  var waypoints = PersistedContent.getAppWaypoints();
  if (waypoints == null) {
    return false;
  }

  var waypoint = waypoints.next();
  while (waypoint != null) {
    // take first matching object
    if (waypoint.getName().equals(waypointName)) {
      try {
        // Check if toIntent method exists (API 2.3.0+)
        if (waypoint has :toIntent) {
          var intent = waypoint.toIntent();
          if (intent != null) {
            System.exitTo(intent);
            return true;
          }
        }
        System.println("Waypoint toIntent() not available or returned null");
        return false;
      } catch (ex) {
        System.println("Error launching waypoint: " + ex.getErrorMessage());
        return false;
      }
    }
    waypoint = waypoints.next();
  }

  return false;
}
  • In the past 2 weeks they acknowledge reports pretty fast, but don't know if it means anything. Let's hope that things will go faster even after acknowledgement. This January they actually wrote here to reopen new reports if it's not fixed after a while (we joked about it that we'll open new versions of bugs yearly...) Unfortunately even that won't really work probably as half of the people continued to comment , up-vote on the old one, even though they were directed to the new one. On the other hand we don't even know if that would matter at all (in other words whether Garmin follows up on things commented/voted once they acknowledged a report). Sometimes we get a comment from Garmin, but that's the minority of the reports only

  • That's a legit bug on the Fenix 8 Pro and Forerunner 965. The waypoint.toIntent() call starts the activity but drops the navigation data entirely, even though courses work fine and manual selection does too. Garmin already logged it as CIQQA-3741, so they're aware. Hopefully a fix lands in the next beta firmware.