-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blocks #245
Comments
Does anyone have any ideas on this -- this is somewhat delaying my project until I can solve this :) |
Unfortunately, I'm not well-versed with the newer Blocks APIs. Afaik, we don't do any validation in the library and the messages just get serialized as-is and sent to Slack. It might be worthwhile to check other libraries or the official API for any hints on what's causing this. It also might be worthwhile to view the raw responses with Fiddler4 or use the library directly and step through to see the raw response from the API to see if it contains any more descriptive error messages. |
Hi, thank you in any case. I will try and inspect the serialized JSON to see what it shows :) |
Ok, I got this, using a new script:
This is hard to read, but when imported to the slack Block Builder, I see that: "title" is invalid for a block of type section: (Invalid additional property "title" error) I think there is a bug with the title element on your side, and a bug in the block ID on my side :) So I will continue debugging, now moving on to try and add fields. |
Hi,
I am having trouble sending a block message to slack. I wonder if someone could advise me what I am doing wrong?
I can send ordinary messages just fine, but its these blocks that are giving problems. I was unable to find any example or documentation for this, but this, I understood should have worked...
My sendMessageAsync function is as such:
In each case I get invalid_blocks as an error.
The text was updated successfully, but these errors were encountered: