Indie watchOS Toolkit Survival Guide
# Indie watchOS Toolkit: The Survival Guide + Error Handling KitShip your standalone watchOS app without losing a week to bugs Apple never documented.---## The problemYou built something great for the wrist. Then Xcode wouldn't archive it. Then App Store Connect showed you the same app twice with no explanation. Then a rejection cited "Safety" when the real issue was a cut-off label. None of this is in Apple's docs — because none of it is supposed to happen.It happened anyway. This guide is the record of exactly how it got fixed, written down so you don't have to rediscover it the hard way.## What's insideThe Survival Guide (PDF, 15 chapters + appendices)A field-tested walkthrough of the specific failures that stall standalone watchOS shipping — and the fixes that actually worked, not just the ones that sound plausible:- The Xcode 26 standalone watchOS archiving bug — what it is, the workarounds that don't work (so you can skip them), and the one that does- Duplicate app records — how App Store Connect ends up showing your app twice, how to tell which one is real, and how to safely repoint your project- Decoding App Review rejections — what Guideline 1.4.1 and 4.0 actually mean in practice, with a real case study of two rejections that traced back to one layout bug- Health app–specific landmines — HealthKit permission strings, App Privacy disclosures, and how to frame scores/results so they read as informational, not diagnostic- Builds that vanish — stuck processing, expired builds, and how to tell a real failure from normal Apple slowness- A pre-flight checklist to run before every archive, so most of this never happens to you in the first placeAppError.swift — a reusable error handling systemNot a toy example — a genericized version of a routine used in shipped health & wellness apps:- One LocalizedError enum covering HealthKit, SwiftData persistence, notifications, widgets, and Watch Connectivity- An ErrorReporter singleton that logs everything and surfaces only what the user actually needs to see- A single .appErrorAlert() SwiftUI modifier — attach it once, get consistent error UI everywhere- Drop-in ready, fully commented, with usage examples included## Who this is forSolo and small-team iOS/watchOS developers shipping standalone Watch apps — especially in health, wellness, or any category where App Review runs extra scrutiny. If you're about to archive a watch app for the first time, or you're stuck right now on a build that won't upload, this is built for you.## What this is notNot a general Swift tutorial. Not App Store Connect's documentation restated. This is specifically the undocumented, in-between-the-lines stuff — the parts that cost real time because no official source covers them.## Format- 1 PDF guide (also available as an editable Word document)- 1 Swift source file, ready to drop into your project## Price$15 for the full bundle — guide + error handling kit.(Just want the guide? [Available separately]() for $150)---Written by an indie developer currently shipping four apps in the health & wellness space. Every bug in this guide was hit — and fixed — on real, submitted apps.[Get the bundle →]()
Get it → mikewm.gumroad.com