[com.plumelabs.flow] Unable to log into an app #842

ghost · 2019-06-19T04:04:18Z

Hi there,

I'm unable to use a really specific app of my collection (Flow, package=com.plumelabs.flow).
The app launches correctly, but recquire immediatly to log in, and whereas there is absolutely no problem with this step on another GAPPS phone, it's been at least 3 times with 3 different roms I'm facing the same issue with microG: can't log in, having a loading circle looping infinitly.
Here is the corresponding logcat :

06-17 23:47:18.814 I/FirebasePerformance(19092): Session ID - 4aca52a6838f4ec981d9d07922d89453
06-17 23:47:18.815 D/Logger  (19092): (Application.kt:65) LoginActivity started
06-17 23:47:18.815 D/FirebasePerformance(19092): Creating a new Non Verbose Session: d60752291be14690aad0afb8ac72afb5
06-17 23:47:18.818 D/Logger  (19092): (Application.kt:61) LoginActivity resumed
06-17 23:47:18.821 W/ActivityManager(16239): Unable to start service Intent { act=com.google.android.gms.config.START pkg=com.google.android.gms } U=0: not found
06-17 23:47:18.821 W/ActivityManager(16239): Unbind failed: could not find connection for android.os.BinderProxy@7f37fd3
06-17 23:47:18.821 E/GmsClient(19092): unable to connect to service: com.google.android.gms.config.START on com.google.android.gms
06-17 23:47:18.824 D/GmsMeasureBrokerSvc(17687): onBind: Intent { act=com.google.android.gms.measurement.START pkg=com.google.android.gms }
06-17 23:47:18.826 D/GmsClearcutSvc(17687): onBind: Intent { act=com.google.android.gms.clearcut.service.START pkg=com.google.android.gms }
06-17 23:47:18.831 W/FirebaseRemoteConfig(19092): IPC failure: 17:API: Config.API is not available on this device.
06-17 23:47:18.835 D/SafeParcel(17687): Unknown field num 10 in com.google.android.gms.common.internal.GetServiceRequest, skipping.
06-17 23:47:18.835 D/SafeParcel(17687): Unknown field num 11 in com.google.android.gms.common.internal.GetServiceRequest, skipping.
06-17 23:47:18.835 D/SafeParcel(17687): Unknown field num 12 in com.google.android.gms.common.internal.GetServiceRequest, skipping.
06-17 23:47:18.835 D/GmsClearcutSvc(17687): bound by: GetServiceRequest{serviceId=CLEARCUT_LOGGER, gmsVersion=12451000, packageName='com.plumelabs.flow', extras=Bundle[{}]}
06-17 23:47:18.839 D/GmsClearcutLogSvcImpl(17687): log: LogEventParcelable[1, PlayLoggerContext[1, package=com.plumelabs.flow, packageVersionCode=78, logSource=-1, uploadAccount=null, loggingId=-1, logAndroidId=false, logSourceName=FIREPERF, isAnonymous=true, qosTier=0], LogEventBytes: CKLDoru2LTKjAQpoCigxOjEwMzE1NTYzODIzMzc6YW5kcm9pZDo4ZDliZGY3NDZkZjMxMTM1EgtkbVRLWU1iU3ZXMBotChJjb20ucGx1bWVsYWJzLmZsb3cSDzEuMC4wLjIyNTA1MzI1NhoGMS4yLjAzKAMSNwoDX2JzINi02vC+8eICKK/2ghVKIgogZDYwNzUyMjkxYmUxNDY5MGFhZDBhZmI4YWM3MmFmYjV4wHCIAaKj9CE=, AddPhenotypeExperimentTokens: true]
06-17 23:47:18.843 I/LatinIME(16521): Starting input. Cursor position = 46,46
06-17 23:47:18.847 D/SafeParcel(17687): Unknown field num 10 in com.google.android.gms.common.internal.GetServiceRequest, skipping.
06-17 23:47:18.847 D/SafeParcel(17687): Unknown field num 11 in com.google.android.gms.common.internal.GetServiceRequest, skipping.
06-17 23:47:18.847 D/SafeParcel(17687): Unknown field num 12 in com.google.android.gms.common.internal.GetServiceRequest, skipping.
06-17 23:47:18.847 D/GmsMeasureBrokerSvc(17687): bound by: GetServiceRequest{serviceId=MEASUREMENT, gmsVersion=12451000, packageName='com.plumelabs.flow', extras=Bundle[{}]}
06-17 23:47:18.848 D/GmsMeasureSvcImpl(17687): onTransact [unknown]: 10, android.os.Parcel@4f6de2e, 16

