-
Notifications
You must be signed in to change notification settings - Fork 5
Halifax Mobile Banking #309
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
Comments
By the way @akc3n, the issue form requests that you add the appropriate country label but only people with triage permissions can do that (I'm not sure if it's geared towards the general population or for internal members though). |
@brxken128 thanks for reminding me of that. I'll update the instructions on the form. |
Are reports from the same bank, but different devices supported? I just flashed my Pixel 8 pro and use 4/5 UK banking apps. |
@brxken128 Yes. Issue authors may edit their own banking app report, add additional devices they've tested on, and update the notes field to reflect changes, if any possible solutions for
For non-authors of a submitted banking app report it might be best to add a comment with those details. That way users and contributors whom subscribe to specific app reports can be notified of changes. Making compatibility with GrapheneOS easier to track.
I should make a snippet template for this sort of things to make things easier when contributors wish to update others banking app reports in the comments. |
Thanks to the recent improvements in avoiding detection by third party sdks and also working around buggy play integrity implementations, Halifax appears to be working again. |
I'm still having problems with Halifax (and mirrored in Lloyds app) on their version 156.03, currently on GOS 2025030800. After switching on Exploit protection compatibility mode and clearing storage, the first launch took me through the enrolment process, called me with a 4 digit code, and let me in to my accounts. |
@doogstar Did you call them? |
Can confirm that I'm suffering from the same issue as @doogstar Deregistered device for security after it was all set up |
Marking incompatible again. Are you notified of play integrity usage at any point? Keep me updated if anything changes. |
Been through the process again, verified pin through the automated call then same message. No play integrity notification shown. Have written down number and will plan to call them, especially as my old backup phone has started receiving notifications that they're going to drop Android 7 support from the app shortly, so that won't be an option anymore. Depending on what they say will probably start a formal complaint. |
Same hear. No play integrity and it let's me get through the whole process again before saying it is getting deregistered for security. As far as I remember, this never happened on my old phone with stock ROM. If there's any other information you need, let me know. I haven't collected much else though |
Is there an existing issue for this?
App name
Halifax Mobile Banking
Link to app
https://play.google.com/store/apps/details?id=com.grppl.android.shell.halifax
App version
123.04
Country of the app
United Kingdom
Build Number
UP1A.231005.007.2023101300
Device list
Pixel 6
Profile app tested in
Secondary profile(s)
Google Play installed
Installed
Google Play services Network permission revoked?
Native code debugging
Exploit protection compatibility mode
Stock OS compatibility
NFC payments
Description of the app's functionality
The app works great, although signing in is a pain if you use a randomly generated password as switching between a password manager and the app resets all of the details - I think this is just the app, and no fault of gOS as I've experienced it on my stock P8 Pro (will be installing gOS on that shortly, I'm pretty certain it'll still work fine though).
Of course, there's no working Google Wallet integration.
Are there any extra notes you think users should know about?
As with my last submission, I'm not 100% on the build number but it was the 2023101300 release.
ADB logcat of the app if necessary
No response
The text was updated successfully, but these errors were encountered: