Launching External Apps
Over time, Android is restricting more and more how applications can access files on device shared storage like SD cards, and how applications can pass references to those files between each other. With eLibrary Manager version 3.1.4 on Android 7.0 and greater, the application is changing how it integrates with external applications, including external book readers (i.e. non-ePub book readers, or alternative ePub book readers) and image viewers.
If you use eLibrary Manager to launch external book reader or image viewer apps, you won't notice any changes if those apps have migrated to one of the new and sanctioned Android file sharing mechanisms. However, if those external apps have not been updated, you may find that you can no longer launch them.
If you encounter such issues, you can download and install the eLibrary File URI Launcher add-on app that allows the newest versions of eLibrary Manager to maintain the old behaviour. This add-on app simply intercepts "new style" external app launch requests and converts them to the "old style". See the links below for downloading and installing the add-on app.
More Technical Details (for anyone who is interested)
As of Android 7.0 (SDK level 24), apps that target SDK 24 or greater can no longer launch activities (i.e. app interfaces) using file URI intents. Instead, content URI intents must be used in their place. Any app attempting to use a file URI intent will fail with a runtime exception.
If installed, the eLibrary File URI Launcher add-on app is able to translate launch requests from eLibrary Manager into a file URI request that it then sends to external apps that support them. The add-on can accomplish this because it targets SDK level 23 and therefore is still able to use the old app integration mechanism.
eLibrary File URI Launcher
There is no setup required for the eLibrary File URI Launcher add-on app. Simply install it and it should do its job.
Or download from eLibrary File URI Launcher (File name should be eBookFileUriLauncher.apk. Your browser may have renamed it on download.)