Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

launchArguments not passing

ANSWERED

I am having issues getting the launchArguments to work correctly. I have privately published a new app, that I can successfully launch from my watch face, but I am unable to get the launchArguments to pass through. Is this a bug with the API?

 

Both projects are being built with SDK v3.0, and I have also added the dependent project io-ts that is missing when installing the @Fitbit npm.

 

Watch Face:

import { launchApp } from "system";
let appUUID = "<Removed from public view>";
const appArgs = { PassingValue: true };
launchApp(appUUIDappArgs);

 

App:

import { me } from "appbit";
console.warn("applicationId: " + me.applicationId);  // I get the app ID
console.warn("buildId: " + me.buildId); // I get the build ID
console.warn("launchArguments: " + JSON.stringify(me.launchArguments)); // This always returns as undefined
Best Answer
0 Votes
1 BEST ANSWER

Accepted Solutions

Are you seeing this issue on both the simulator and on the physical device?

View best answer in original post

Best Answer
0 Votes
2 REPLIES 2

Are you seeing this issue on both the simulator and on the physical device?

Best Answer
0 Votes

Appears that it only happens on the simulator. Physical device recognized the passed parameters. Thank you!

Best Answer
0 Votes