You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @viperfx, thanks for taking the time to write in and sharing the code example (that was so helpful to understand your question)!
This might be a bit confusing but to update a modal in response to view_submission requests (= the request handled by @app.view listeners), you can use ack() method with response_action instead of a views.update API call:
If your app just received a view_submission payload, you have 3 seconds to respond, and update the source view. Respond to the HTTP request app with a response_action field of value update, along with a newly composed view. https://api.slack.com/surfaces/modals/using#updating_response
For reference, this example app may be helpful for learning how to use it in a real situation.
app.view("modal-callback-id",async({ ack, body })=>{awaitack({response_action: "update",view: buildNewModalView(body),});});
I found that this bolt-js document section should have a clear explanation about this. We'll update the part shortly.
Description
Describe your issue here.
What type of issue is this? (place an
x
in one of the[ ]
)Requirements (place an
x
in each of the[ ]
)Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
package version: 3.6.0
node version: 14
OS version(s): Windows Gitbash
Steps to reproduce:
Expected result:
The updated view should stay open.
Actual result:
we are finding that when we use the client.views.update call - our updated view closes straight after being updated.
We are using the the docs outlined here - https://slack.dev/bolt-js/concepts#updating-pushing-views
We have tried to call ack right at the start or right after the view.update call - neither make a difference.
We noticed this behaviour upgrading from the legacy slack SDK to Bolt SDK
The text was updated successfully, but these errors were encountered: