[com.ing.banking] Scanning a QR-code is not working

[hrosseel]

Affected app
Name: ING Banking (Belgian ING banking app)
Package id: com.ing.banking

Describe the bug
When trying to scan a QR-code inside the application, the screen turns black (unable to open the camera) and an error message pops up saying: "Unable to scan at the moment. Please try again later".

To Reproduce
Steps to reproduce the behavior:

1. Click on 'Scanner' at the top right corner of the Overview
2. A black screen is shown with the error message: "Unable to scan at the moment. Please try again later."

Expected behavior
When using the scanner, the camera should open inside the application. The user can then scan a QR-code which gets automatically recognized by the application.

System
Phone: Pixel 6
Android Version: 12
Custom ROM: CalyxOS 3.1.1

microG
microG Core version: 0.2.22.214516-37
microG Self-Check results: All ticked

Additional context

Logcat outputs the following logs when pressing the "Scanner" button:

01-19 12:13:33.112 20312 20312 W GmsDynamiteLoaderImpl: No such module known: com.google.android.gms.vision.dynamite.ocr
01-19 12:13:33.112 20312 20312 D GmsDynamiteLoaderImpl: unimplemented Method: getModuleVersion for com.google.android.gms.vision.dynamite.ocr
01-19 12:13:33.112 20312 20312 W GmsDynamiteLoaderImpl: No such module known: com.google.android.gms.vision.ocr
01-19 12:13:33.112 20312 20312 D GmsDynamiteLoaderImpl: unimplemented Method: getModuleVersion for com.google.android.gms.vision.ocr
01-19 12:13:33.112 20312 20312 E Vision  : Error loading optional module com.google.android.gms.vision.ocr: com.google.android.gms.dynamite.DynamiteModule$LoadingException: No acceptable module found. Local version is 0 and remote version is 0.
01-19 12:13:33.113 20312 20312 W TextNativeHandle: Native handle not yet available. Reverting to no-op handle.
01-19 12:13:33.113 20312 20312 W GmsDynamiteLoaderImpl: No such module known: com.google.android.gms.vision.dynamite.barcode
01-19 12:13:33.113 20312 20312 D GmsDynamiteLoaderImpl: unimplemented Method: getModuleVersion for com.google.android.gms.vision.dynamite.barcode
01-19 12:13:33.113 20312 20312 D GmsDynamiteLoaderImpl: createModuleContext for com.google.android.gms.vision.barcode at version 1
01-19 12:13:33.114 20312 20312 W com.ing.bankin: Unsupported class loader
01-19 12:13:33.164   469 20310 I keystore2: keystore2::watchdog: Watchdog thread idle -> terminating. Have a great day.
01-19 12:13:33.168 20312 20312 W com.ing.bankin: Unsupported class loader
01-19 12:13:33.169  1495  1922 E system_server: Invalid class loader spec: =UnsupportedClassLoaderContext=
01-19 12:13:33.169  1495  1922 E PackageDexUsage: Unsupported context?
01-19 12:13:33.172 20312 20312 D SafeParcel: Unknown field id 3 in com.google.android.gms.vision.barcode.internal.client.BarcodeDetectorOptions, skipping.
01-19 12:13:33.175 20312 20312 W GmsDynamiteLoaderImpl: No such module known: com.google.android.gms.vision.dynamite.ocr
01-19 12:13:33.175 20312 20312 D GmsDynamiteLoaderImpl: unimplemented Method: getModuleVersion for com.google.android.gms.vision.dynamite.ocr
01-19 12:13:33.175 20312 20312 W GmsDynamiteLoaderImpl: No such module known: com.google.android.gms.vision.ocr
01-19 12:13:33.175 20312 20312 D GmsDynamiteLoaderImpl: unimplemented Method: getModuleVersion for com.google.android.gms.vision.ocr
01-19 12:13:33.175 20312 20312 E Vision  : Error loading optional module com.google.android.gms.vision.ocr: com.google.android.gms.dynamite.DynamiteModule$LoadingException: No acceptable module found. Local version is 0 and remote version is 0.

[ale5000-git]

Could you please retry with microG GmsCore 0.2.23.214816?

[hrosseel]

@ale5000-git, just tried it with microG GmsCore 0.2.24.214816-23 but got the same result.

[attah]

I and other Sailfish OS users are seeing a very similar problem with se.bankgirot.swish:

