Skip to main content
Most Whip hiccups have a quick fix. Builds that seem stuck usually retry on their own; apps that won’t open often just need a moment to wake up; sign-in trouble is almost always the wrong provider or a typo. Find your symptom below for the exact steps — and if nothing here helps, we’re one message away.
Most apps are ready in about a minute or two; ambitious ones take longer. Builds retry themselves through temporary hiccups, so a slow one is often still working hard. If a build genuinely gets stuck, it stops on its own with a clear error rather than spinning forever. You don’t have to watch — leave the screen, browse the feed, and come back. Whip sends a notification when your app is ready.
A failed build never eats your idea. Send another message in the same chat to pick up where it left off. If it keeps failing, try simplifying your request or splitting one big idea into smaller ones. Whip already retries automatically before you ever see a failure, so a message from you is usually all it needs. Full rescue guide in build limits and failed builds.
Building draws from a shared daily pool — creating, editing, and remixing all count toward the same limit. When you hit it, Whip tells you when it resets. The limit resets automatically, so come back a little later and you’re good to go.
Apps you haven’t opened in a while wake up automatically the first time you return — give it a moment to load. If it’s still stuck, check your internet connection, then force-quit Whip and reopen it. That clears most one-off loading snags. More on opening and using apps.
First, make sure you’re using the same method you signed up with — Apple, Google, or email and password. For email sign-in, watch for stray capitals and typos in your password. There’s no self-serve password reset yet, so if you’re locked out, email support@whip.run and we’ll help you back in.
Open Settings → Notifications and check the master switch plus the individual categories — one might be off. Also confirm Whip has permission to send notifications in your phone’s system settings; if you denied it at first launch, that’s set at the OS level. Details in notifications.
This appears when Whip loses your connection. Reconnect to Wi-Fi or mobile data and Whip reconnects as soon as you’re back online. An action you tapped right before going offline resumes once you’re reconnected.
A required update means a new version of Whip is ready and needed to keep everything working. Tap the button in the Update available prompt to grab the latest from the App Store or Play Store. More in manage your account.
A blocked title, image, or app is almost always the automatic safety screen, not a person. Edit the wording or swap the image and try again — small changes usually clear it. If you’re sure it was a mistake, see report content for what to do next.
Still stuck after trying the steps above? We’d genuinely like to help — reach out through contact and support.

Build limits and failed builds

Why builds fail, how retries work, and how to recover your app.

Contact and support

Email, Discord, and the fastest way to reach the team.
Last modified on July 3, 2026