For app support, write to support@wellscode.com. For private-preview invitations and TestFlight feedback, use beta@wellscode.com or the feedback controls in TestFlight. See TestFlight help.
Wells Code treats feedback as part of making the apps. Every message is read by a person. We investigate bug reports and review feature requests.
What to include
A good report is usually four sentences:
- The app, version and build number: Settings ▸ About ▸ Version.
- Your device and its OS version.
- What you did, what happened, and what you expected instead.
- Whether it happens every time or only sometimes.
A screenshot usually saves a round trip. A screen recording is better still for anything involving movement or timing.
Attach diagnostics
Every app has Settings ▸ About ▸ Copy Full Diagnostics, which puts a technical summary on your clipboard: versions, configuration, sync state and other recent state. Paste it into the email.
That covers sync problems too. Orbit also has Settings ▸ Sync ▸ Troubleshooting ▸ Diagnostics, which copies a report for sync alone. See Fixing iCloud sync.
Reporting from inside the app
Settings ▸ About ▸ Report a Bug opens a prepared email with the version details already filled in. It is the quickest route and the least likely to miss something.
We aim to reply within five working days. If an expected invitation or reply is missing, check Junk as well as your inbox.
What happens next
We try to reproduce reported issues, trace their cause and fix bugs in Wells Code’s code that we can verify. If a problem is intermittent or depends on Apple or another service, we may ask for more detail or look for a workaround.
Feature requests
Describe the problem you want to solve, what you do today and how often it comes up. We cannot promise to build every suggestion, but this context helps us evaluate it.
Crashes
If an app crashed, please allow your device to share analytics with developers (iOS Settings ▸ Privacy & Security ▸ Analytics & Improvements ▸ Share With App Developers). Crash reports include a stack trace that can help pinpoint the cause. Please also describe what you were doing when the app closed.