-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Crash when trying to upload via image selector on first use #6131
Comments
@sivaraam Taking this issue |
Not able to reproduce the issue in v5.1.2 |
I think I've mentioned that in the description itself. This issues only happens on the |
I synced with the latest main branch and followed the steps outlined in the issue description, but I’m still unable to reproduce the crash on my device. I’ve tested with a clean installation and different scenarios, but the app behaves as expected. |
@sonalyadav1 Perhaps it is device/etc-specific? Maybe better leave the issue to someone who happens to be able to reproduce the issue, if that's OK with you? Thanks for checking! |
@nicolas-raoul It’s possible that the issue is device or environment-specific, and since I’m unable to reproduce it on my setup, I’m happy to leave this issue to someone who can replicate it more reliably. |
Indeed @savsch . I'm no longer able to reproduce in the latest |
Summary
The app crashes when trying to do an upload using the normal file picker for the first after installation. This happens on the latest
main
. The second upload seems to correctly take us to the upload screen, though. We should look into fixing this as it is not a good UX to crash upon first upload.Steps to reproduce
Expected behaviour
The app should proceed to the upload screen after the permission has been granted.
Actual behaviour
The app crashes with the crash log given below.
Device name
OnePlus Nord
Android version
Android 12
Commons app version
main (does not happen in v5.1.1)
Device logs
Screen-shots
Screen recording to demonstrate the issue
Would you like to work on the issue?
None
The text was updated successfully, but these errors were encountered: