Slack connector OAuth fails with invalid_team_for_non_distributed_app
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- authentication
Research direction
No source file or test is named. Start by reproducing the dashboard's Slack as Bot authorization flow and read the linked Slack OAuth error documentation, then inspect the connector documentation for the intended flow. Done means authorization reaches the consent screen and the bot appears under Your connections.
Written by the indexing model from the issue text.
Description
Summary
Authorizing a Slack as Bot connector from the Sprites dashboard for the dashaai.slack.com workspace fails before authorization completes.
Steps to reproduce
- Open a Sprites organization in the dashboard.
- Go to Connectors.
- Add a Slack as Bot connection.
- Select and authorize the Slack workspace.
Actual result
Slack displays:
Something went wrong when authorizing this app.
invalid_team_for_non_distributed_app
Retrying does not resolve the failure.
Expected result
Slack should display the consent screen, complete authorization, and add the bot connector under Your connections.
Likely failure boundary
Slack documents this error as occurring when an undistributed Slack API app is authorized on a workspace other than the workspace where the app was created. Because the Sprites dashboard supplies the OAuth application for this connector flow, the OAuth client may be undistributed or the flow may be using the wrong client ID.
The target workspace cannot change distribution settings for a Slack app owned by Sprites.
References
- Slack error definition: https://docs.slack.dev/authentication/installing-with-oauth/#errors
- Sprites connector documentation: https://docs.sprites.dev/concepts/connectors/
- Closed Fly.io forum report from other affected users: https://community.fly.io/t/sprites-connector-slack-invalid-team-for-non-distributed-app/28049
Observed on July 13, 2026.
- Dominant language
- TypeScript
- Stars
- 51
- Forks
- 4
- Avg merge
- 23h 57m
- Merged PRs (30d)
- 12
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from superfly/sprites-docs
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
superfly/sprites-docs#226 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
superfly/sprites-docs#220 ·
-
superfly/sprites-docs#237 · 1 assignee ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
superfly/sprites-docs#231 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
superfly/sprites-docs#230 · 2 comments ·
All issues in superfly/sprites-docs
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·