@Zach F Try to use the object schema for the command response.
For the second question about the missing responses in the Command history, yes, it looks like this is a bug.
btw. this is a duplicate question to SO.
Thanks
Roman
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I am using the code from the async-hub-scenarios, particularly the "receive_direct_method" file.
It states to do the following:
This is what happens in the "response"
If I serialize the payload, the response now shows - however - there is no "view payload" button and the response is overwritten in the command history when I send another command.
Here is code:
Here is response with no "view payload" button.
Why is the response originally nothing, then theres no view payload button - but the entire time, every response overwrites the previous response in the command history section. Thank you.