srajiang
commented
2 years ago Hey @ro-internal - Always cool to see folks starting out in development trying out our frameworks :)
I pulled down the code sample you provided above and noticed a couple of things that might be the culprit(s) here:
// did you mean 'wake up'?
app.message("ake`` up", async ({ command, say }) => {
// to access message and it's properties, declare it in your callback params.
// Bolt will pass message as an argument to your callback when it invokes it
try {
say({ text: "I'm awake! ⭐️ Do you need assistance?", thread_ts: message.ts });
} catch (error) {
console.log("err")
console.error(error);
}
});A very slightly modified version of your code works for me! Let me know whether that fixes it for you.
app.message("wake up", async ({ message, say }) => {
try {
await say({ text: "I'm awake! ⭐️ Do you need assistance?", thread_ts: message.ts });
} catch (error) {
console.log("err");
console.error(error);
}
});
ro-internal
dhaval079
zimeg
I have a bot that's meant to reply to messages in a channel with certain keywords it's listening for. I have it deployed and it's working perfectly, but it replies in the channel rather than starting a thread to a user's message. I apologize if this seems self-explanatory, I’m fairly new to JS and programming in general. Here's my code that's meant to start the thread:
app.message("ake up", async ({ command, say }) => { try { say({ text: "I'm awake! ⭐️ Do you need assistance?", thread_ts: message.ts }); } catch (error) { console.log("err") console.error(error); } });Nothing happens when I send a message saying "wake up". When it's the same without thread_ts: message.ts and just says say("I'm awake! ⭐️ Do you need assistance?")}, it works perfectly. and responds with that, but just as a message in the channel.
What type of issue is this? (place an
xin one of the[ ])Requirements (place an
xin each of the[ ])Attachments:
Here's the beginning of my code for reference:
require("dotenv").config(); const app = new App({ token: process.env.SLACK_BOT_TOKEN, signingSecret: process.env.SLACK_SIGNING_SECRET, socketMode:true, appToken: process.env.APP_TOKEN });