Added a new sample to show working with I/O Events #6
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hmm. This mostly works, but I'm not getting any webhook responses. I can see that events are happening in the debug tracing on Console, but the response is empty, leading to an error in the JS console:
|
|
Hmm... I'm also running into this issue now. It looks like for some reason the webhook is returning an empty body which is causing the issue. I'll have to look into this one further |
|
Just did some more testing. It looks like the HTTP request from Adobe IO doesn't have a body attached to it. Although in the event debug tracing tab it says does. Any ideas? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a new sample to show how to work with I/O Events with CC libraries. The sample takes the form of a webpage that allows you to trigger different I/O events and shows the resulting API and webhook responses. Solves issue #3.