Page 2 of 3

Re: Issue with android 9 call Java method

Posted: 22 Apr 2019 07:44
by anuraag
There is no other flow with "Send/Share Intent Received" trigger active?

Re: Issue with android 9 call Java method

Posted: 22 Apr 2019 08:33
by ziotempa
No, I disabled the other one (there's only one) and closed automagic from the multitasking before trying :|

Re: Issue with android 9 call Java method

Posted: 22 Apr 2019 10:34
by anuraag
I believe stream_uri is getting lost in Android 9 faster than 8. Send/Share Intent Received should provide temp/real file path by default. Hope Martin will add it one day. We may need to create a feature request topic for it.

If you want to buy and use a plugin then AutoShare gives temp/real path variable by default.

Re: Issue with android 9 call Java method

Posted: 22 Apr 2019 11:06
by Desmanto
@anuraag : Same error here on Pie 9.0. MiXplorer share is fine though, but it is copied to temporary directory first.

I found out that I can use Query content provider to directly get the real path from MiXplorer. But the same flow only get the file name from Whatsapp. I can match with the extra received and test the file existence in whatsapp folder. But the script won't work universally. Tested from CamScanner, it provided a full path using file:/// format, so not need extra query content. It is very complicated to create each handler for each app method.

But so far I only share mostly from these 3 apps, so maybe I will modify my flow to suit to those. Prefer not to use additional app if the workaround exists.

Re: Issue with android 9 call Java method

Posted: 22 Apr 2019 11:35
by anuraag
Desmanto wrote:
22 Apr 2019 11:06
@anuraag : Same error here on Pie 9.0. MiXplorer share is fine though, but it is copied to temporary directory first.
I have provided temp flow to check that input stream error. So Mixplorer gives correct path with my previous script.
Desmanto wrote:
22 Apr 2019 11:06
But the script won't work universally. Tested from CamScanner, it provided a full path using file:/// format, so not need extra query content. It is very complicated to create each handler for each app method.
There aren't many formats (only 3 as per documentation - android.resource, content and file). I haven't came across file:/// format. Most apps uses content:/// format. And these 2 are used for files. So it is easy to add a line for file:/// format in script.
Desmanto wrote:
22 Apr 2019 11:06
Prefer not to use additional app if the workaround exists.
Same here. Not yet purchased any plugins.

Re: Issue with android 9 call Java method

Posted: 22 Apr 2019 13:23
by ziotempa
Ok then.... I'll wait for... for... for what?
I understood correctly that there is a different format for each app? As for me I use only whatsapp and quickpic (which works with the first version of the script)

Re: Issue with android 9 call Java method

Posted: 22 Apr 2019 15:41
by Desmanto
@anuraag : I will try to create the handlers for those 3 app first. Let's see how it works out. Will compare to your java call method and see the difference.

@ziotempa : which quickpic version do you use? the old one from xda? I will try to check the way it share the file too.

Re: Issue with android 9 call Java method

Posted: 22 Apr 2019 15:54
by ziotempa
Quickpic 3.5, not the xda version

Re: Issue with android 9 call Java method

Posted: 29 Apr 2019 22:00
by anuraag
Martin has added a workaround in latest EAP which is working.

Here is a modified flow to support for uri starting with "file://"

Re: Issue with android 9 call Java method

Posted: 30 Apr 2019 01:00
by ziotempa
Sorry, what EAP stands for? Because I imported this flow and it still doesn't work when I share the image from whatsapp