search

status-im / status-mobile

a free (libre) open source, mobile OS for Ethereum
https://status.app
Mozilla Public License 2.0
3.88k stars 984 forks source link

Scanner in app fails to scan QR codes from Desktop and Mobile devices #20990

Open Horupa-Olena opened 1 month ago

Horupa-Olena commented 1 month ago

Bug Report

Reproduction

  1. Create a new user A.
  2. Navigate to Messages -> Add Contact -> QR Scanner.
  3. Scan the QR code of user B’s profile from either a desktop or mobile device.

Expected behavior

The profile of user B should open on the mobile device.

Actual behavior

When pointing the scanner at the QR code, nothing happens.

Additional Information

qfrank commented 1 month ago

Oh, just saw "reproduce only on Xiaomi 11 Lite with Android 13" , unassign myself

briansztamfater commented 1 month ago

Might be related to #20891

J-Son89 commented 1 month ago

@ilmotta - imo this should be part of 2.31 work if not sooner

ilmotta commented 1 month ago

imo this should be part of 2.31 work if not sooner

If this issue is only reproducible in one device (or possibly a very small set of devices) then it is acceptable to ignore it for 2.30 @Horupa-Olena.

@Horupa-Olena which other devices did you check that did not fail?

ilmotta commented 3 weeks ago

@churik @Horupa-Olena since this is potentially a serious issue, could you confirm if the bug is reproducible in only one device or maybe not reproducible anymore?

@churik One thing we should consider is ensuring that all issues created by QAs and devs specify the exact revision used to reproduce the bug. This way, developers can precisely reconstruct the builds on their machines. Many issues currently only mention nightly or release which can be problematic. It's common for a developer to pick up an issue days or even weeks later, and by then, terms like nightly/release lose their relevance.

On the dev side, we can actually add this build-time info directly to the logs (in the db.json file to be exact), so that if the person shares the logs zip we can easily get the revision used.

Wdyt?

Horupa-Olena commented 3 weeks ago

@ilmotta Hi! I'm sorry, I was on vacation last week and didn't see your comment. On my device (Xiaomi 11 Lite with Android 13), the issue still occurs. However, this issue is not reproducible on the following devices: pixel 7a with Android 13; iPhone 11 pro max with IOS 17

churik commented 3 weeks ago

Not n my Xiaomi 9T Pro (Android 10)

so I suppose might be very specific to device / Os combination.

churik commented 2 days ago

We'll keep an eye on user reports in regards to this issue, so far it is only one device

churik commented 1 day ago

I found the second device where scanning is not working at all.

Nothing OS 2.6, Nothing Phone 1

Logs: Status-debug-logs.zip

At attempt to scan it there was an error "WalletConnect NaN version is not supported" and any QR (tried different - from profile, wallets etc) is not possible to scan - nothing happens.

https://github.com/user-attachments/assets/c3b036ba-fd04-4ee5-bfbf-ce6acf6e947f