Slipway is built by a solo developer, and every report gets read. The fastest way to get a fix is to report a bug from inside the app, so the report includes diagnostics.
Where to start#
- Look for your error message in Troubleshooting & FAQ.
- If it isn't there, report it with Help ▸ Report a Bug….
- For anything that doesn't belong in a public issue, such as purchases or privacy questions, email support@handheldworks.com.
Help menu#
| Item | What it does |
|---|---|
| Slipway Help | Opens slipwaymac.com |
| Report a Bug… | Collects diagnostics, then opens a prefilled GitHub issue in your browser |
| Copy Diagnostics | Collects the same diagnostics and copies them to your clipboard |
Report a bug#
- Choose Help ▸ Report a Bug…. A Collecting diagnostics… toast appears for a moment.
- Your browser opens a new issue on Slipway's GitHub repository. The issue already has a What went wrong? heading and a Diagnostics block.
- Under What went wrong?, describe what you did, what you expected, and what happened instead.
- Check the diagnostics, then submit the issue. You need a GitHub account to submit.
Nothing is sent until you submit the issue in your browser. GitHub issues are public, so read the diagnostics block first. GitHub limits how long a link can be, so if the diagnostics are very long, Slipway drops lines from the end of the block to fit.
If you'd rather not use GitHub, choose Help ▸ Copy Diagnostics. When the toast says Diagnostics copied to the clipboard, paste the report into an email to support@handheldworks.com.
What diagnostics contain#
Here's an example. The values are made up, but every line follows the exact format the app uses:
Slipway 0.1.0 (1)
macOS Version 15.6 (Build 24G84)
Accounts: 2 (keys 7K9PQ2XR4M, 3HJ8WQ6N2D)
AI provider: Anthropic
JWT 7K9PQ2XR4M ok
GET /v1/apps ok (1 app)
JWT 3HJ8WQ6N2D ok
GET /v1/apps FAILED: App Store Connect returned HTTP 403.
xcodebuild ok
Last ASC error: GET https://api.appstoreconnect.apple.com/v1/apps?… -> 403 FORBIDDEN_ERROR …
| Line | Meaning |
|---|---|
Slipway …, macOS … |
App version and build, and your macOS version |
Accounts |
How many teams are connected, and their Key IDs (never the keys) |
AI provider |
The provider's name (never your AI key) |
JWT … ok / FAILED |
Whether Slipway could sign a token with each key |
GET /v1/apps ok / FAILED |
A one-app test request with each key |
xcodebuild ok / not found |
Whether Xcode's command-line tools are available for Build & Upload |
Last ASC error |
The most recent failed App Store Connect request, or none |
The last line can include app or version IDs in the request URL. Edit them out if you'd rather not share them.
When Slipway crashes#
If Slipway quit unexpectedly, the next launch shows Slipway crashed last time. Slipway finds out about crashes by reading the crash report macOS saves in ~/Library/Logs/DiagnosticReports. The sheet shows when the crash happened, the exception type and the first line of Slipway's code involved. Your choices:
- Not Now: dismisses the sheet. Nothing is sent.
- Copy Crash Log: copies the full crash log to your clipboard so you can attach it to an email.
- Report on GitHub: opens a prefilled issue with diagnostics and the first 60 lines of the crash log. Lines containing device identifiers are removed first.
As with bug reports, nothing leaves your Mac until you submit the issue yourself.
Contact#
- Email: support@handheldworks.com
- Website: slipwaymac.com
For release notes, see the Changelog. For how your data is handled, see Privacy & security.