Flipper doesn't work with apps originally installed on the system partition

🐛 Bug Report

@passy I set up Flipper in our app. It worked on a (non-64 bit) emulator but when I run in on our kiosk-like hardware, Flipper shows a bar that says: Client setup error: No matching device for app: PACKAGE_NAME

Flipper can see it for its generic features like logs and CPU info. However, it doesn’t connect to the FlipperClient.

EDIT I did some debugging and found that the run-as command here is failing with PACKAGE_NAME is not an application. I tracked that down to here which is the case when the app is a system application. In our case, I have installed a debuggable version of the app over the one on the system partition and that is the setup that 100% of people here will be using when working.

To Reproduce

You can push an APK to the system partition by booting an AVD with -writeable-system (StackOverflow link). Then push your own apk to the system partition and optionally install it again in the user partition.

Expected Behavior

Flipper connects to the FlipperClient.

Environment

Our Kiosk-like hardware runs Marshmallow.

Thanks for working on Flipper. It looks really awesome and we have some ideas for useful plugins that we can build already.

[gpeal]

Please leave this open. It is still an issue.

[gpeal]

This still requires attention.