Phone Model : OnePlus6

MicroG installation :

Using the NanoDroid installer (NanoDroid-21.0.20190601)

Has anyone an idea on how to troubleshoot this case ? That might be related to #404 #529 #497 and #310 but not so much information there since :

issue seems to have magically resolved with new release or
issue was related to a -dirty microG build or
user has got around not using the problematic app anymore

At this point, any help is welcome ;)

The text was updated successfully, but these errors were encountered:

Nanolx · 2019-06-19T22:40:58Z

Not related to the actual issue, but: you're not on the latest unofficial beta build (which is 0.2.7.14755-beta-80). See https://www.nanolx.org/fdroid/repo

Additionally the next version of NanoDroid will by default install the official microG build instead of the unofficial custom build (see https://gitlab.com/Nanolx/NanoDroid/commit/8e115c0dbc62281e336cc5c06c25e05733b21b22) and provide the mapbox instead of vtm build (see https://gitlab.com/Nanolx/NanoDroid/commit/1f57ba0567b313e78762354d64386d25fac3667e).

(another step to get rid of the unofficial build)

ghost · 2019-06-20T01:30:00Z

Still the same with version 0.2.7.17455-beta-80 (sorry for not having tested before, had a F-Droid cache issue, and thus didn't see the update earlier) unfortunately.
I'm gonna wait for the next NanoDroid release.

If ever you have the time for this, I'm having 2 questions by the way:

Can we just flash a NanoDroid new version right over another, or should we always uninstall any previous one and clean install a new one? Asking this because of all the already GCM registered apps.
If not, is there a way to reset the GCM registering process without having to backup data, reinstall and restore data?

Thanks by advance for any answer.

Nanolx · 2019-06-20T20:22:27Z

a) Why do you expect an uninstallation to be necessary? Just flash the update.
b) Yes, there is, if your device is rooted, run the following command in a shell: nutl -r (reset GCM connection for all apps) or nutl -r <appid> , e.g. nutl -r com.android.vending (reset GCM connection for specific app)

ghost · 2019-06-20T21:22:17Z

Ok about the updating process, thanks.
Oh yeah I'm sorry man I remember I saw it in the wiki but when I wanted to try it out previously (on another ROM), running su and then nutl -r , I had a "No command found" and couldn't figure out which package was necessary or what I did wrong.
It's now working as expected, don't know what is different from previous installation, but nevermind I got it now.
Thank you so much. Is this command still gonna work with official microG instead of your custom one ?

ghost · 2019-06-21T00:24:41Z

I don't think it's gonna bring more information, but I eventually tried with the 0.2.7.17455 official microG GMS (using nanodroid_gmscore=1 in the .nanodroid-setup config file) just in case, but sill the same :

06-21 02:09:35.227 W/BiChannelGoogleApi(31968): [FirebaseAuth: ] getGoogleApiForMethod() returned Gms: com.google.firebase.auth.api.internal.zzal@e3d1fb3

Nanolx · 2019-06-21T06:12:15Z

There's no (more) technical difference between both builds thus the error log is the same and yes nanodroid-util (or the nutl shortcut) works with both.

ghost · 2019-06-21T07:46:44Z

