The app us.personals https://play.google.com/store/apps/details?id=us.personals&hl=en doesn’t work anymore. The app itself boots, but you can’t sign up. Both sign up using a Google account and sign up using a phone number don’t work. Selecting sign up using a Google account opens a microG popup where you can select an account, but after selecting an account it fails and you get returned to the start screen. Selecting sign up using a phone number takes you to a screen where you can fill out a phone number, but then pressing the next button which should send a text message doesn’t send anything. I contacted Lex developers about this and they thought it might be a Firebase error. I am not an experienced Android developer so I don’t know if that information is of any use. In any case they didn’t think they could fix it. Can this be fixed in /e/OS?
I am using the latest version of /e/OS for my Fairphone 4, which is version 2.9 (Android 14).
you’d need to go through having adb logcat running while doing the register steps to yield a log that either microG issues can carry or the developers can figure out. Firebase is broad and the Auth component has different methods, not all are supported, see microGs wiki:
Still a stacktrace under the appid [us.personals] can help down the line - other folk to signal the need, developers to figure out what APIs they’d need to support.
Would help if there was an Android emulator version of /e/OS, but I discovered that I can disable developer mode easily so I tried it. However running adb logcat spams the output with a whole bunch of constantly logged messages such as lines starting with “sensors-hal”, “WifiHAL”, “cnss-daemon”. How do I get a usable log?
I tried running logcat with *:E (still got some spam but much less), and noticed this output that deviated from the pattern of regular stuff appearing right at the moment of pressing next on the screen where I filled in my phone number for verification…
04-15 15:15:52.662 8576 8576 E ndation.e.drive: Not starting debugger since process cannot load the jdwp agent.
04-15 15:15:52.724 8598 8598 E id.gms.unstable: Not starting debugger since process cannot load the jdwp agent.
04-15 15:15:53.496 8598 8619 E id.gms.unstable: Attempt to load writable dex file: /data/user/0/com.google.android.gms/app_cache_dg/7e8517018c5530a89d83337f7f5e177831596540/the.apk
04-15 15:15:53.648 630 642 E QC-time-services: Receive Passed == base = 13, unit = 1, operation = 2, result = 0
04-15 15:15:53.648 872 1182 E QC-time-services: Daemon: Time-services: Waiting to acceptconnection
04-15 15:15:53.650 872 1182 E QC-time-services: Daemon: Time-services: Waiting to acceptconnection
04-15 15:15:51.332 0 0 E audit : rate limit exceeded
04-15 15:15:54.716 7919 7919 E android.vending: Attempt to load writable dex file: /data/user/0/com.android.vending/app_cache_dg/7E8517018C5530A89D83337F7F5E177831596540/the.apk
And then a bit later…
04-15 15:15:55.939 8333 8333 E D : Failed to initialize reCAPTCHA config: No Recaptcha Enterprise siteKey configured for tenant/project *
And last…
04-15 15:15:53.630 0 0 E audit : rate limit exceeded
at best you file a logcat with the appid in the title with microG issues, link it to the existing #1967
pure speculation: device does not succeed in all Safetynet - or its successor - tests (selfcheck?), then enterprise recaptcha is triggered → what can’t be fulfilled, then firebase auth declines to send an SMS
that particular commit or change hasn’t made it yet to /e/s microg repo. /e/os devs sometimes import patches (or write their own) before upstream makes a release.
Unsure if the change addresses your issue - the error would be then Error handling incoming SMS (see try/catch) instead of the earlier failure at requesting the SMS.