08-03 19:44:40.910  2436  2436 W GmsDynamiteLoaderImpl: No such module known: com.google.android.gms.vision.dynamite.barcode
08-03 19:44:40.910  2436  2436 D GmsDynamiteLoaderImpl: unimplemented Method: getModuleVersion for com.google.android.gms.vision.dynamite.barcode
08-03 19:44:40.911  2436  2436 D GmsDynamiteLoaderImpl: createModuleContext for com.google.android.gms.vision.dynamite at version 1
08-03 19:44:40.930  2436  2436 W bankgirot.swis: Unsupported class loader
08-03 19:44:40.944   727  1293 D MeasurementService: f1(com.google.android.gms.measurement.internal.EventParcel@188da46) for AppMetadata[se.bankgirot.swish]
08-03 19:44:40.965  2436  2436 W bankgirot.swis: Skipping duplicate class check due to unsupported classloader
08-03 19:44:41.068    57   519 I CameraService: CameraService::connect call (PID -1 "se.bankgirot.swish", camera ID 0) for HAL version default and Camera API version 1
08-03 19:44:41.068    42   392 E /system/bin/hw/[email protected]: Failed to get IAshmemDeviceService.
08-03 19:44:41.069    57   519 I Camera2ClientBase: Camera 0: Opened. Client: se.bankgirot.swish (PID 2436, UID 10044)

microG version: 0.2.24.214816

Anything more i could do to help in troubleshooting?

[hrosseel]

Bump. Anyone willing to look at this?

[Bishopsik]

I also have this error now and I am using a pixel 6 pro. Has a resolution been found? I find no other information online regarding this error.

[wstroow]

Hi, I experienced the same problem since yesterday (30/09/2022) although I have the ING Banking app already since a few years on the phone (and scanned QR's regularly). I have a Huawei P30, EMUI 12.0.0.134. And the weird thing is that the QR Reader app works perfectly, as well as I can scan QR with another foreign banking app. Someone a solution to the problem?

[hilder-vitor]

Same problem. Android 12, cellphone model: Redmi Note 10S.

[jpsaroud]

Same problem with galaxy S22

[ArchangeGabriel]

Similar issue with another apps to handle comics collection (https://play.google.com/store/apps/details?id=com.bdgest.bdgestmobile):

01-08 19:22:36.770 31093 31093 E ViewManagerAdapter_ExpoBarCodeScannerView: Error when setting prop barCodeTypes. Exception occurred while updating property barCodeTypes on module ExpoBarCodeScannerView: null
01-08 19:22:36.777 31093 31093 W DynamiteModule: Local module descriptor class for com.google.android.gms.vision.dynamite.barcode not found.
01-08 19:22:36.779  4422 13073 D ChimeraServiceProvider: query: content://com.google.android.gms.chimera/api_force_staging/com.google.android.gms.vision.dynamite.barcode
01-08 19:22:36.779 31093 31093 W DynamiteModule: Failed to retrieve remote module version.
01-08 19:22:36.787 31093 31093 I st.bdgestmobil: The ClassLoaderContext is a special shared library.
01-08 19:22:36.793 31093 31093 W GmsDynamiteLoaderImpl: No such module known: com.google.android.gms.vision.dynamite.barcode
01-08 19:22:36.793 31093 31093 D GmsDynamiteLoaderImpl: unimplemented Method: getModuleVersion for com.google.android.gms.vision.dynamite.barcode
01-08 19:22:36.793 31093 31093 I DynamiteModule: Considering local module com.google.android.gms.vision.dynamite.barcode:0 and remote module com.google.android.gms.vision.dynamite.barcode:0
01-08 19:22:36.793 31093 31093 D BarcodeNativeHandle: Cannot load feature, fall back to load dynamite module.
01-08 19:22:36.794 31093 31093 W DynamiteModule: Local module descriptor class for com.google.android.gms.vision.dynamite not found.
01-08 19:22:36.795 31093 31093 I DynamiteModule: Considering local module com.google.android.gms.vision.dynamite:0 and remote module com.google.android.gms.vision.dynamite:1
01-08 19:22:36.795 31093 31093 I DynamiteModule: Selected remote version of com.google.android.gms.vision.dynamite, version >= 1
01-08 19:22:36.796 31093 31093 D GmsDynamiteLoaderImpl: createModuleContext for com.google.android.gms.vision.dynamite at version 1
01-08 19:22:36.802 31093 31093 W st.bdgestmobil: Unsupported class loader
01-08 19:22:36.803 31093 31093 W st.bdgestmobil: Skipping duplicate class check due to unsupported classloader

So I guess the barcode module of dynamite is not yet implemented?

[ArchangeGabriel]

Though I read here that it should be implemented actually?

[ArchangeGabriel]

Though it’s interesting #1637 and #1639 were opened almost at the same time. So maybe something changed w.r.t. this API?