Ok, thanks for those precisions.
Hoping it won't be too much pain, I really want to thank you @mar-v-in and @Nanolx for all the hard work done so far to bring everyone this so useful and great alternative.
Have a nice weekend :)

starbrights · 2019-06-22T16:29:30Z

I am reading here because of #809
I am wondering howto find the problem in the many lines of locgat.

ghost · 2019-06-23T19:48:18Z

I am reading here because of #809
I am wondering howto find the problem in the many lines of locgat.

If you strip out the logcat to the actual moment where the issue showed up (like few sec around it), there are not so many lines, and it's suddenly easier to find the problem ;)
Also, it's easier if you have experience in debugging, and even more when you are the dev :D

ghost · 2019-07-04T13:29:03Z

With new version [0.2.8.17785-beta-1 (8b4852b-mapbox)], I got this when trying to log in, with still the loading circle looping forever :

07-04 15:17:10.658 W/BiChannelGoogleApi(21165): [FirebaseAuth: ] getGoogleApiForMethod() returned Gms: com.google.firebase.auth.api.internal.zzal@17578b1

x37-potter · 2019-07-08T16:42:07Z

Hello,
I am having the same issue on 0.2.8.17785-mapbox on the N26 app, can't go pass login.
Getting this error:

W ActivityManager: Unable to start service Intent { act=com.google.android.gms.config.START pkg=com.google.android.gms } U=0: not found
W ActivityManager: Unbind failed: could not find connection for android.os.BinderProxy@3929783
E GmsClient: unable to connect to service: com.google.android.gms.config.START on com.google.android.gms

mar-v-in · 2019-07-08T18:11:54Z

@voxitme microG does not support Firebase Auth so far, which very likely is the issue here. I will let you know once first support is there.

@x37-potter The log you presented is most likely not the issue causing you the problem. Can you provide further logs?

x37-potter · 2019-07-08T19:05:44Z

Here you go, thank you so much for your help!
log-number26.txt

ale5000-git · 2019-07-09T07:16:36Z

We need a dummy com.google.android.gms.config.START, I see it also in other issues and it appears multiple times in the log, it possibly not fix the problem but it will avoid many failed attempts.

ghost · 2019-07-09T20:51:02Z

Edit: I don't know what is happening with the formating... Can't manage to just type a * followed by a #...
See @ildar 's comment below (thanks for pointing this out !)

@x37-potter I personally never had an issue with the N26 app, Magisk not even being hidden to it...
Is it correctly registered in GCM ? Are other apps registered ?
If not (if not saying "Current state: connected since x" and not showing any apps list in the GCM menu), try this : go to the phone dialer and type

##2432546## (or ##CHECKIN##)

