Appsupport Epassi unable to log in

REPRODUCIBILITY: 100%
OS VERSION: 4.6.0.11
HARDWARE: X10 III
UI LANGUAGE: Finnish
REGRESSION: not sure, had a working app before but not sure if it was possible to sign in with recent versions of the app

DESCRIPTION:

I had a working Epassi app before but reinstalled it after update to 4.6.0.11. App launches but it is not possible to log in using SMS or email because of captcha. It is trying to use https://eu-api.friendlycaptcha.eu/api/v1/puzzle but that fails.

PRECONDITIONS:

STEPS TO REPRODUCE:

  1. install Epassi App
  2. select phone number or email and try to get a code

EXPECTED RESULT:

send code button activates and code is sent via SMS or email

ACTUAL RESULT:

captcha fails and there is a try again button which does not help

MODIFICATIONS:

opengapps

ADDITIONAL INFORMATION:

I have tried with older version of the app but that does not help

Do you have set up a default browser for the Android side? Mobilepay app was difficult to get authorized (semi-externally off the app) until I installed Vivaldi and it became the default browser, after which the authorization succeeded.

The Mobilepay app apparently relies to some extent on the chromium browser assets and then fails if it can’t find a default browser present in the Android system, or something.

1 Like

I tried that now but unfortunately it did not help. Maybe Epassi is using Android WebView which is quite old vesion.

You could try updating it by editing AppSupport’s system image, however it’s quite tricky operation.
Jolla should provide latest WebView instead, but we will wait long for any update…

On the other hand, I have Epassi logged in and working fine, so it seems to be just the login part that doesn’t work. I don’t dare logout to test though…

So, guys, what exactly are the magical incantations on Terminal that allow you to see what exactly happens within Android apps and where exactly the failure happens? I’m lost with the logcat business.

Have you tried running

journalctl --follow

as devel-su on Terminal to see if that gives any hint what happens when the authorization fails to happen?

devel-su appsupport-attach /system/bin/logcat

(Currently too lazy to find a good example of where this info is already present).

1 Like

No lines generated when I click try again for the captcha.

Same here.