Multiple Mac players report ReStory exit(173), damaged-app, App Store, and iCloud launch messages after patch 1.0.011r. Use safe checks while a fix is confirmed.
Symptoms reported after 1.0.011r
Current Steam technical threads describe several launch messages in the same short window. Treat them as a report cluster, not proof that every Mac failure has one cause.
| Visible symptom | What it proves | What it does not prove |
|---|---|---|
| exit(173) / Not Available | Steam failed to complete the launch | That saves are damaged |
| Application is damaged | macOS rejected or could not validate the app | That deleting personal data will help |
| Get it from the App Store | A platform or package check interrupted launch | That ReStory is sold through the App Store |
| iCloud sign-in message | An account-related prompt appeared | That resetting iCloud is a confirmed fix |
Safe troubleshooting order
Start with reversible checks and stop when the result changes.
- Quit ReStory and Steam completely
- Restart macOS
- Open Steam and confirm patch 1.0.011r finished downloading
- Steam Library → ReStory → Properties → Installed Files → Verify integrity
- Launch once from Steam, not from an old Dock shortcut
- Record the exact message and macOS version
- Check the current Steam technical thread before deeper changes
Story progress can depend on a completed repair, a To-Do, and the next conversation. Check all three before treating a quiet shop as a softlock.
Open original page →Protect saves before deeper testing
A launch error occurs before normal play, so deleting save folders is not a sensible first step. Preserve local ReStory data and Steam Cloud state before changing files. Do not disable macOS security globally, run commands copied from an unrelated game's forum, or remove application signatures unless the developer or Steam Support publishes a ReStory-specific procedure.
What to include in a useful report
State whether the Mac uses Apple silicon or Intel, the macOS version, Steam client version, ReStory build, exact error text, and whether the game launched before 1.0.011r. Attach a screenshot and the time of the attempt. If Steam verification finds files, report the count and whether the next launch changes.
Marketplace decisions start with the listing: compare condition, price, seller information, license access, and the parts or resale purpose before buying.
Open original page →Current status
The issue is based on multiple current player reports in the ReStory technical forum (https://steamcommunity.com/app/3812600/discussions/1/). The official 1.0.011r notes do not list a Mac launch fix. This page will keep the short answer conservative until the developer confirms a cause, hotfix, or supported workaround.
Does reinstalling guarantee a fix?
No. Reinstallation can replace missing or corrupted game files, but it does not guarantee a solution for a packaging, entitlement, operating-system, or patch-specific problem. Verify files first and preserve saves.
Should I delete my ReStory saves?
No. There is no verified evidence that a pre-launch exit(173) error is caused by a game save. Back up data and wait for ReStory-specific support guidance.
Where should I check for a confirmed fix?
Check the official Steam announcements, the pinned ReStory bug-report thread, and any reply marked as a developer answer. Match the advice to 1.0.011r or a later build before using it.
Research links
These are the primary pages used to check the facts and current release context in this guide.
Official information, observable release behavior, and community reports are deliberately separated. A community report is not presented as a universal fix until it can be reproduced or supported by current patch notes.