. Go back to microG and check if current state is now saying connected (don't remember if a reboot is necessary, maybe do it just in case). If yes, just uninstall reinstall N26 and all your other apps using GCM. They will appear in a list there.
Maybe that's useless for you but can help some others.

All of this is in the Nanolx's Nanodroid wiki.

x37-potter · 2019-07-10T06:19:50Z

Thanks, I didn't know about that wiki. Nope, I didn't manage to register it - the code didn't work (it said connected but no apps underneath).
Anyway, at the moment I had to uninstall microg because my phone becomes very slow and most apps don't start... I don't know what I did wrong.
Edit: I got it to work, thanks!

ildar · 2019-07-11T09:23:27Z

go to the phone dialer and type ##2432546## (or ##CHECKIN##).

bad formatting. Right is: `*#*#2432546#*#*` (or `*#*#CHECKIN#*#*`)

starbrights · 2019-10-15T08:54:14Z

long time no updates, is it under development or dropped?

ghost · 2020-07-27T13:04:22Z

Hey there,
I'm upping this post because I'm still having this issue after updating to v0.2.11.202414
Is there any information about this issue? I can provide a logcat if needed.

saradasama · 2020-09-21T10:50:16Z

Hey there,
I'm upping this post because I'm still having this issue after updating to v0.2.11.202414
Is there any information about this issue? I can provide a logcat if needed.

I am also very curious about this specific issue as the app still does not let the user log in even with the latest version of microG. Should I provide a log about this behaviour?

mar-v-in · 2020-10-13T20:14:39Z

This should be fixed in c3bfb63 (otherwise please reply so I can reopen).

ghost changed the title ~~ActivityManager: Unable to start service Intent~~ Unable to log into an app - ActivityManager: Unable to start service Intent Jun 19, 2019

mar-v-in added confirmed 🔑 Firebase Auth labels Jun 19, 2019

mar-v-in changed the title ~~Unable to log into an app - ActivityManager: Unable to start service Intent~~ [com.plumelabs.flow] Unable to log into an app Jun 19, 2019

Romern mentioned this issue Feb 6, 2020

Tier App not working (FirebaseAuth) #1013

Closed

GRBurst mentioned this issue Sep 28, 2020

Targeting Firebase Auth #1198

Closed

mar-v-in closed this as completed Oct 13, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[com.plumelabs.flow] Unable to log into an app #842

[com.plumelabs.flow] Unable to log into an app #842

ghost commented Jun 19, 2019

Nanolx commented Jun 19, 2019

ghost commented Jun 20, 2019 •

edited by ghost

Nanolx commented Jun 20, 2019

ghost commented Jun 20, 2019

ghost commented Jun 21, 2019

Nanolx commented Jun 21, 2019

ghost commented Jun 21, 2019

starbrights commented Jun 22, 2019

ghost commented Jun 23, 2019 •

edited by ghost

ghost commented Jul 4, 2019

x37-potter commented Jul 8, 2019 •

edited

mar-v-in commented Jul 8, 2019

x37-potter commented Jul 8, 2019 •

edited

ale5000-git commented Jul 9, 2019 •

edited

ghost commented Jul 9, 2019 •

edited by ghost

x37-potter commented Jul 10, 2019 •

edited

ildar commented Jul 11, 2019 via email •

edited

starbrights commented Oct 15, 2019

ghost commented Jul 27, 2020 •

edited by ghost

saradasama commented Sep 21, 2020

mar-v-in commented Oct 13, 2020 •

edited

[com.plumelabs.flow] Unable to log into an app #842

[com.plumelabs.flow] Unable to log into an app #842

Comments

ghost commented Jun 19, 2019

Nanolx commented Jun 19, 2019

ghost commented Jun 20, 2019 • edited by ghost

Nanolx commented Jun 20, 2019

ghost commented Jun 20, 2019

ghost commented Jun 21, 2019

Nanolx commented Jun 21, 2019

ghost commented Jun 21, 2019

starbrights commented Jun 22, 2019

ghost commented Jun 23, 2019 • edited by ghost

ghost commented Jul 4, 2019

x37-potter commented Jul 8, 2019 • edited

mar-v-in commented Jul 8, 2019

x37-potter commented Jul 8, 2019 • edited

ale5000-git commented Jul 9, 2019 • edited

ghost commented Jul 9, 2019 • edited by ghost

x37-potter commented Jul 10, 2019 • edited

ildar commented Jul 11, 2019 via email • edited

starbrights commented Oct 15, 2019

ghost commented Jul 27, 2020 • edited by ghost

saradasama commented Sep 21, 2020

mar-v-in commented Oct 13, 2020 • edited

ghost commented Jun 20, 2019 •

edited by ghost

ghost commented Jun 23, 2019 •

edited by ghost

x37-potter commented Jul 8, 2019 •

edited

x37-potter commented Jul 8, 2019 •

edited

ale5000-git commented Jul 9, 2019 •

edited

ghost commented Jul 9, 2019 •

edited by ghost

x37-potter commented Jul 10, 2019 •

edited

ildar commented Jul 11, 2019 via email •

edited

ghost commented Jul 27, 2020 •

edited by ghost

mar-v-in commented Oct 13, 2020 •

edited