Quick Desktop App — Slack OAuth fails with invalid_team_for_non_distributed_app

Q&A
,
1

I’m trying to connect Slack from the Amazon Quick desktop app (Windows) but the OAuth flow is failing.

Environment:

  • Platform: Amazon Quick Desktop App (Windows)
  • Account: amazonbi
  • Target workspace: amazon.slack.com (with Prime Air selected)

What happens:

  1. I click Sign In for Slack in Quick Desktop → Settings → Connections
  2. Browser opens to Slack OAuth page
  3. I authenticate and select my workspace
  4. Auth appears to complete, but the redirect lands on the Slack web page instead of returning the token back to Quick
  5. Quick stays stuck on “Authenticating…”

Second attempt — directly specifying Prime Air workspace:

Expected behavior: OAuth callback should return to Quick and complete the Slack connection.

Additional context:

  • Other team members on the same workspace can connect to Slack successfully
  • The redirect URL should be: https://us-east-1.quicksight.aws.amazon.com/sn/oauthcallback
  • Similar issue reported here: Unable to sign in Slack from Quick Suite | AWS re:Post
  • Root cause appears to be that the Quick Suite Slack app does not have “Public Distribution” activated, preventing installation on workspaces other than where the app was originally created

Has anyone found a workaround for this? Is there a timeline for a fix?

2

Hi @jmevert

Welcome to the Quick Suite community!

The invalid_team_for_non_distributed_app error occurs because the Amazon Quick Slack integration currently supports connecting to your organization’s primary Slack workspace. When a secondary workspace (such as a sub-workspace on Enterprise Grid) is selected during the OAuth flow, Slack’s API rejects the authorization request.

Could you please try this, during the OAuth sign-in flow, select your primary workspace instead? If your organization uses Slack Enterprise Grid, channels from other workspaces should still be accessible once connected.

3

Hi @jmevert

It’s been a while since we last heard from you. If you have any further questions, please let us know how we can assist you.

If we don’t hear back within the next 3 business days, we’ll proceed with close/archive this topic.

Thank you!

4

Hi @jmevert

Since we have not heard back from you, I’ll go ahead and close/archive this topic. However, if you have any additional questions, feel free to create a new topic in the community and link this discussion for relevant information.

Thank you!