keeps getting stuck on the “choose your country" button. The ‘next’ button doesn’t seem to work.

[teolemon]

What

• Hi,

I have just downloaded your app for the first time and it keeps getting stuck on the “choose your country" button. The ‘next’ button doesn’t seem to work. Any ideas on how to bypass this issue?

I’ve attached a screen recording to demonstrate.

RPReplay_Final1756916524.mp4

[monsieurtanuki]

For the record I couldn't reproduce this issue with a Pixel 2 emulator, when replaying the onboarding, with an app already in French. I even tried Ireland too ;)
I'm a bit surprised by "éire", that is currently supported by our country package only for Irish/Gaeilge.
I also tried in Irish+Ireland but still managed to click on the Next button.

[g123k]

We have also received messages on the support email.
It seems to be quite random (both Android and iOS).

[Hars465465]

Thanks for the context.
Given the intermittent and cross-platform nature of this issue, I’ll investigate the onboarding state and Next button enablement logic to see where it can become inconsistent.
I’ll share findings in a PR once I have a deterministic fix.

[Hars465465]

I traced the intermittent “Choose your country / Next button does nothing” issue to the onboarding Next button awaiting OnboardingLoader.runAtNextTime() before navigation.

On the Welcome page, runAtNextTime() shows a non-dismissible LoadingDialog and awaits _downloadData().timeout(4s). If this async future stalls, errors, or doesn’t resolve cleanly, navigation never executes, which matches the reported random behavior across platforms.

From a flow perspective, this download looks preparatory rather than required for rendering the next page. Before proposing a fix, I wanted to confirm whether this async step is intended to block navigation, or whether navigation should be guaranteed even if the download is slow/fails.

If this aligns with the intended onboarding flow, I’m happy to propose a small PR to make navigation resilient.

[monsieurtanuki]

Hi @Hars465465!
Interesting comment.

That said, I've just tried to use a 4 milliseconds timeout instead of 4 seconds: I've managed to get an exception, but that didn't freeze the app, that went to the next page.

E/flutter (26475): [ERROR:flutter/runtime/dart_vm_initializer.cc(40)] Unhandled Exception: TimeoutException after 0:00:00.004000: Future not completed
E/flutter (26475): #0      Future.timeout.<anonymous closure> (dart:async/future_impl.dart:1042:24)
E/flutter (26475): #1      Timer._createTimer.<anonymous closure> (dart:async-patch/timer_patch.dart:18:15)
E/flutter (26475): #2      _Timer._runTimers (dart:isolate-patch/timer_impl.dart:423:19)
E/flutter (26475): #3      _Timer._handleMessage (dart:isolate-patch/timer_impl.dart:454:5)
E/flutter (26475): #4      _RawReceivePort._handleMessage (dart:isolate-patch/isolate_patch.dart:193:12)

I've also tried with a different Exception List<int> test=[];print('${test[1]}');: an Exception again, visible in the logs only, but still going to the next page.

Were you able to reproduce the OP bug?

[Hars465465]

Thanks for checking this and for the detailed experiments.

I wasn’t able to reliably reproduce the issue described in the original report either (emulator or replaying onboarding), which seems consistent with it being intermittent and hard to trigger.

As you observed, explicit exceptions or timeouts still allow navigation to proceed. My concern was more about the case where the awaited future inside runAtNextTime() never completes (e.g. dialog lifecycle or async timing issues), in which case navigation would never be reached.

The intent of this PR is to act as a defensive safeguard so onboarding navigation is guaranteed in such edge cases, while keeping the existing preload behavior unchanged when it succeeds.

[monsieurtanuki]

My concern was more about the case where the awaited future inside runAtNextTime() never completes (e.g. dialog lifecycle or async timing issues), in which case navigation would never be reached.

In that case, you should be able to reproduce the case you are supposed to fix, with a Future.sleep(Duration(seconds: 10)) (or something like that).
Please do that.

[Hars465465]

Thanks for the suggestion.

I tested this locally by temporarily replacing the preload in runAtNextTime() with a long Future.delayed(const Duration(seconds: 10)) to simulate a non-resolving async task.

In that case, tapping Next on the Welcome page results in no visible action until the delay completes; navigation is blocked during that time, and the UI appears unresponsive. After the delay finishes, navigation proceeds.

This matches the failure mode I was concerned about: when the awaited future does not resolve promptly, navigation is never reached from the user’s perspective.

The intent of the PR is to defensively guarantee onboarding navigation in such cases, while keeping the existing preload behavior unchanged when it succeeds.