Acknowledged
2 months ago

bug: activity data simulation doesn't work on Mac

None of the watch buttons or the buttons in Simulation > Activity Data window trigger any of the callback functions on a DataField. The same code with the same SDK version did work in Linux, so this seems to be a bug in the Mac implementation of the simulator.

SDK 4.1.7, MacOS: 13.1

I found some similar issues but none is exactly the same:
https://forums.garmin.com/developer/connect-iq/i/bug-reports/ciq-simulator-time-simulation-does-not-work-on-mac
https://forums.garmin.com/developer/connect-iq/i/bug-reports/sdk-4-1-1-simulator---activity-data-simulation-do-not-support-button-press
https://forums.garmin.com/developer/connect-iq/i/bug-reports/simulator-in-sdk-4-0-6---removed-support-for-activity-simulation-for-widgets-and-watch-faces

flocsy🤠
Parents
  • over 2 years ago

    I'm on a MacbookPro right now and I'm seeing no such problems with either the 4.1.7 or 4.2.1 SDK. Here is the debug output from my test app.. the X vs Y values are the timerTime vs elapsedTime values of the Activity.Info object.

    I'm able to use both the device buttons in the simulated device as well as the buttons in the Activity Data menu.

    Background: AppBase.initialize
Background: AppBase.onStart
Background: AppBase.getServiceDelegate
Background: AppBase.onAppInstall
AppBase.initialize
AppBase.onStart
AppBase.getInitialView
View.initialize
View.onLayout
View.onShow
0 vs 0
0 vs 0
0 vs 0
0 vs 0
0 vs 0
0 vs 0
0 vs 0
0 vs 0
0 vs 0
0 vs 0
0 vs 0
View.onTimerStart
48 vs 48
1071 vs 1071
2070 vs 2070
View.onTimerStop
2644 vs 3071
2644 vs 4071
2644 vs 5070
2644 vs 6070
View.onTimerLap
2644 vs 3144
2644 vs 4143
2644 vs 5144
2644 vs 6143
2644 vs 7144
2644 vs 8144
2644 vs 9144
2644 vs 10144
2644 vs 11119
View.onTimerStart
3571 vs 12143
4572 vs 13144
5572 vs 14144
6571 vs 15143
7572 vs 16144
Background: AppBase.onStop
View.onTimerPause
7647 vs 17145
View.onTimerResume
View.onTimerLap
8572 vs 18144
9572 vs 19144
View.onWorkoutStepComplete
10572 vs 20144
View.onNextMultisportLeg
11546 vs 21118
12572 vs 22144
13572 vs 23144
14572 vs 24144
View.onTimerStop
14572 vs 25144
14572 vs 26144
14572 vs 27144
14572 vs 28118
14572 vs 29144
AppBase.onStop

Comment
  • over 2 years ago

    I'm on a MacbookPro right now and I'm seeing no such problems with either the 4.1.7 or 4.2.1 SDK. Here is the debug output from my test app.. the X vs Y values are the timerTime vs elapsedTime values of the Activity.Info object.

    I'm able to use both the device buttons in the simulated device as well as the buttons in the Activity Data menu.

    Background: AppBase.initialize
Background: AppBase.onStart
Background: AppBase.getServiceDelegate
Background: AppBase.onAppInstall
AppBase.initialize
AppBase.onStart
AppBase.getInitialView
View.initialize
View.onLayout
View.onShow
0 vs 0
0 vs 0
0 vs 0
0 vs 0
0 vs 0
0 vs 0
0 vs 0
0 vs 0
0 vs 0
0 vs 0
0 vs 0
View.onTimerStart
48 vs 48
1071 vs 1071
2070 vs 2070
View.onTimerStop
2644 vs 3071
2644 vs 4071
2644 vs 5070
2644 vs 6070
View.onTimerLap
2644 vs 3144
2644 vs 4143
2644 vs 5144
2644 vs 6143
2644 vs 7144
2644 vs 8144
2644 vs 9144
2644 vs 10144
2644 vs 11119
View.onTimerStart
3571 vs 12143
4572 vs 13144
5572 vs 14144
6571 vs 15143
7572 vs 16144
Background: AppBase.onStop
View.onTimerPause
7647 vs 17145
View.onTimerResume
View.onTimerLap
8572 vs 18144
9572 vs 19144
View.onWorkoutStepComplete
10572 vs 20144
View.onNextMultisportLeg
11546 vs 21118
12572 vs 22144
13572 vs 23144
14572 vs 24144
View.onTimerStop
14572 vs 25144
14572 vs 26144
14572 vs 27144
14572 vs 28118
14572 vs 29144
AppBase.onStop

Children
No Data