-
Notifications
You must be signed in to change notification settings - Fork 6.1k
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
Only call ExifInterface on RAW/JPEG image formats. #3851
Comments
This might be something specific to Android Q betas, trying to get clarification |
Probably the same as #3383, unfortunately we can't control what they log. We might be able to avoid calling the support library for pngs though. |
What about possibly using the Exif support library? |
I try to use support library exif, I'm using AVD (API 29) |
I am getting the noisy logs as well. Photos are loading normally.
Logs are below :
Any plan to fix this soon ? |
Happy to jump in with bug report. Running on Android Q AVD (Pixel 3). Sad to say I am now unable to reproduce this, I guess the image has changed (we re-generate it on server every minute). If it happens again, I will attach it. Here is another one, but it works fine: Log:
|
same issue here. Is that possibly cause a bug in some devices? |
Same here Pixel 2XL, Android 10. |
I see a few options:
|
I am seeing the same issue.
|
Still happening on 4.10.0 |
same issue here |
happened on Oneplus 7 pro(Android10) |
Fixes #3851. PiperOrigin-RevId: 278010807
Fixes #3851. PiperOrigin-RevId: 278010807
Fixes #3851. PiperOrigin-RevId: 278010807
When release this? |
Are you using " new DrawableCrossFadeFactory.Builder(300).setCrossFadeEnabled(true).build()"? If you delete this, there is no problem, I don't know if it is caused by this. |
@sjudd when can we expect this to hit release? thanks |
same issues on Xiao Mi 8 (On android 10) |
Same issues on Pixel3a Android Q simulator. |
same issue on Google Pixel 2 On Android 10 |
same issue... is there any alternative for this problem ? |
Well I removed Glide over this issue - didnt really enjoy the logs being chock full of stack traces. |
all images are loaded, but I got a lot of useless text in logcat - can I disable it without changing image library to picasso ???? |
Same Issue for me also. But if i remove Requestoptions then there is no exception log.Why? |
I have changed
to
and got successfully decoded image instead of crash |
Take into account that ExifInterface 1.2.0-beta01 (androidx support library), adds support for WebP and PNG files, so instead of placing a RAW/JPEG exif filtering in Glide, probably would be better to wait for the next ExifInterface stable release. https://developer.android.com/jetpack/androidx/releases/exifinterface#1.2.0-beta01 |
same issue on Pixel 2(Android 10) |
Why issue closed? I still have same problem (( implementation 'com.github.bumptech.glide:glide:4.10.0' |
Why has this issue been closed. I still receive these errors on Android 10, and only on Android 10. Not only do i receive these annoying log messages but I load a lot of images and videos, and on Android 10, it is very slow. I tested this on a Pixel 1 device with Android 9, the images and videos were loading fast, when I updated the device to Android 10, with no change to the code the device started writing these logs and loading image and video thumbnails very slow. |
I also receive these errors on Android 10. This issue should definitely be reopened. |
Please reopen and fix, it's a major problem with Android 10! |
Glide 4.11 and onwards use the support library, but on android 10 you may still see these logs from other applications or the framework itself attempting to parse exif data For more information on exif redaction which may cause these logs and/or impact performance, see: https://developer.android.com/training/data-storage/shared/media#location-info-photos. If anyone sees Glide 4.11 or higher producing these logs, please file a new issue. I'm going to lock this one to reduce the noise. |
This file yields the following error trace from glide, even though it is rendered correctly. This suggests to me that it's either a noisy logger that should be configurable/suppressed or it should have more information as to what the consequences are of this
https://avatars3.githubusercontent.com/u/698437?v=4
The text was updated successfully, but these errors were encountered: