capabilities works fine on the emulator, kills the rest of the page on a real watch

[PeterSumm]

The capabilities property seems to work fine on the emulator (from Cloudpebble), but when I run it on my watch the rest of the configuration page is lost after that field. This happens with several different apps, but a much simpler app with an identical config file works fine.

Basalt watch, firmware 4.02, iOS app 4.1

I'll investigate further and add more details if I can.

[keegan-lillo]

Please post your config.json and custom function.

On Sep 16, 2016 4:47 AM, "PeterSumm" notifications@github.com wrote:

The capabilities property seems to work fine on the emulator (from
Cloudpebble), but when I run it on my watch the rest of the configuration
page is lost after that field.

Basalt watch, firmware 4.02, iOS app 4.1

A much simpler app with an identical config file works fine.

I'll investigate further and add more details if I can.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#139, or mute the thread
https://github.com/notifications/unsubscribe-auth/ADX8K7clLZ_Np7MJrRP8X4U9ZaF24wVyks5qqoHigaJpZM4J-23c
.

[PeterSumm]

This is the source code for the project if that helps (it's open source).

The problem statements in config.js have been commented out.

moon_health_location_and_weather_watch (10).zip

[keegan-lillo]

You are initializing clay inside of a ready event (line 539). This will not work. Clay needs that event internally to obtain the capabilities.

[PeterSumm]

Yep, that fixed it. Sorry, I thought I'd tried that.

Thanks for your help.