Checklist
- I am able to reproduce the bug with the latest version given here: CLICK THIS LINK.
- I made sure that there are no existing issues - open or closed - which I could contribute my information to.
- I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
- This issue contains only one bug.
- I have read and understood the contribution guidelines.
Affected version
2.0.1
Steps to reproduce the bug
- Open the app
- Click on the top right people icon
- Press the QR code icon
- Switch from My QR tab to Scan
Expected behavior
It should open the Scan tab and show a the camera preview to scan someone else's QR code to verify
Actual behavior
The app crashes instantly when you try to switch to the scan tab
Screenshots/Screen recordings
https://github.com/user-attachments/assets/15c1dc5c-ab62-414e-85cb-1180dce9059d
Affected Android/Custom ROM version
Android 16
Affected device model
Nothing phone (2) / A065
Additional information
No response
Activity
4I tested it and I can confirm that it's a bug and the app crashes.
I'm also a Nothing user, in this case the 3a model, but I can also confirm that I have the same error
Still reproducible on Android 2.0.1, on two devices
Environment
- Bitchat Android 2.0.1, installed from Zapstore on both devices
- Phone A: stock Android with Google Play services
- Phone B: GrapheneOS
- Camera permission granted
Steps to reproduce
- Tap the people icon (top right)
- Tap the QR icon to open Verify
- Tap Scan
Expected behavior
The camera opens to scan the other person's verification QR code.
Actual behavior
The app crashes as soon as the camera should start. Same result on both phones, every attempt, so it doesn't appear to be specific to GrapheneOS or to a single device.
Related
Looks like the same crash as #970 (which includes a stack trace). PR #900 says it fixes this issue. Happy to test #900 on these two devices if that helps get it merged.
Drafted with the help of an AI assistant; reproduced and confirmed by me on the devices above.
I tested it and I can confirm that it's a bug and the app crashes.