Bug report // direct to the developer
Send one useful signal.
You do not need to diagnose the problem. Tell us what you expected, what happened, and where you were. The button opens a prepared email you can edit before sending.
The useful minimum
A short honest report is enough. These four details make it much easier to fix:
- Where: the sector, Shipyard page, tutorial lesson, or menu.
- Expected: what you thought the game would do.
- Actual: what it did instead.
- Device: iPhone or iPad model and orientation.
Visual and touch issues
Please leave the full screen visible in a screenshot when possible. Include whether the device was in portrait, landscape, split view, or a folded Duo posture. Mention if display zoom, larger text, or another accessibility setting was active.
For control problems, say where your finger started, what you tried to tap or hold, and whether the ship moved unexpectedly.
Crashes, freezes, and lost progress
Tell us the last action you remember before the problem. If the app reopened, note whether your pilot, cargo, or current sector changed. Do not erase your pilot to troubleshoot unless the developer specifically asks you to.
Gripwake currently uses local saves. Deleting the app can remove progress, so send the report before reinstalling when practical.
Before sending
- The website does not upload a report. It only opens your email app.
- Remove passwords, verification codes, serial numbers, and unrelated personal notifications from screenshots.
- Your email address, message, and attachments will be received by the developer and used to investigate or reply.
- You can delete any line from the template before sending.
See the privacy notice for the full plain-language explanation.
Ready when you are.
Bug reports go to dev@gripwake.com. For TestFlight access rather than a problem report, use the private testing page.
Open the email template