Closed PauliusRaskevicius closed 8 years ago
Futures throw ExecutionExceptions when the corresponding request throws an exception. Some part of Glide's load process fails and throws an exception, which triggers the ExecutionException.
Some errors are expected (I/O due to invalid image data, or flaky networks in particular), some are not. You'd need to inspect or log the ExecutionExceptions to determine their cause and whether or not they're expected.
The stack trace seems to point to this code:
} else if (exceptionReceived) {
throw new ExecutionException(exception);
Which means that this stack trace should have a "Caused by". Lacking that it seems that exception is received, but it is null
. This usually means that you called load(null)
.
The effect is based on what you do with this in VintedImageLoader
.
It can also mean that the decoder returned null, but with the built-in ones it's highly unlikely, check if it's possible that your model is null. For more on this see https://github.com/bumptech/glide/issues/859#issuecomment-173612899
Thank you for your help guys. Turns out we weren't using Glide.clear(target)
Can you please explain it in more detail? I'm not sure I understand, and it may be helpful if someone finds this in the future.
Hi, i have same issue But after read your comment, still cannot understand how to fix this. Please explain it in more detail .
Glide Version: 3.7.0
Integration libraries: OkHttp, v2.7.4
Device/Android Version: Equal distribution among all devices and Android versions
Issue details / Repro steps / Use case background:
Stack trace:
You can find loads of other relevant info here: http://crashes.to/s/f039183c34f
Unfortunately I can't provide screenshots or screen recording, because we're not really sure what this error means and what it impacts. Has anyone had something similar or knows what it means? We're trying to find out what visible impact this error has for our users.