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
{{ message }}
This repository has been archived by the owner on Jun 17, 2024. It is now read-only.
I successfully installed and ran the bot-start-slack example app. The bot communicates with me fine when I talk to it via direct message. Commands such as hello, thanks, uptime etc work in DM.
I found a case that causes Botkit Studio to crash. Here's how to replicate it.
Invite the bot to a channel, for example random.
Do an empty mention of the bot, for example "@MYBOT " and hit enter
Botkit Studio will send a message to the channel "I experienced an error with a request to Botkit Studio: undefined"
This error message comes from the catch clause on line 142
.catch(function(err) {
bot.reply(message, 'I experienced an error with a request to Botkit Studio: ' + err);
debug('Botkit Studio: ', err);
});
When you do an empty mention of the bot, the message.text is "" and it causes botkit studio to crash. This only happens on a mention, so If I call
controller.studio.runTrigger(bot, "", message.user, message.channel) the error is not triggered.
The text was updated successfully, but these errors were encountered:
Hi all,
I successfully installed and ran the bot-start-slack example app. The bot communicates with me fine when I talk to it via direct message. Commands such as hello, thanks, uptime etc work in DM.
I found a case that causes Botkit Studio to crash. Here's how to replicate it.
This error message comes from the catch clause on line 142
.catch(function(err) {
bot.reply(message, 'I experienced an error with a request to Botkit Studio: ' + err);
debug('Botkit Studio: ', err);
});
When you do an empty mention of the bot, the message.text is "" and it causes botkit studio to crash. This only happens on a mention, so If I call
controller.studio.runTrigger(bot, "", message.user, message.channel) the error is not triggered.
The text was updated successfully, but these errors were encountered: