picasso: Images no longer displayed after killing/updating the app

When I install my app on my device, everything works perfectly. But when I update it (like using the “run” button from Android Studio), or just kill it (by swiping it from my “Recent apps”), the images are no longer displayed.

My code:

Picasso picasso = Picasso.with(mContext);
picasso.setLoggingEnabled(true);
picasso.load(url).into(viewHolder.mainPicture, new Callback() {
    @Override
    public void onSuccess() {
        Log.i(TAG, "PICASSO OK");
    }

    @Override
    public void onError() {
        Log.i(TAG, "PICASSO KO");
    }
});

Logs

08-27 16:22:41.266      654-654/io.shace.app D/Picasso﹕ Main        created      [R2] Request{http://192.168.0.5:9000/assets/medias/14ce899e-7021-44ef-b44d-bbab5307fa0f.jpg}
08-27 16:22:41.266      654-746/io.shace.app D/Picasso﹕ Dispatcher  enqueued     [R2]+2ms
08-27 16:22:41.276      654-762/io.shace.app D/Picasso﹕ Hunter      executing    [R2]+2ms
08-27 16:22:41.856      654-746/io.shace.app D/Picasso﹕ Dispatcher  retrying     [R2]+586ms
08-27 16:22:41.856      654-748/io.shace.app D/Picasso﹕ Hunter      executing    [R2]+587ms
08-27 16:22:42.576      654-746/io.shace.app D/Picasso﹕ Dispatcher  retrying     [R2]+1307ms
08-27 16:22:42.576      654-749/io.shace.app D/Picasso﹕ Hunter      executing    [R2]+1308ms
08-27 16:22:42.596      654-746/io.shace.app D/Picasso﹕ Dispatcher  batched      [R2]+1326ms for error
08-27 16:22:42.796      654-654/io.shace.app I/EventAdapter﹕ PICASSO KO
08-27 16:22:42.796      654-746/io.shace.app D/Picasso﹕ Dispatcher  delivered    [R2]+1528ms
08-27 16:22:42.796      654-654/io.shace.app D/Picasso﹕ Main        errored      [R2]+1528ms

Looks like a cache issue to me. The URL is obviously working (locally) since it’s working when I uninstall/reinstall the app. The image is not huge (58KB). It’s also the only image I’m trying to load so it’s probably not a cache size issue.

The code is inside getView() on a custom Adapter.

About this issue

  • Original URL
  • State: closed
  • Created 10 years ago
  • Comments: 40 (2 by maintainers)

Most upvoted comments

Its May-2022 and this issue still exist in v 2.71828. Can somebody reopen this