status-im
Xiaomi, Nothing: QR Scanner in app fails
Bug Report
Reproduction
- Create a new user A.
- Navigate to Messages -> Add Contact -> QR Scanner.
- 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
- Status version: release
- Operating System: reproduce only on Xiaomi 11 Lite with Android 13 Status-debug-logs (5).zip logcat.zip
Oh, just saw "reproduce only on Xiaomi 11 Lite with Android 13" , unassign myself
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?
@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?
@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
Not n my Xiaomi 9T Pro (Android 10)
so I suppose might be very specific to device / Os combination.
We'll keep an eye on user reports in regards to this issue, so far it is only one device
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
It looks like more people are encountering this issue, so I’ve added it back to the milestone for investigation.
cc @ilmotta to prioritize
It looks like more people are encountering this issue, so I’ve added it back to the milestone for investigation.
cc @ilmotta to prioritize
@churik could you elaborate more on "more people are encountering this issue"? Which devices were they using? By people do you mean CCs or have you got feedback from users?
@ilmotta Affected devices confirmed by users: Nothing phones (seems affected all devices, checked on Nothing phone 2 and 3, nothing OS 3.1, based on Android 15)
https://github.com/user-attachments/assets/b41e8e13-71f9-448b-976b-bfe862e35167
Logs (haven't find anything useful though there):
Changed the issue description
Thanks @churik for updating the issue with a new brand.
@status-im/mobile does anybody have a Nothing phone or a Xiaomi to diagnose this issue?
We have a minuscule percentage of users with Nothing phones according to Google Play statistics, so according to our official device support we can't guarantee support for Nothing OS. If one of the CCs have the hardware available we can give a quick try, otherwise this issue can't be resolved now.
Xiaomi does have a larger audience, but still on the lower end.
@ilmotta I wonder if we really can fix this.
Seems an issue from the library, instead we could submit an issue in lib's repo with the details of the affected devices. Wdyt?
@ilmotta I wonder if we really can fix this.
Seems an issue from the library, instead we could submit an issue in lib's repo with the details of the affected devices. Wdyt?
Which lib @ulisesmac? We have this other issue about replacing react-native-camera-kit https://github.com/status-im/status-mobile/issues/20346, and I'm wondering if we could fix the issue by using this library. But without a Nothing phone there's not much devs can do.
It's good practice to submit issues with as much detail as possible, but the video is insufficient to pinpoint the cause and the logs are not helpful, so I'd personally not submit an issue yet.
Side notes:
- Looking at Nothing OS repos https://github.com/NothingOSS?tab=repositories, they barely have any activity and the most active one doesn't have a single issue open.
- This is a great example of an issue that could be addressed by external contributors because we have limited capacity to test and develop in all known devices/OSes.
@ilmotta
Someone reported it here but didn't provide enough info:
- https://github.com/teslamotors/react-native-camera-kit/issues/322
If the amount of unsupported devices increases, we should try other libs, Xiaomi is very popular in development countries, which we've seen are an important part of our users.