My app vanished overnight. Here's how Claude helped me fix it.

I woke up one morning, went to log my health data, and the app was gone.

Not crashed. Gone. An app I built myself with Claude Code and Xcode, the one that counts my steps, tells me when to lift and when to rest, tracks my seven-day weight average and walks me through my nightly routine. Off my phone.

When I recorded this in January, I was about a week and a half into Claude Code. Brand new. So this is a real beginner's fix, start to finish, including the part where the build failed on camera. Because that is what building with AI actually looks like.

Let me show you what happened, how I fixed it, and the workflow that made it easy.

Why the app disappeared

Here's what nobody told me. When you build an iPhone app in Xcode and install it on your own phone without the right Apple developer setup, it only lasts about seven days. Then it stops opening. Apple treats you like any other customer, even though you made the thing.

I had a paid Apple developer account. That is the 99 dollars a year one that also lets you put apps on the App Store. The catch? I built this app before I got the account. So the project was still pointed at my old free personal team.

That was the whole problem. Not the code. The signing.

Step one: make Claude study the app first

Before I touched anything, I did the thing I tell everybody to do. I had Claude study the app.

I gave Claude Desktop the folder path and typed: "Study the app first, and then let's talk about it."

Why? Because once it has studied the project, it has all the context. It knows the files. It knows how the pieces connect. Every answer after that is sharper.

Quick Mac tip, because I had to look this up. You cannot drag a whole app folder into Claude. To get the path, hold Option, right-click the folder, and choose Copy as Pathname. Paste that in. Not everybody knows that. I didn't.

Step two: talk it out, then hand off one prompt

My workflow is simple. I talk it out in chat first. Then I take the plan to the terminal.

Since I was rebuilding the app anyway, I wanted an update too. I use a CPAP machine at night, and I kept forgetting to fill it. So I asked Claude for options. It gave me a few: a fourth step in my sleep routine, a separate notification, or both. I picked the fourth step and asked it to give it major XP, because I love that gamified feel and it would keep me doing it every night.

Then I asked Claude to write me the exact prompt for Claude Code. Which files to change, what to add, what to check. It could name those files because it had already studied the app. That is the key.

I pasted that one prompt into Claude Code in my regular Mac terminal, and it went to work. Man, it was on a feeding frenzy.

A word of caution here. I ran Claude Code in a mode where it does not stop to ask permission for every step. That is fine on your own machine, on your own Wi-Fi, on your own project. On a company machine? You might be cooked. Know what you are turning on.

Step three: the build failed. On camera.

Claude Code finished and said the Xcode project was ready. So I hit Command B to build.

Build failed.

I did not panic. I took a screenshot of the error, dropped it into the terminal and typed, "Hey, build failed." Claude Code went right back to work. It came back and said it pulled the sleep task row out into its own piece to simplify things, try again.

Command B. Build succeeded. Command R to run it on my phone. Installed, running. My hydration check gave me my XP, my weight average was there, all my data was still there. That was my biggest fear, by the way. Losing the data. It held.

That is the real loop. You build, something breaks, you show Claude exactly what broke, it fixes it. Over and over.

Step four: stop the seven-day clock

Back to the actual problem. I told Claude: I already have a paid Apple developer account, but I built this app before I had it. Do I need to do anything?

Here's what it walked me through:

• Open the project in Xcode and select it in the Project Navigator.
• Under Targets, check the Team setting and pick your paid team, not the old personal team.
• Make sure you are signed in under Xcode, Settings, Accounts.
• Rebuild and run it on your actual phone, not the simulator.

When I checked, my personal team was gone and my developer account was showing. Since I had just rebuilt and run it, it was signed the right way.

The lesson? If you think you might ever sell an app, set up the Apple developer account first. Then you never hit this.

What this means for you

You do not need to be a developer to fix things like this. I wasn't. What you need is a way of working: let the AI study what you built, talk the plan out, hand off one clear prompt, and when it breaks, show it exactly what broke.

That is the kind of thing the RMDW Platform teaches, starting with Claude, in lessons built around your own business. Learn the workflow once and you stop being scared when something disappears overnight.