Edge 520 ConfirmationDelegate not being called

Hello,

My CIQ app uses a very simple ConfirmationDialog. It works on my FR935 and in the simulator, but on my Edge 520 the ConfirmationDelegate isn't called.

A user reported a similar problem last July on the Edge 1030, but never followed up on the thread:
https://forums.garmin.com/forum/developers/connect-iq/connect-iq-bug-reports/1373170-class-ui-confirmationdelegate-never-call-onresponse-with-an-edge-1030

I'm calling the dialog like this
var dialog = new WatchUi.Confirmation("Download now?");
Ui.pushView(
dialog,
new DownloadNowConfirmationDelegate("today"),
Ui.SLIDE_IMMEDIATE
);


Thanks!
  • Here's the delegate:

    class DownloadNowConfirmationDelegate extends Ui.ConfirmationDelegate {
    var fromMenu = "today";

    function initialize(fm) {
    fromMenu = fm;

    ConfirmationDelegate.initialize();
    }

    function onResponse(response) {
    Util.log("conf response: " + response);
    if (response == 0) {
    } else {
    var workoutLoader = new WorkoutLoader(fromMenu);
    workoutLoader.loadNewWorkouts();
    }
    }
    }
  • Have you tried the confirmation dialog sample in the SDK? Sounds like from the 1030 thread you linked to, the Garmin folks couldn't reproduce that.

    If the sample in the SDK works for you, you may need to narrow down the differences.
  • I built the ConfirmationDialog prg and placed it in the APPS directory, but it's not showing up on the 520. Also, my app runs fine on the 935 and the simulator -- the confirmation dialog is only broken on the 520.

    Any ideas? Thanks!
  • Ah, I got the ConfirmationDialog sample running on my 520. I didn't realize that it's a widget. I was looking for it under apps. The dialog works in the sample on the device.

    So, one big difference: my app is an app -- not a widget. The dialog is being loaded from a menu selection. It's showing correctly, but doesn't fire any events to the delegate. I have to reboot the device after the dialog is loaded.
  • Further narrowed down the problem: the confirmation dialog works as intended if it's the first/only view loaded by the app. It doesn't work when it's pushed into view from a Menu.
  • Update: I gave up on trying to get this to work. I'll just use a Menu on the 520 instead of a ConfirmationDialog.