DiskLruCache | Java implementation of a Disk-based LRU cache | Caching library

I am developing an app where I need to cache images such that I can retrieve them when the user is offline and they should also be accessible once the user closes and reopens the app.

I need something like

I have a GridView with images and i have populated it using Volley and cached the images using the below links. I want to access the selected image of GridView in a new activity from the cached implementation. I have searched here on StackOverflow but could not find how to access the cached images using their key(int this case the URL). i have followed these links but couldn't find anything:

Jake Whartons Volley CUstomization

VolleyImageCacheExample

Do I have to use the same LruCache object created in ImageLoder object in the second activity or is there any other way?

Imageloader object in Singleton class

This is the default implementation of LruCache object used. If someone could explain using the code below?

The App works fine when I export it as as a debug version with no errors at all however it crashes at launch when I export it as a release version.

I've attached the error from the Android Monitor

I'm getting an error in my app-level build.gradle where on the first support library I am using, it tells me that all com.android.support libraries must use the exact same version specification and that it's found versions 27.1.1 and 26.0.2. In my app-level build.gradle, there is no line using 26.1.0. Also, all compile statements have been changed to implementation, the compileSdkVersion is 27 and the targetSdkVersion is 27. To attempt to find the culprit, I ran:

Getting a strange gradle build error after integrating certain libraries, before that app was running fine, but now showing the following error.

We are migrating from Android Gradle plugin 2.3.3 to Gradle plugin 3.0.1. Our application consists of an Application module and a Library module. Several dependencies are transitive (connected using api keyword) but even making them non-transitive using implementation doesn't help. After changing all the compile-type dependencies to the new ones, debug build works well. However, release build with Proguard shows thousands of warnings (on 2.3.3 everything goes well)

In particular, I don't get why do we have such problems, when Android classes from library depend on Android classes from program (here are just few examples):

I am getting this error after updating Support libraries to 27.0.2.

I ran into a really silly issue. I can't assemble my project.

I created single projects for e.g. database managment, for an api, custom layouts, etc. Now I am trying to combine all of these projects into one, to build a single application.

But unfortunaley it does not work as excpected as I am getting this error:

Execution failed for task ':app:transformDexArchiveWithDexMergerForDebug'. com.android.build.api.transform.TransformException: com.android.dex.DexException: Multiple dex files define Lorg/apache/commons/io/IOUtils;

My dependencies tree is the following:

I am getting this error