Lidl Plus login gets stuck after SMS verification in Jolla Browser

Bug Reports
1

REPRODUCIBILITY: Always so far
OS VERSION: 5.2.0.17
HARDWARE: Jolla Phone 2026
UI LANGUAGE: German
REGRESSION: Unknown

DESCRIPTION:

When logging into the Android Lidl Plus app, the authentication flow opens in the Jolla Browser at accounts.lidl.com.
The login works up to the security verification step. After entering the 6-digit SMS verification code and pressing “Confirm”, the page shows some loading activity but then remains on the verification screen and does not continue.
Pressing “Confirm” a second time results in Lidl’s generic “There’s been an error” page.
Going back afterwards returns to the beginning of the login flow where the email address has to be entered again.

PRECONDITIONS:

- Android AppSupport enabled
- Lidl Plus Android app installed
- Existing Lidl account with SMS verification available

STEPS TO REPRODUCE:

  1. Open Lidl Plus.
  2. Start the login process.
  3. Lidl Plus opens accounts.lidl.com in Jolla Browser.
  4. Enter the email address and password.
  5. Select SMS as the security verification method.
  6. Enter the received 6-digit verification code.
  7. Press “Confirm”.
  8. Wait.

EXPECTED RESULT:

The verification completes and the authentication flow continues, eventually returning to the Lidl Plus app as a logged-in user.

ACTUAL RESULT:

Some loading activity is visible after pressing “Confirm”, but the browser remains on the SMS verification screen indefinitely.
Pressing “Confirm” again leads to Lidl’s generic error page (“There’s been an error / Sorry, something went wrong”).
Going back restarts the login flow from the email-address screen.

MODIFICATIONS:

ADDITIONAL INFORMATION:

I also tried opening the initial authentication URL manually in Atlantic Browser. There the Lidl authentication flow fails earlier and directly shows Lidl’s generic error page. Therefore I am reporting the Jolla Browser behaviour described above separately.

2

Try installing an Android browser, e.g. Firefox, and logging in that way, it should work. Once it’s installed, you may need to first set the Android browser as the default browser in the Android settings, which you can reach by going to the AppSupport settings and tapping the Android version number a couple of times. Then try logging in again.

5 Likes
3

That’s the standard use case for most android apps…

1 Like
4

A Chromium-based Android browser which is set as the default browser for Android is often needed to get through these signing-ups successfully and avoiding hiccups. Vivaldi browser is a good choice, I have had instances when a non-Chromium browser like Firefox didn’t do the trick.

Not having a preset default browser for Android is in my experience the usual culprit in failure.

1 Like
5

This doesn’t work because the native browsers can’t/don’t know how to redirect these requests back to the AAS container. As pointed out, using Android Browser, these redirects usually works, because the flow stays inside the AAS.

6

I did just successfully set up the Lidl Plus app, Finnish UI on my own phone. The set up procedure did specifically prompt that it moved over to Vivaldi browser.

As for setting the default browser in Android, I don’t think I had to do anything else but download Vivaldi from Aurora Store and then use it.

7

Thanks for all your feedback. I was hoping this would work with the native browsers, but it sounds like this is a limitation of the Android App Support boundary.

I was also hoping the setup would be more straightforward for new users, but for me using an Android browser is an acceptable workaround