HTTP "PUT" failed in fxAbort unhandled exception

[stc1988]

Pebble SDK Version: Pebble Tool v5.0.29 (active SDK: v4.9.148)

I tried to run example applicaiton hellohttpclient/src/embeddedjs/main-put.js, but failed with below error.

[21:24:42] xsPlatform.c:209> undefined
[21:24:42] xsPlatform.c:217> fxAbort unhandled exception: call: not a function
[21:24:43] ault_handling.c:99> App fault! {12471cb1-caf2-4925-a63c-f27e9eb9cf68} PC: 0x5 LR: ???
Program Counter (PC)    : 0x5        b'??:0'
Link Register (LR)      : ???        ???

[vincentezw]

I'm experiencing this for every non-GET request I make, both with fetch and underlying HTTPClient directly. @moddable/pebbleproxy/proxy.js shows me that it receives app messages with id 15001 (number), 15002 (schema/protocol/url array), 15003 (headers). It receives no 15004 (body) and then falls through into makeRequest where on a missing 15005 it throws with expected property missing. The simulator then fails with fxAbort unhandled exception like above.

This is a blocker for me as it disallows network requests from Alloy. Using app messages may be a workaround but shouldn't be necessary.

[phoddie]

I'm experiencing this for every non-GET request I make

The problem is related to the presence of a request body on an HTTP request, not any particular method. We're investigating. However, the issue appears to be a bit subtle. Thank you for your patience.

...it disallows network requests from Alloy

That's overly broad: Requests without a request body do work. Also, WebSockets is also a "network request" and it is working.

[vincentezw]

Yes, my statement was overly broad but generally POST, PUT and PATCH requests need request bodies, and websockets are not a convenient replacement for REST endpoints, which are important on an IoT device.
I played a bit more with the app message proxy but it seems to be the internal state machine in the Moddable C-bridge is hitting an invalid function pointer when transitioning from recieveHeaders to receiveBody. thanks for looking into it ❤️ .

[phoddie]

Good news. Problem resolved. The issue was that the Pebble httpclient needed updates in a couple places in write() after a recent reorganization to how it manages app messages. The output is now as expected.

This should be integrated into the forthcoming April Moddable SDK release for the Pebble team to integrate into their next Alloy release.