Tether 1.0.6

Tether 1.0.6

This release improves the folder picker experience when Google Drive rejects folder listing with 403 Forbidden.

Folder picker diagnostics

• Drive API requests now opt out of Obsidian's default 400+ throwing behavior so Tether can read Google's JSON error response body.
• Added a structured GoogleDriveApiError with HTTP status, Google reason, and setup hints.
• The folder picker now shows a clear troubleshooting checklist instead of only Request failed, status 403 in DevTools.
• Added a Retry button after folder fetch failures.

Setup guidance

• Added 403 troubleshooting steps to the README, hosted setup page, and in-app setup guide.
• The checklist covers the common causes: Google Drive API not enabled, missing Drive scopes, app still in Testing without the user added as a test user, stale tokens after changing scopes/testers, and Google Workspace admin restrictions.

OAuth error parsing

• Token exchange now also disables Obsidian's default 400+ throwing behavior so OAuth errors like redirect URI mismatch keep their useful Google response body.

Version and assets

• Bumped the plugin version to 1.0.6.
• Rebuilt main.js; release assets include main.js, manifest.json, and styles.css.

For users who hit the 403

1. In Google Cloud, enable Google Drive API in the same project as the OAuth client.
2. Confirm Data Access includes Drive, Drive metadata, openid, and email scopes.
3. If the app is in Testing, add the user's Google account under Audience > Test users.
4. If anything changed after login, log out of Tether and log in again before selecting a folder.