App and clock interfere

[JasonShort]

I’m running into a strange issue where my test app won’t launch when I have a clock face running that I designed. 

Tapping the app shows the name of the clock face on startup then the app crashes. When either app or clockface is not installed, things work just fine and the app or clockface function normally. 

[JonFitbit]

Seems strange.

Are you seeing any error messages in the logs?

If an app takes more than 10 seconds to launch then it's killed.

During the first launch after install, the JavaScript is converted to bytecode, and this can take some time too.

Is your app doing anything particularly taxing on startup?

[JasonShort]

The app is a little graphic heavy, but when I recreated it in a new app by copying over code and resources it launches fine. It’s something else entirely that is confusing the system in thinking the app is the current clock face. The launch animation shows the clock face app name and when I install the app, the clock breaks and gives me the error screen.

[JonFitbit · Accepted solution]

You can rename the package.json to package.json.txt and check that the app uuid is different for both projects.

If you cloned them from the same source project, it may have duplicated by uuid.

[JasonShort]

Thanks, that was it. I downloaded a watch face and use the layout to start as the basis on of an app. I'm surprised this doesn't happen more often!

[JonFitbit]

If you know where you downloaded it, let them know if they remove the app uuid from their package.json, it will avoid this problem.

[timjkstrickland]

This solved a similar issue for me where I was trying to post an update to an old project. It turns out that the UUID had changed like you suggested, but I don't understand why. If I'm just updating the same project I opened a few months ago, what's the purpose of changing the UUID when I make the updates now?