Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My app opens and then sits on a spinner or a white screen

Short answer

An app that never leaves its loading screen is usually waiting for something that does not arrive: a server that is down, a login or data call that fails, a missing setting, or a file that was not packed into the release. Check whether the server and the website work first, then bring me what you see.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The app opens, shows a logo or spinner, and never moves on.
  • The screen stays white or black after the splash.
  • It worked yesterday and nothing was updated on my side.
  • It hangs for some users or phones only.
  • It gets stuck only after a new release went out.

Why does this happen?

  1. The app is waiting for a server that does not answer

    Most apps ask a server for the first screen's data before they can show it. If that call fails and the app was not written to handle the failure, it waits forever. The server may be down, out of space or blocked by a changed setting.

  2. The phone cannot find the server's address

    A changed domain, an expired domain or a wrong address in the release makes the first call fail before it reaches your server at all.

  3. A setting or key is missing in the release build

    An app can run fine in testing and stall in the store version when a configuration value, such as a Firebase setup, was not included in the final build.

  4. A file the app needs was left out of the release

    If an image, a font or a data file was not packed correctly, the first screen cannot be drawn and the app waits on it.

  5. The app is stuck doing slow work on its main thread

    Android calls it an Application Not Responding error when an app has not reacted to a touch within 5 seconds. Android names slow work on the main thread, such as heavy reading of data, as a common cause.

What can I do about it today?

  1. Check your server and website firstOpen your website and, if you have one, the admin panel on a computer. If they are also slow or down, the app is a symptom, and this is a server problem.
  2. Try another phone and another networkTest on a second phone and on mobile data instead of Wi-Fi. Write down which combinations get stuck.
  3. Note the app version and the date it startedOpen the app's information page on the phone and write the version number. If it began right after a release, say so.
  4. Record the screenUse the phone's built-in screen recording for the whole attempt. A short video tells me more than a description.
  5. Do not publish a new version in a hurryA second rushed release can add a second problem. If the last release caused it, ask your developer or me for a safe way back.
  6. Check the domain and hosting are paidAn expired domain or a suspended hosting account stops the app's first request. Look in your email for notices from the registrar or the host.

When should I bring someone in?

  • The website or admin panel works but the app does not, and you do not know why.
  • It started after a release and nobody can say what changed.
  • Customers are blocked from ordering, booking or logging in.

How do I handle it?

  1. Reproduce it on a deviceI run the same build the store has and watch what the first screen is waiting for.
  2. Separate app from serverI check whether the call the app makes on start succeeds from outside the app, so I know which side to repair.
  3. Fix the cause, then add a safe failureOnce the cause is repaired, the first screen is changed so that a failed call shows a message and a retry button instead of a spinner without end.
  4. Release with a way backA fixed build is tested before it goes out, and the previous working build stays available. A store's review time is its own, so I cannot promise when users get it.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Is it my phone or the app?

If a second phone on a different network gets stuck in the same way, it is the app or the server. If only one phone does, restart it and update the app first.

Why did it work in testing and not in the store?

A store build is packed differently from a test build, so a missing setting or file only shows up after release. That is one of the first things I compare.

Can the server be fine and the app still hang?

Yes. A wrong address, a missing setting or slow work inside the app can stall it while the server is healthy.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.