You are deep in a Rork or Rork Max project and suddenly nothing moves. Generation spins without producing files. Native builds fail every time while the preview is fine. The project opens but will not advance. I have lost full days to this, and after shipping several apps I now have a fairly reliable mental model of what is happening and what to do.
This guide is that mental model written down. We will classify the stuck mode in ten seconds, then work the recovery that fits.
The four stuck modes
Grouping every "Rork is stuck" under one label is why fixes feel hit-or-miss. The diagnoses and fixes diverge.
Mode 1 — generation looks alive but is not advancing. Prompt sent, progress indicator still, no new or modified files for many minutes.
Mode 2 — preview works, native build fails. Web or Expo preview is fine; iOS / Android native builds fail the same way every time. Common around Rork Max SwiftUI native builds and Expo iOS builds.
Mode 3 — dependency graph broken. Nothing is generating or building anymore, and errors include Cannot find module or Invalid configuration.
Mode 4 — prompt drift. Builds succeed but the app keeps evolving in a direction that is not what you asked for. Technically not "stuck," but the cure for your calendar is the same.
Ten-second triage:
- Generation seems alive but no file activity → Mode 1
- Preview OK, native build broken → Mode 2
Cannot find module/Invalid configerrors → Mode 3- Builds fine, behavior drifts from your intent → Mode 4
Mode 1 — generation stalled
Decide first whether it is actually stuck. Rork resolves file dependencies internally, so short quiet periods are normal.
Rule of thumb: if 15+ minutes have passed with no change to the file tree and no new log lines, consider it truly stalled. Five to ten quiet minutes is within the normal range.
Three-step recovery:
Step 1 — reload the page. The backend sometimes finishes while the frontend freezes on an old render state.
Step 2 — split the prompt. Compound requests like "build me the login, profile, and settings screens" often stall while Rork tries to plan too large a generation. "Just the login screen, please" unblocks a surprising share of stalls.
Step 3 — rewrite for specificity. Replace "make it nice" with concrete tech choices (state management library, screen layout, nav stack). Less room for the generator to over-plan means fewer stalls.
Prompts that stall most often
- Requests with fuzzy success criteria ("nice," "cool")
- Single prompts asking for 10+ screens
- Large rewrites of existing code (new creation is far more stable)
Shape prompts to be incremental — one screen, one feature, one change.
Mode 2 — native builds keep failing
Most common on a first Rork Max SwiftUI native build. Three sub-causes.
2-A — signing / provisioning. The iOS wall everyone hits. A missing Apple Developer enrollment, a wrong certificate, a mis-scoped provisioning profile — any one of them kills the build. Work through a published checklist; do not skip.
2-B — native module dependency mismatch. Rork's auto-added native modules (camera, notifications, StoreKit, etc.) fall out of version sync. Linker command failed or Undefined symbols are the give-away. Fix by asking Rork itself to "reset and realign native dependencies" — hand-editing native config is a deep hole.
2-C — iOS / Xcode version mismatch. Your app uses a SwiftUI feature that needs a newer iOS than your Info.plist MinimumOSVersion allows. Raise the target or stop using the feature.
Mode 3 — broken dependencies
Once the graph is corrupted, nibbling at it from inside the Rork chat rarely wins. Switch to a clean rebuild.
- Export the current project as a backup (zip it if possible).
- Create a new empty project.
- Copy over business logic only — MDX content, domain code, assets.
- Let Rork rebuild native/app configuration from scratch by prompting: "Implement the following feature using a clean project."
Counter-intuitive, but fewer hours than spelunking a broken tree.
Mode 4 — prompt drift
The slow poison. You fix the drift, drift recurs, days melt.
Write a spec before you open Rork
## App spec
### Screens
- Home: today's tasks (up to 10), new-task button
- Create: title input, due-date picker, save
- Detail: title, complete button, delete
### Data model
- Task: id (UUID), title (string), dueDate (date), completedAt (date?)
### Non-functional
- Offline-first (local DB)
- Cold start ≤ 3s
- iOS 17+
Paste that into Rork verbatim. The difference between "I chatted my way to an app" and "I specified an app" is measured in hours saved per week.
Final recovery checklist
When you are stuck, walk this list in order:
- Give it 15 more minutes — is it actually stalled?
- Reload the page.
- Split the prompt; try the smallest piece alone.
- Check Rork Companion connection if anything cross-device is involved.
- For native builds, walk the certificates / profiles checklist.
- For broken dependencies, clean-rebuild instead of repairing.
- For drift, rewrite the spec first, then talk to Rork.
Most stuck moments resolve within an hour this way.
If you are moving beyond unblocking and want the end-to-end production story — designing the spec, staging generation, keeping diffs reviewable, and landing in the App Store — the deep dive Rork Max SwiftUI native apps: a production shipping guide goes all the way from requirements to review response.