Opening image files from file manager does not work

Expected behavior

When opening an image file, BinaryEye should be one of the apps available for selection and, if chosen, decode any supported codes within the image file to text.

Actual behavior

I’m running Android 8.1.0 and BinaryEye 1.20.1 When opening an image file, the native Android “open-with” application picker does not include BinaryEye.

In the (proprietary) file manager FX (nextapp.fx), there is a built in “open-with” application picker. It shows an entry for BinaryEye [which is why i’d expect it to support opening a file this way]. Howerver, the entry is marked with a red x-icon and, once tapped, triggers a message that reads: “The selected app does not support opening this item using a “Content URI”. As of late 2018 Google has required apps to only use Content URIs for opening files. You may need to update the target application or contact its developer.”

Proposed solution

Is it possible to implement Content URI support in BinaryEye?

[SebiderSushi]

Otherwise, from the Android Developer Guide about Intents, i think this is the section relevant to this topic of Content URIs. It seems to me that the issue would be connected to declaring the scheme “file” in this line in BinaryEye’s manifest.

[SebiderSushi]

Sweet! Since i don’t use Google Play i have tried the APK from the releases page and it works for me as well. Now waiting for the update to be published by F-Droid. Thank you for fixing 😃