Issue with android 9 call Java method
Moderator: Martin
Re: Issue with android 9 call Java method
There is no other flow with "Send/Share Intent Received" trigger active?
Re: Issue with android 9 call Java method
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
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.
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
@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.
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.
Index of Automagic useful thread List of my other useful posts (and others')
Xiaomi Redmi Note 5 (whyred), AOSP Extended v6.7 build 20200310 Official, Android Pie 9.0, Rooted.
Xiaomi Redmi Note 5 (whyred), AOSP Extended v6.7 build 20200310 Official, Android Pie 9.0, Rooted.
Re: Issue with android 9 call Java method
I have provided temp flow to check that input stream error. So Mixplorer gives correct path with my previous script.
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.
Same here. Not yet purchased any plugins.
Re: Issue with android 9 call Java method
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)
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
@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.
@ziotempa : which quickpic version do you use? the old one from xda? I will try to check the way it share the file too.
Index of Automagic useful thread List of my other useful posts (and others')
Xiaomi Redmi Note 5 (whyred), AOSP Extended v6.7 build 20200310 Official, Android Pie 9.0, Rooted.
Xiaomi Redmi Note 5 (whyred), AOSP Extended v6.7 build 20200310 Official, Android Pie 9.0, Rooted.
Re: Issue with android 9 call Java method
Quickpic 3.5, not the xda version
Re: Issue with android 9 call Java method
Martin has added a workaround in latest EAP which is working.
Here is a modified flow to support for uri starting with "file://"
Here is a modified flow to support for uri starting with "file://"
- Attachments
-
- flow_Get_file_name_file_type_file_path_20190707_124407.xml
- Fixed getting path for external sdcards.
- (5.6 KiB) Downloaded 950 times
Last edited by anuraag on 07 Jul 2019 07:16, edited 3 times in total.
Re: Issue with android 9 call Java method
Sorry, what EAP stands for? Because I imported this flow and it still doesn't work when I share the image from whatsapp