-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
N26 actions tab loads forever #1207
Comments
Hello, I have the same issue, and I can't make a transfer anymore on version 3.51.2 (202040000). |
@fdawans where did I say anything about downgrading? |
So you kept that version? |
@fdawans I uninstalled microG and switched to GApps |
Hi, I have the same issue. Tested with N26 version 3.51.2 and 3.52.202041002. I can't do development in java, but happy to help with testing, investigating and moral support :) |
I can confirm this, n26 version 3.45 is last version that is working. |
N26 3.53 works for me. |
(Just to be clear: in this version, they removed “Actions” and replaced it with “Card”, which just works) |
I'm closing it since it is no longer an issue. |
In N26, the actions tab shows a placeholder screen forever. If no GMS implementation is installed, this does not happen. I spent a decent amount of time tracking this down to the wallet API — I believe that its existence makes N26 think there is support (or makes it attempt to test for support), but since the IOwService does nothing, it just waits for a response forever. After some more searching, I also came across this Reddit thread, which arrives at the same conclusion.
I believe that #971, #372, and #626 are caused by this as well, and there's probably more apps out here with the same behaviour that haven't been reported yet (indeed, the N26 bug had a Reddit post but no relevant issue here), so this would probably be good to fix sooner rather than later. I spent quite some time looking through decompiler output and the GMS docs to see if I could figure out the exact sequence of events that would happen with Google's implementation (and thus the minimum necessary API implementation), but I'm not familiar enough with the GMS internals (or Android, for that matter) to do so.
Here's the logcat for posterity:
The relevant lines are of course the following:
The text was updated successfully, but these errors were encountered: