-
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
IllegalArgument IP:null #28
Comments
Thanks for the report and the test case! I'll look in to it. The null result exception is also probably not ideal... |
I just tried loading the image and was unable to reproduce this exception using the following snippet:
where test_image_view is:
Can you still reproduce this? If so can you paste the Glide line you're using? |
When loading these images on a listview the images don't load. I will mail you a sample code if needed. The best probable way to reproduce a lot of these bugs is to load images on a gridview from creating a list of images from onloadresouce in a webview. |
If you can send some sample code, I'm definitely curious. That exception will essentially only occur if BitmapFactory fails to decode a Bitmap from a given url, which should be pretty rare. It might be that the image has a huge or malformed header, but I'd expect that would be reproducible... |
I am using PullToRefresh + StaggeredGridView and Glide+Volley for image caching and everything works fine until I reach 100 image download. If I scroll back to top, I am getting the following error messages: 11-25 13:46:43.848: E/GLIDE(17027): IP: onImageLoadException model= |
@leventepal Thanks for reporting the problem, next time feel free to open a new issue if you're seeing an unrelated exception so we can keep the threads more or less on topic. That particular exception is because you're passing '/' as a path or a file uri to Glide. Make sure the uris or paths you pass in are valid files and it should work. |
Glide doesn't download few image urls and throws this exception but the image exists when I hit the url.
The text was updated successfully, but these errors were encountered: