New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[com.greengot] Impossible to use my banking app #2017
Comments
Hi, |
Hello, |
It is possible that it is already solved but need testing to know for sure so we should wait the newer version. |
Okay, thank you. |
Hello, |
That's weird: I'm using MicroG |
Affected app
Name: [Green-Got]
Package id: [com.greengot]
Describe the bug
Impossible to use my banking app. I will talk about my case in more details, but I've seen similar report and I suppose that there is some other app which have the same problem. It is a problem that didn't exist several months ago, but it appeared maybe with app updates or MicroG updates or android updates, I don't know.
Just after logging into my account, just when the app is supposed to let me access the rest of the app, it gets stuck on the login screen and seems to keep trying to load indefinitely. Exactly the same thing happens when I open the application after closing it, except this time it's on the launch screen that the application gets stuck. So, impossible to access to the app and my banking account on my phone. As a result, to use this application, I have to use it on an Android tablet with Google Play Services. And it's by using it on this tablet that I've been able to observe certain differences and understand a little better exactly what the problem is, and I suppose that it has to do with authorizations and access to the Telephon and SMS from the application and/or MicroG. The best way to explain it is to show you with pictures, in the screenshot part.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
If the problem com from MicroG, I'm not an expert but I suppose it, it would be great if this problem could be patched and get my application working properly again and get access to the entire app and my banking account, and by the way the same thing for several others apps which have the same problem.
Screenshots
In these pics, it show what happen when the app is launched on the android tablet device with Google Play Services, this don't happen on my phone with MicroG on which the app just stay stuck, and show, I think, the problem on MicroG. In these pics, it happen at launching of the app after login and closing the app, but it is exactly the same thing just after login.
So, just after launching the app, it stay stuck on the launching screen (just like on my phone with MicroG) and I receive a notification, as you can see below.
After clicking on this notification, this small window appears over the app.
As requested in this window, I give the necessary Telephone and SMS access authorizations to Google Play Services in the settings page of the Google Play Services application. And just after that, the app work very well without any problem. And as long as I don't grant these authorizations, the application remains blocked indefinitely, just like on my phone with MicroG. That seem to be logical if it need some authorizations.
BUT it work only with Google Play Services, even if I allow the Telephone and SMS access to MicroG or all the access available for MicroG on his setting page, the app stay stuck at the launching screen or just after login.
System
Android Version: [13]
Custom ROM: [LineageOS 20]
microG
microG Core version: [0.2.28.231657]
microG Self-Check results: [All ticked]
Additional context
Because of this problem, I'm forced to use an other android device, which is not my phone but a tablet, with Google Play Services, only to use my banking app and to be able to access to my banking account, it's very annoying to not be able to use my banking app on my phone. And I've seen than I'm not alone in this situation.
And also, before this bug happened only on launching screen and not at login.
The text was updated successfully, but these errors were encountered: