GOWOD mobility test won’t finish? Try these fixes in order

03Rule out a connection interruption without losing your place

A test can appear frozen while the app is trying to load the next screen or show a result. Before closing it, I check whether the phone has a usable connection. I switch between Wi-Fi and mobile data only if one is available and working, then return to GOWOD and give the current screen a moment. This is a small change that leaves the test itself alone.

I also look for a connection warning rather than treating every pause as the same problem. At home, a weak signal in the room where I stretch may be enough to make a screen hesitate; in that case, moving closer to the router is simpler than changing app settings. I would not start the test again until I knew the current screen was still unresponsive.

This check fits into an ordinary interrupted day: a takeout pickup message or a food delivery arrival can pull me out of a stretch without meaning anything has failed. When I return, I first make sure GOWOD is still on the test screen. If the connection is sound and the controls still do nothing, reopening the app is the next reasonable step.

04Reopen GOWOD, then check whether the test saved your place

I leave the test screen, close GOWOD from the phone’s recent-apps view, and open it again. Then I return to the mobility test and look for a way to continue. I do not assume it has saved every movement; I check the screen before starting over. If it resumes, I can carry on without changing any settings.

If it opens at the beginning, I would redo the test when I have enough uninterrupted time to follow the movements properly. I would not rush through them to recover my place. A baseline that reflects what I can actually do is more useful than one assembled while I am watching the clock for restaurant reservations or another appointment.

If the app closes unexpectedly each time I reach the same point, I note that point before doing anything more thorough. “It stops while showing my result” is more useful than “it’s broken,” both for choosing my next check and for describing the problem if I need help. The next step is to look at the app itself, not my stretching technique.

05Check Google Play before clearing app data

I open the Google Play listing for GOWOD and check whether an app update is available. An update is worth trying when a screen repeatedly stops responding, particularly if reopening the app made no difference. After installing it, I reopen the test and check whether I can move past the same point. I would make this check before clearing storage because it is less disruptive.

I also restart the phone if the app is still unresponsive. That clears a temporary phone-level hiccup without asking me to remove the app or erase its data. On my Galaxy A-series phone, I would then open GOWOD directly, rather than moving between it and event tickets or messages while trying to establish whether the test works.

Clearing app storage is a much bigger step: it can remove locally held information and require me to sign in again. I would leave that alone while there are simpler checks to try, especially if I am unsure of my sign-in details. If the problem survives an app update and a phone restart, I would gather the details needed to ask for help.

06If the same screen still sticks, report the exact point

I would use GOWOD’s available support route and describe the screen where the test stops, what I tapped, and whether the app froze or closed. I would include my phone model and whether the problem happens on Wi-Fi, mobile data, or both. Those details separate a repeatable test-screen issue from a one-off connection interruption.

I would keep the report focused on the mobility test. GOWOD also offers sport-specific routines and protocols such as ACTIVATE and RECOVER, but a routine that feels unsuitable is a different question from a test that will not finish. If I can open other parts of the app, I would say so; if I cannot, I would say where access stops.

While waiting, I would avoid treating an unfinished test as a completed baseline or using it to judge progress. The useful goal is to get through the instructions and see the result without guessing. Starting with the on-screen control, then the connection, then a fresh app session gives me the best chance of doing that without unnecessary changes.