Use a dot to fix and resubmit a rejected app

A developer had a dot track down a build crash, patch the app, test it, and resubmit it from a remote conversation.

Done with Dots· Intermediate· Oct 2026

What they did
A developer asked their dot to look into why an app submission was rejected. The agent found the crash came from missing Scene lifecycle support needed for iOS/iPadOS 27 SDK builds, then applied the Expo patch and a configuration change on its own. It also checked the release build and launched the app in the iPad simulator before opening a pull request and uploading the new build.
How it went
The dot handled the investigation, fixes, testing, pull request, and resubmission end to end. The work was done remotely, and no extra issues were reported.
Tips
For a task like this, give the agent clear permission to inspect the build, make code changes, and stop before any submission step if you want a final review. Keep the conversation open so you can verify the fix and decide whether to proceed.

Try it yourself with Dots

Investigate why [app name] was rejected after a build. Find the crash or setup problem, explain the cause, and make the smallest safe fix needed in the code or config. Then run the relevant build check and test the app in [target simulator/device]. If the fix would affect a release, submission, upload, or deletion, pause and ask for my approval before you do that. After I approve, open a pull request with the changes and resubmit the updated build.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on x.com ↗

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.