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

Testing App and Deploying new versions after release

I have a few questions.  The first is, I'm having trouble testing my watchface.  Specifically, Some number I'm relying on is not accurate for the first 5 or so seconds that my watchface is open.  It causes the numbers to spiral out of control, then recover.  It's not the end of the world, but not a great user experience, and it's not consistent enough to measure in the studio app.  Is there a pattern for unit testing in the app, and/or some way to get the console.log messages from my watch throughout the day?

 

Second.  There's a warning when I try and submit my app that says that "you will not be able to edit the metadata or upload new builds"  Does this mean we can't add new features to the app after it has been deployed?

 

Thanks!

Best Answer
0 Votes
1 REPLY 1

Right now, the only way to debug your application is by using console logs. As for having log details all day long, you would need to work on something a little more elaborate: either something visual that display this information on the watch or in the companion settings, or using the messaging API to send data to the companion app which in turn, can send you that information in different ways.

 

You can submit a new version of your application once the latest build is either rejected or approved.

Best Answer
0 Votes