You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Glide Version/Integration library (if any): 3.5.2 Device/Android Version: S4/4.4 Issue details/Repro steps: I found this one while working on #396. The error reported when handing Glide a "" to load is extremely confusing. Somehow Glide manages to acquire a ParcelFileDescriptor for "" which obviosly can't be opened. I'm guessing there's a catch-all else branch somewhere creating a ParcelFileDescriptor when parsing as anything else fails.
The same exception is displayed through log.tag.GenericRequest.
The URL String was acquired from a utility method like this (generalized):
An obvious workaround here is to return null, but it would help to have better message for those new to Glide (and experienced users too, I was puzzled for a few minutes too).
Glide load line:
Glide.with(context)
//.fromString() // optional, doesn't change a thing//.asBitmap() // only changes stacktrace slightly//.error(R.drawable.error) // displays correctly if provided
.load("")
.into(imageView)
;
Glide Version/Integration library (if any): 3.5.2
Device/Android Version: S4/4.4
Issue details/Repro steps: I found this one while working on #396. The error reported when handing Glide a
""
to load is extremely confusing. Somehow Glide manages to acquire aParcelFileDescriptor
for""
which obviosly can't be opened. I'm guessing there's a catch-allelse
branch somewhere creating aParcelFileDescriptor
when parsing as anything else fails.The same exception is displayed through
log.tag.GenericRequest
.The URL String was acquired from a utility method like this (generalized):
An obvious workaround here is to
return null
, but it would help to have better message for those new to Glide (and experienced users too, I was puzzled for a few minutes too).Glide load line:
Stack trace (with
.asBitmap()
):The text was updated successfully, but these errors were encountered: