Watch app: Activity recording session.start() freezes the app and the simulator

3904515 over 1 year ago

Using the SDK 6.4.0

Device: FR265

function startSession() as ActivityRecording.Session {

var session = ActivityRecording.createSession({ // set up recording session

:name=>"Bouldering", // set session name

:sport=>Activity.SPORT_ROCK_CLIMBING, // set sport type

:subSport=>Activity.SUB_SPORT_BOULDERING // set sub sport type

});

if ((session != null) && (session.isRecording() == false)) {

session.start();

} else {

System.println("cant start session because session is ==>" + session);

}

return session;

}

The app completely freezes along with the simulator. the only way out is to kill the simulator, because even trying to stop the app gets timeout with the launcher.

I tried running/debugging the `Activity Tracking` example from the SDK, same behaviour

3904515 over 1 year ago in reply to jim_m_58

thanks jim_m_58 for helping in debugging this, I really do appreciate it.

I tried java 17 now as well.

java -version
openjdk version "17.0.9" 2023-10-17
OpenJDK Runtime Environment Homebrew (build 17.0.9+0)
OpenJDK 64-Bit Server VM Homebrew (build 17.0.9+0, mixed mode, sharing)

No dice. Still hangs at the same point.

this is the command that gets executed:

java -Xms1g -Dfile.encoding=UTF-8 -Dapple.awt.UIElement=true -jar /Users/<user>/Library/Application Support/Garmin/ConnectIQ/Sdks/connectiq-sdk-mac-6.4.1-2023-12-04-6cafd260d/bin/monkeybrains.jar -o bin/RecordSample.prg -f /Users/<user>/Library/Application Support/Garmin/ConnectIQ/Sdks/connectiq-sdk-mac-6.4.0-2023-11-15-2e7aa9074/samples/RecordSample/monkey.jungle -y /Users/<user>/Documents/personal-workspace/developer_key -d fr265_sim -w

All other example works.

I had my app working for most things that i wanted to do, recording the data to fit file was the last thing left.

3904515 over 1 year ago in reply to 3904515

ok Definitely a bug in SDK,

after trying everything else, i downloaded the SDK 6.2.1, and that works fine ! no issues. So, its definitely a problem with 6.4.0+

philbert82 over 1 year ago in reply to 3904515

I had exactly the same problem using SDK 6.4.1. It is not solved. 6.3.1 seems to be okay. Thanks for going through the pain of figuring this out. It cost me a few hours, but your experience got me unblocked.