app_home_opened event fires twice when the 'messages' tab is clicked

Using app.action to monitor app_home_openend fires twice when a user clicks on the messages tab

 app.event("app_home_opened", async context => {
    console.log(context.payload.tab);
  });

What type of issue is this? (place an x in one of the [ ])

• bug
• enhancement (feature request)
• question
• documentation related
• testing related
• discussion

Requirements (place an x in each of the [ ])

• I’ve read and understood the Contributing guidelines and have done my best effort to follow them.
• I’ve read and agree to the Code of Conduct.
• I’ve searched for any related issues and avoided creating a duplicate issue.

---

Bug Report

Reproducible in:

package version: 1.5.0

node version: v10.14.1

OS version(s): OSX 10.14.6

Steps to reproduce:

 app.event("app_home_opened", async context => {
    console.log(context.payload.tab);
  });

Expected result:

Clicking back and forth between the Home and Messages tab should appear in the console as:

home messages home messages

Actual result:

[jamesfmac]

Thanks @seratch! agree that it doesn’t look like a Bolt issue 😃 I’ll test again in a fresh workspace and if the issue persists I’ll follow your advice and raise it with Slack support.

[seratch]

@jamesfmac Thanks for the information with us. I tried to reproduce your situation again, but I was not able to. I did the following steps. The issue didn’t occur to me.

• Create a new Slack app
• Run your Bolt app with the issued signing secret
• Add a bot user
• Enable Event Subscriptions & add app_home_opened (the outcome is the same with bot events or/and workspace events)
• Sign up for App Home open beta
• Install the app to its development workspace
• Restart the Bolt app with the issued bot token
• Open Home / Messages tabs associated to the bot user on Slack

This issue doesn’t seem to be Bolt-specific. So, as a Bolt maintainer, there is nothing further I can do for you. 🙇

I’m afraid something is happening with your Slack app configuration or workspace. Even if you build the endpoint with other tools, the problem will remain. If you don’t mind, could you contact Slack’s support next year? In case your Slack app has some server-side issues, they may cooperate with related teams (sharing your app id would be helpful for them).