When a developer tries to upload a new application (e.g., a Watchface based on a template or a previous project) without changing the default UUID, the developer portal shows a "Submission failed" error.
Current Behavior:
The current error message correctly identifies that the UUID already exists but instructs the user to fix it in the wrong file for a typical workflow:
"An application with the supplied UUID already exists. ... please generate a new UUID in your appinfo.json."
The Problem:
For developers using the standard build tools, appinfo.json is an auto-generated file. Any manual changes made to it will be overwritten the next time the project is built. The actual source of the uuid is in the package.json file. This instruction can cause confusion, especially for new developers, as their "fix" will disappear after a rebuild.
Suggested Solution:
The error message should be updated to guide the user to edit the source configuration file instead of the generated one.
A clearer message would be:
"An application with the supplied UUID already exists. To fix this, please generate a new UUID in your project's package.json file and then rebuild your application before uploading again."
Disclaimer: I'm speculating a bit on the standard workflow here based on my experience, so please feel free to correct me if I'm wrong about anything.