filmaj
commented
1 year ago The following error:
[DEBUG] Error details: TypeError: Cannot read property 'teamId' of undefined, storedResponse: undefined
Comes from one of two locations:
- From the
AWSLambdaReceiver: https://github.com/slackapi/bolt-js/blob/main/src/receivers/AwsLambdaReceiver.ts#L203 - From the
HTTPModuleFunction: https://github.com/slackapi/bolt-js/blob/main/src/receivers/HTTPModuleFunctions.ts#L204
First question: are you using this app on AWS Lambda, and using it with the AWS Lambda receiver that bolt provides? I believe the answer is "no", as to configure bolt-js for use on AWS Lambda, you must manually instantiate the receiver class and pass it as a receiver property to your App constructor. However, what confuses me is you are using the processBeforeResponse property, which is aimed for use exclusively with the AWS Lambda Receiver. We should clarify this point and ensure you are not setting processBeforeResponse unnecessarily, as this could also further confuse bolt execution.
Second, I am not exactly sure what is happening in your authorize function, but some observations:
- the instantiation of the connection to the mongoose DB is done using promise methods (i.e.
then(),catch()) while inside anasyncfunction. This means that the DB connection establishment is done in separate ticks of the JavaScript event loop. This jumps out as me as having the potential for race conditions. - I don't know what the
Slackbotconstruct is or what library this uses, but, if this construct relies on the mongoose DB connection, then it is quite possible, as I mentioned in the previous point, that the mongoose DB connection establishment is not complete by the timeSlackbot.findis called.
If my assumption that Slackbot relies on the mongoose DB connection, then to fix the potential for race conditions, you could change your authorize function to use await to make sure that the code executes sequentially. Something like the following would address that:
const authorizeFn = async ({ teamId, enterpriseId }) => {
console.log(teamId);
// Fetch team info from database
try {
await db.mongoose
.connect(process.env.DB_CONNECTION_STRING, {
useNewUrlParser: true,
useUnifiedTopology: true
});
console.log("Connected to the database!");
} catch (err) {
console.log("Cannot connect to the database!", err);
process.exit();
}
const data = await Slackbot.find({ "access_details.team.id": teamId });
if (!data)
console.log("Not found slack user with team " + teamId);
else {
console.log(data[0].access_details);
return {
// You could also set userToken instead
botToken: data[0].access_details.access_token,
botId: data[0].access_details.app_id,
botUserId: data[0].access_details.bot_user_id
};
}
}
anilskalyane
github-actions[bot]
We are facing the following issue with the Slack app when we are trying to add the app to another workspace (different from the one where it was created). Once the authorization is given, we are able to read all the credentials including team id, access token, etc. However, when we try to use the same credentials to access the workspace for any activity,
we are getting the following error:
I think getting this response from Slack bolt,
In the first line, I'm printing the teamId and same also passing it to the bolt lib(authorizer),
Code: