troubleshooting · how to

Install or reinstall does not complete

Diagnose and recover when install or reinstall does not complete needs attention.

Use this guide when the Slash Social install or reinstall flow stops before App Home and slash commands work in Slack.

Symptoms

You may see one or more of these signs:

  • OAuth finishes or appears to finish, but App Home stays blank or never loads work centers.
  • /social, /social-create, or /social-approve do not autocomplete in Slack.
  • The app appears under Apps, but the Home tab is missing or empty.
  • Slack shows a pending app request instead of a completed install.
  • Commands worked in another workspace but not in the one you just installed into.

The install must complete before App Home navigation and the public slash commands work in that workspace.

Likely causes

  • The installer picked the wrong Slack workspace.
  • Slack blocked the install because of workspace app policies.
  • The OAuth step returned an error or the browser closed before completion.
  • An older install is still cached and commands point at the wrong app version.
  • Required bot events or scopes were not granted during reinstall.
  • A workspace admin must approve third-party app installs before the flow can finish.

Checks

  1. Confirm you are signed into the Slack workspace where the team expects Slash Social.
  2. Open the install page at https://go.slashsocial.app/slack/install and read the workspace name on the consent screen before you approve.
  3. After OAuth, open Apps, then Slash Social, and look for the Home tab.
  4. Type /social in a channel and check whether Slack autocompletes the command.
  5. Ask a workspace owner whether third-party app installs need admin approval.
  6. Confirm you completed OAuth in one browser session without switching Slack accounts mid-flow.

Fixes

  1. Run the install again from https://go.slashsocial.app/slack/install and choose the correct workspace.
  2. Complete OAuth in one session without switching Slack accounts mid-flow.
  3. Reinstall from Slack app management if the app is already listed but commands or Home fail. Remove the old install only when your workspace policy allows it, then install again from the link above.
  4. Request admin approval when Slack shows a pending app request instead of a finished install.
  5. Open App Home after install and run /social once to confirm the command palette loads.

App Home should show a loading state, then the full home view with setup or work centers once the install is complete.

Confirm the fix

App Home opens with setup or work centers. /social, /social-create, and /social-approve autocomplete in Slack. You can open Settings from App Home without errors.

Ask one non-admin teammate to open App Home too, so you know the install works beyond the installer account.

Prevent it next time

  • Read the workspace name on the OAuth consent screen every time you install or reinstall.
  • Use one Slack account and one browser session for the full OAuth flow.
  • After manifest or scope changes in your environment, reinstall when your admin team directs you to, so bot events and scopes stay current.
  • Follow Install Slash Social in Slack for the standard first-time path before you troubleshoot edge cases.

Contact support

Escalate when OAuth finishes without an error but App Home stays blank and none of the three public commands autocomplete after reinstall.

Send support:

  • Workspace name
  • Installer Slack user ID or display name
  • Browser error text if any appeared during OAuth
  • Whether the app appears under Apps
  • Whether /social autocompletes

Related articles: