[Legacy Pebble App] Cannot open the settings page if there is already an item added

[ledenis]

Once an item has been added (via the settings page), when I try to open again the settings page, it does not open.

Only if I clear the existing item, the settings page can be opened.

Expected: I should be able to open the settings page if there is an item added

System informations

App version: 2.0
Watch: Pebble Time
Phone: Android 14, using the Pebble App from Rebble

[tilden]

Ah, this is the second bug report I've gotten about the legacy app, though the first on Android. Android is a bit easier to test, so I'll have to do some digging to see if I can replicate the issue.

In the meantime, if you can figure out any way to get logs out of it that could be useful!

[ledenis]

Ok, so when I try to open the settings page, here are the logs that show up ("Test" is the existing item):

[22:10:23] pkjs> Checklist:88 Requesting current state from watch
[22:10:23] messaging.c:41> State request received, sending current state
[22:10:23] messaging.c:122> Serialized current state: [{"n":"Test","c":0}]
[22:10:23] pkjs> Checklist:236 failed to JSON.parse data passed in
[22:10:23] pkjs> Checklist:90 State request sent
[22:10:23] messaging.c:67> Outbox send success!

Full logs:

$ pebble install --logs --phone 192.168.1.10
Installing app...
App install succeeded.
[22:10:02] pkjs> StraightForecast:392 loadScript /data/user/0/com.getpebble.android.basalt/app_js_app_files/28cbebad-8721-47ef-99ec-fb415cbf7f1c/pebble-js-app.js
[22:10:02] ocess_manager.c:470> Heap Usage for App <StraightFo: Total Size <53752B> Used <26244B> Still allocated <156B
[22:10:04] essage_outbox.c:69> app_message_open() called with app_message_outbox_size_maximum().
[22:10:04] essage_outbox.c:72> This consumes 8200 bytes of heap memory, potentially more in the future!
[22:10:04] message_inbox.c:13> app_message_open() called with app_message_inbox_size_maximum().
[22:10:04] message_inbox.c:16> This consumes 8200 bytes of heap memory, potentially more in the future!
[22:10:04] messaging.c:23> Watch messaging is started!
[22:10:05] pkjs> Checklist:392 loadScript /data/user/0/com.getpebble.android.basalt/app_js_app_files/b938082c-c230-4b8f-847d-15b27b1f907e/pebble-js-app.js
[22:10:05] pkjs> Checklist:372 signalLoaded
[22:10:05] pkjs> Checklist:374 inside try-bridge-active
[22:10:05] pkjs> Checklist:383 signalLoaded (finalized)
[22:10:05] pkjs> Checklist:84 JS component loaded!
[22:10:09] pkjs> Checklist:88 Requesting current state from watch
[22:10:09] messaging.c:41> State request received, sending current state
[22:10:09] messaging.c:122> Serialized current state: []
[22:10:09] messaging.c:67> Outbox send success!
[22:10:09] pkjs> Checklist:90 State request sent
[22:10:16] messaging.c:49> Item updates received: [{"name":"Test","checked":false,"action":"update"}]
[22:10:16] messaging.c:189> Processed item updates
[22:10:16] pkjs> Checklist:117 Sent config data to Pebble
[22:10:23] pkjs> Checklist:88 Requesting current state from watch
[22:10:23] messaging.c:41> State request received, sending current state
[22:10:23] messaging.c:122> Serialized current state: [{"n":"Test","c":0}]
[22:10:23] pkjs> Checklist:236 failed to JSON.parse data passed in
[22:10:23] pkjs> Checklist:90 State request sent
[22:10:23] messaging.c:67> Outbox send success!

[tilden]

Thanks, I'll have a look! Just confirming: these logs are from the latest test build that fixed issue #11 right?

[ledenis]

No, sorry, the logs were from the last published version 2.1. I didn't think of using that build 😅

So, here are the logs from the latest build from #11:

$ pebble logs --phone 192.168.1.10          
[12:41:32] pkjs> Checklist:104 Requesting current state from watch
[12:41:32] messaging.c:41> State request received, sending current state
[12:41:32] messaging.c:122> Serialized current state: []
[12:41:32] messaging.c:67> Outbox send success!
[12:41:32] pkjs> Checklist:106 State request sent
[12:41:45] messaging.c:49> Item updates received: [{"name":"Test","checked":false,"action":"update"}]
[12:41:45] messaging.c:189> Processed item updates
[12:41:45] pkjs> Checklist:154 Sent config data to Pebble
[12:41:54] pkjs> Checklist:104 Requesting current state from watch
[12:41:54] messaging.c:41> State request received, sending current state
[12:41:54] messaging.c:122> Serialized current state: [{"n":"Test","c":0}]
[12:41:54] pkjs> Checklist:236 failed to JSON.parse data passed in
[12:41:54] pkjs> Checklist:106 State request sent
[12:41:54] messaging.c:67> Outbox send success!

[tilden]

Ah dang, I was hoping that build would fix it!

Anyway, I've created a new build with some additional attempted robustness; let me know if this one fixes it!
PebbleChecklist.pbw.zip

[ledenis]

The problem is still there 😅, here are the logs with this last build:

$ pebble logs --phone 192.168.1.10
[22:09:51] pkjs> Checklist:104 Requesting current state from watch
[22:09:51] messaging.c:41> State request received, sending current state
[22:09:51] messaging.c:99> Serialized current state: 
[22:09:51] pkjs> Checklist:106 State request sent
[22:09:51] messaging.c:67> Outbox send success!
[22:09:55] messaging.c:49> Item updates received: [{"name":"Test","checked":false,"action":"update"}]
[22:09:55] messaging.c:166> Processed item updates
[22:09:55] pkjs> Checklist:171 Sent config data to Pebble
[22:09:59] pkjs> Checklist:104 Requesting current state from watch
[22:09:59] messaging.c:41> State request received, sending current state
[22:09:59] messaging.c:99> Serialized current state: Test	0
[22:09:59] pkjs> Checklist:236 failed to JSON.parse data passed in
[22:09:59] pkjs> Checklist:106 State request sent
[22:09:59] messaging.c:67> Outbox send success!

[tilden]

Okay, so based on yours and others reports, this is definitely a problem that occurs 100% of the time on the legacy Pebble app, both Android and iOS. I'll see if I can set up a test device to track it down.

[tilden]

In the meantime, the old build will still work, so you can sideload this if needed until I can come up with a more permanent fix:

PebbleChecklistLegacy.pbw.zip