Invalid Certain app crashes on Android 12, Poco f3, after Android 12 update

[Natesk]

Good day.

I would like to ask if there's a workaround (while the official devs are working on their app) for the crashing banking app (it opens for 0.5 - gray screen, then closes, no notification) for NFC payments and confirmation of transactions, since it limits my daily activities (this is the only way to confirm payments).

Since I installed MIUI 13 weekly on my Poco f3, everything works perfectly except this banking app. The official apps for seeing the accounts etc. works fine, but the other for confirming online payments and NFC payments doesn't.

I ran the ADB debugging and this is what I get regarding the app:

01-06 09:52:25.938  6046  6046 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-06 09:52:25.938  6046  6046 F DEBUG   : Build fingerprint: 'Redmi/alioth/alioth:12/SKQ1.211006.001/21.12.30:user/release-keys'
01-06 09:52:25.938  6046  6046 F DEBUG   : Revision: '0'
01-06 09:52:25.938  6046  6046 F DEBUG   : ABI: 'arm64'
01-06 09:52:25.938  6046  6046 F DEBUG   : Timestamp: 2022-01-06 09:52:23.829489828+0100
01-06 09:52:25.938  6046  6046 F DEBUG   : Process uptime: 0s
01-06 09:52:25.938  6046  6046 F DEBUG   : Cmdline: si.nkbmmdenarnica
01-06 09:52:25.938  6046  6046 F DEBUG   : pid: 5884, tid: 5884, name: .nkbmmdenarnica  >>> si.nkbmmdenarnica <<<
01-06 09:52:25.938  6046  6046 F DEBUG   : uid: 10263
01-06 09:52:25.938  6046  6046 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
01-06 09:52:25.938  6046  6046 F DEBUG   : Cause: null pointer dereference
01-06 09:52:25.938  6046  6046 F DEBUG   :     x0  0000000000000000  x1  0000000000000000  x2  0000000000000000  x3  0000000000000000
01-06 09:52:25.938  6046  6046 F DEBUG   :     x4  0000000000000000  x5  0000000000000000  x6  0000000000000000  x7  0000000000000000
01-06 09:52:25.938  6046  6046 F DEBUG   :     x8  0000000000000000  x9  0000000000000000  x10 0000000000000000  x11 0000000000000000
01-06 09:52:25.938  6046  6046 F DEBUG   :     x12 0000000000000000  x13 0000000000000000  x14 0000000000000000  x15 0000000000000000
01-06 09:52:25.938  6046  6046 F DEBUG   :     x16 0000000000000000  x17 0000000000000000  x18 0000000000000000  x19 0000000000000000
01-06 09:52:25.938  6046  6046 F DEBUG   :     x20 0000000000000000  x21 0000000000000000  x22 0000000000000000  x23 0000000000000000
01-06 09:52:25.939  6046  6046 F DEBUG   :     x24 0000000000000000  x25 0000000000000000  x26 0000000000000000  x27 0000000000000000
01-06 09:52:25.939  6046  6046 F DEBUG   :     x28 0000000000000000  x29 0000000000000000
01-06 09:52:25.939  6046  6046 F DEBUG   :     lr  0000000000000000  sp  0000000000000000  pc  0000000000000000  pst 0000000080001000
01-06 09:52:25.939  6046  6046 F DEBUG   : backtrace:
01-06 09:52:25.939  6046  6046 F DEBUG   :       #00 pc 0000000000000000  <unknown>

Is there a workaround I can use in MIUI 13 while waiting for the official fix, or is the only way at the moment to downgrade?

Thank you!

 

[Igor Eisberg]

This error says nothing useful.

 

[Natesk]

This error says nothing useful.

Sorry, do not know why I thought I'll copy the right lines with zero knowledge whatsoever.

mDenarnic@ is the (only) app that when I try to open, the gray screen appears and closes after < 0.5 s without any warning.

[ removed ]

Thank you!

 

[Igor Eisberg]

Sorry, do not know why I thought I'll copy the right lines with zero knowledge whatsoever.

mDenarnic@ is the (only) app that when I try to open, the gray screen appears and closes after < 0.5 s without any warning.

Here is the whole log while trying to open the app: uploaded on Zippyshare.

Thank you!

No, you caught the correct error. I'm just saying that the error says nothing useful. Looks very low-level and doesn't even have any backtrace. Only the app developers can fix that...

 

[Natesk]

No, you caught the correct error. I'm just saying that the error says nothing useful. Looks very low-level and doesn't even have any backtrace. Only the app developers can fix that...

Thank you for the quick response and all your work! Now I know where I'm at.