PrivSec-dev
Banca March
Is there an existing issue for this?
- [X] I have searched the existing issues
App name
Banca March
Link to app
https://play.google.com/store/apps/details?id=com.bancamarch.bancamovil
App version
v3.3.3
Country of the app
Spain
Build Number
UQ1A.231205.015.2023121200
Device list
Pixel 7 Pro, Pixel 6
Profile app tested in
Secondary profile(s)
Google Play installed?
Installed
Where did you install this app from?
Aurora Store
Google Play services Network permission revoked?
- [ ] Revoked
- [X] Not revoked
- [ ] I did not have Google Play services installed
Native code debugging
- [X] Allowed
- [ ] Blocked
Exploit protection compatibility mode
- [ ] Enabled
- [X] Disabled
Stock OS compatibility
- [X] Works
- [ ] Does not work
- [ ] Not tested
NFC payments
- [ ] Works
- [ ] Works but requires another service
- [ ] Does not work
- [X] N/A (Not supported by app)
- [ ] Not tested
Description of the app's functionality
The app worked fine before few latest updates and now just crash by start (unusable):
type: crash
osVersion: google/cheetah/cheetah:14/UQ1A.231205.015/2023121200:user/release-keys
package: com.bancamarch.bancamovil:202312010
process: com.bancamarch.bancamovil
processUptime: 3842 + 217 ms
installer: com.aurora.store
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.bancamarch.bancamovil/com.bancamarch.login.common.LoginActivity}: java.lang.NullPointerException: packageName can't be null
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3813)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3953)
at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:103)
at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:139)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:96)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2455)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loopOnce(Looper.java:205)
at android.os.Looper.loop(Looper.java:294)
at android.app.ActivityThread.main(ActivityThread.java:8216)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:552)
at com.android.internal.os.ExecInit.main(ExecInit.java:49)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:359)
Caused by: java.lang.NullPointerException: packageName can't be null
at android.os.Parcel.createExceptionOrNull(Parcel.java:3072)
at android.os.Parcel.createException(Parcel.java:3050)
at android.os.Parcel.readException(Parcel.java:3026)
at android.os.Parcel.readException(Parcel.java:2968)
at com.android.internal.telephony.ITelephony$Stub$Proxy.getCellLocation(ITelephony.java:8696)
at android.telephony.TelephonyManager.getCellLocation(TelephonyManager.java:2503)
at ze.c.k(CollectDeviceData.java:3)
at ze.c.h(CollectDeviceData.java:67)
at ze.c.g(CollectDeviceData.java:16)
at ze.c.<init>(CollectDeviceData.java:37)
at ze.c.<init>(CollectDeviceData.java:1)
at ze.c$d.y(CollectDeviceData.java:4)
at ze.l.i(MobileAPI.java:65)
at ze.l.j(MobileAPI.java:48)
at y3.c.a(RSAManager.kt:23)
at r3.b.onCreate(BaseLoginFragment.kt:26)
at androidx.fragment.app.Fragment.performCreate(Fragment.java:27)
at androidx.fragment.app.c0.e(FragmentStateManager.java:50)
at androidx.fragment.app.c0.m(FragmentStateManager.java:130)
at androidx.fragment.app.w.e0(FragmentManager.java:231)
at androidx.fragment.app.w.l1(FragmentManager.java:82)
at androidx.fragment.app.w.b0(FragmentManager.java:22)
at androidx.fragment.app.w.f0(FragmentManager.java:2)
at j2.a.p0(BaseActivity.kt:124)
at j2.a.onCreate(BaseActivity.kt:31)
at com.bancamarch.login.common.LoginActivity.onCreate(LoginActivity.kt:5)
at android.app.Activity.performCreate(Activity.java:8677)
at android.app.Activity.performCreate(Activity.java:8655)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1461)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3795)
... 14 more
Are there any extra notes you think users should know about?
No response
ADB logcat of the app if necessary
No response
I tried enabling exploit protection compatibility and disabling secure app spawning. I have given the app all the permissions it asked for and also have google play services and carrier services installed. Non of that helped nor made a slight difference.
Hello! The app launched fine on my 7a, running in a secondary profile with all security features set to default, installed from the play store & aurora store. I obviously can't proceed past the login page, perhaps it's set to login automatically and there it starts crashing? Consider reinstalling, ideally from the play store.
Hello,
Weird. On two phones the app crashes with the same crash report. On my wife's Pixel 6 and my Pixel 7 Pro. Already reinstalled on my Pixel 7 Pro, but without success.
Any clue from crash report?
Regards, Mike
On Thu, 2023-12-28 at 06:10 -0800, spring-onion wrote:
Hello! The app launched fine on my 7a, running in a secondary profile with all security features set to default, installed from the play store & aurora store. I obviously can't proceed past the login page, perhaps it's set to login automatically and there it starts crashing? Consider reinstalling, ideally from the play store.
— Reply to this email directly, view it on GitHubhttps://github.com/PrivSec-dev/banking-apps-compat-report/issues/372#issuecomment-1871211399, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APYRYAQXZEFTAKA45YU4PXLYLV4WDAVCNFSM6AAAAABBEUDEDWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZRGIYTCMZZHE. You are receiving this because you authored the thread.Message ID: @.***>
@somehuman60 Hi, thank you for submitting the crash report. I to was able to successfully install this app from using our Sandboxed Google Play Store. No issues with launching the app. However, like @spring-onion, I can't proceed past the login page. May you please confirm if this is an issue after you try to log in?
Are you using a VPN by chance? Some banks will block it. Have you tried completely removing Aurora store and removing the banking app, restarting the phone and trying in a fresh secondary profile without a vpn and through the sandboxed Google Play store? Have you made sure that native code debugging is in fact in set allow for this banking app?
Edit: Have you tried this in the owner profile? As this comment suggest here that it could be an upstream bug https://github.com/GrapheneOS/os-issue-tracker/issues/2969#issuecomment-1872592237 Perhaps it is related to your situation as well?
Hi,
Thank you for your Answer.
- As I write the app worked fine before and crash by launching. No chance to get login page and try to login. No setting for this app or whole GOS changed by me.
- Yes, the native code debugging is enabled for this app and all other apps. I have no reason to disable this for any app.
- VPN doesn't matter, because the app worked fine with VPN before. I tried again without VPN and crashed again. I tried on another phone with stock Android and it works fine with VPN.
- It's mystery for me, that fully working app suddenly crash by lauching, altough nothing changed on both phones, except a few GOS updates installed.
On Sat, 2023-12-30 at 14:22 -0800, akc3n wrote:
@somehuman60https://github.com/somehuman60 Hi, thank you for submitting the crash report. I to was able to successfully install this app from using our Sandboxed Google Play Store. No issues with launching the app. However, like @spring-onionhttps://github.com/spring-onion, I can't proceed past the login page. May you please confirm if this is an issue after you try to log in?
Are you using a VPN by chance? Some banks will block it. Have you tried completely removing Aurora store and removing the banking app, restarting the phone and trying in a fresh secondary profile without a vpn and through the sandboxed Google Play store? Have you made sure that native code debugging is in fact in set allow for this banking app?
— Reply to this email directly, view it on GitHubhttps://github.com/PrivSec-dev/banking-apps-compat-report/issues/372#issuecomment-1872617326, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APYRYAUBHVKCSN6DLB3OGZLYMCHZ5AVCNFSM6AAAAABBEUDEDWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZSGYYTOMZSGY. You are receiving this because you were mentioned.Message ID: @.***>
HI,
Have you tried completely removing Aurora store and removing the banking app, restarting the phone and trying in a fresh > secondary profile without a vpn and through the sandboxed Google Play store?
Tried now, the app crash with the same crash report as before.
On Sat, 2023-12-30 at 14:22 -0800, akc3n wrote:
@somehuman60https://github.com/somehuman60 Hi, thank you for submitting the crash report. I to was able to successfully install this app from using our Sandboxed Google Play Store. No issues with launching the app. However, like @spring-onionhttps://github.com/spring-onion, I can't proceed past the login page. May you please confirm if this is an issue after you try to log in?
Are you using a VPN by chance? Some banks will block it. Have you tried completely removing Aurora store and removing the banking app, restarting the phone and trying in a fresh secondary profile without a vpn and through the sandboxed Google Play store? Have you made sure that native code debugging is in fact in set allow for this banking app?
— Reply to this email directly, view it on GitHubhttps://github.com/PrivSec-dev/banking-apps-compat-report/issues/372#issuecomment-1872617326, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APYRYAUBHVKCSN6DLB3OGZLYMCHZ5AVCNFSM6AAAAABBEUDEDWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZSGYYTOMZSGY. You are receiving this because you were mentioned.Message ID: @.***>
Hi. Has anything changed for you since then? I'm thinking what else could be causing this...are you running a 3rd party launcher?
Hi,
No, nothing is changed. Still doesn't work, and no I don't use 3rd party launcher. I use GOS so as is, without changes or special settings. App worked before fine.
On Tue, 2024-01-16 at 07:52 -0800, spring-onion wrote:
Hi. Has anything changed for you since then? I'm thinking what else could be causing this...are you running a 3rd party launcher?
— Reply to this email directly, view it on GitHubhttps://github.com/PrivSec-dev/banking-apps-compat-report/issues/372#issuecomment-1894023019, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APYRYAQXFJQWTUQJW3WBTLLYO2O3HAVCNFSM6AAAAABBEUDEDWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJUGAZDGMBRHE. You are receiving this because you were mentioned.Message ID: @.***>
Might be a longshot. But I tried to download the app on my P6. I got a weird loop where I only got the splash screen and glitched out and tried going from portrait to landscape orientation. Turned out the app acted out due to my display settings, which was set to a low display size and font size. After I changed that I could boot up the app with no issues.
It doesn't sound like the issues you describe here, but wanted to mention it either way as it could potentially be the issue? But perhaps you haven't changed any settings like that.
When you started getting issues did you get it just after a GOS update or did you also update the Bank App in between?
I have not changed the display settings.
I don't use the app that often, but I noticed it after a GOS update. In the meantime there have been 2 updates for the app, and some GOS updates, but the problem is still there.
On Wed, 2024-02-07 at 01:46 -0800, eennoo wrote:
Might be a longshot. But I tried to download the app on my P6. I got a weird loop where I only got the splash screen and glitched out and tried going from portrait to landscape orientation. Turned out the app acted out due to my display settings, which was set to a low display size and font size. After I changed that I could boot up the app with no issues.
It doesn't sound like the issues you describe here, but wanted to mention it either way as it could potentially be the issue? But perhaps you haven't changed any settings like that.
When you started getting issues did you get it just after a GOS update or did you also update the Bank App in between?
— Reply to this email directly, view it on GitHubhttps://github.com/PrivSec-dev/banking-apps-compat-report/issues/372#issuecomment-1931661459, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APYRYAVEKQJ444E23CUF3BDYSNEOVAVCNFSM6AAAAABBEUDEDWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZRGY3DCNBVHE. You are receiving this because you were mentioned.Message ID: @.***>
Have you tried obtaining it from the play store? This seems like the next step here.
Also, if you insist on using Aurora Store, please at least make sure that it's using the "session installer", not native installer or anything else.
But beyond that, please try play store.
Yes, I tried this too. Installed from the play store, but without success. The same issue as before.
On Sat, 2024-02-10 at 05:17 -0800, matchboxbananasynergy wrote:
Have you tried obtaining it from the play store? This seems like the next step here.
Also, if you insist on using Aurora Store, please at least make sure that it's using the "session installer", not native installer or anything else.
But beyond that, please try play store.
— Reply to this email directly, view it on GitHubhttps://github.com/PrivSec-dev/banking-apps-compat-report/issues/372#issuecomment-1937005535, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APYRYASO6NVKQI6J2NHGF3LYS5XM3AVCNFSM6AAAAABBEUDEDWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZXGAYDKNJTGU. You are receiving this because you were mentioned.Message ID: @.***>