-
-
Notifications
You must be signed in to change notification settings - Fork 259
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
Android 13 (SDK 33): CropImageView white on some Samsung devices #599
Comments
Can you reproduce and try to submit a PR which fixes this? |
Facing same issue on my samsung device. I can see the image with crop square but white screen all around. |
Same issue here. But not just Samsung Phones. Motorola phones too. I don't have direct access to the devices facing the issue. |
Facing the same issue on my Vivo device. I can see the image with a crop square but a white screen all around. there is no option to go back and get the cropped image's Uri. |
Same issue here. I Could handle it by implementing a CustomCropImageActivity as stated in documentation and in sample app. Custom activity code
Custom Activity Layout
And this is the code to start the activity.
The custom contract here
|
@vanniktech |
@vanniktech Is this issue fixed in the latest release? |
Has something changed since my last comment? #599 (comment) |
Same issue here, using a Pixel 6 emulator with API 34. |
Roll your own activity and just use the CropImageView. Or alternatively use the workaround: #599 (comment) Long term, I want to get rid of all the contracts & CropImageActivity. |
Hi,
I've an app with 100k+ installs out there. Recently I've updated the target SDK version to 33 without changing anything on the image cropping code. Since that update I receive lots of complaints from users with various (not all) Samsung devices running Android 13 saying that the CIV doesn't load the chosen image and just stays white.
I load the image using the setImageUriAsync() method. Unfortunately I was not able to reproduce that bug on my test devices (which are not made by Samsung). I was also not able to reproduce it using Samsung's Test Lab devices.
But by the amount of bug report messages (including screenshots showing the behavior) I get, I can say for sure, that there is a bug.
(This could by the same bug mentioned here: #593)
The text was updated successfully, but these errors were encountered: