Yes, I encounter the same problem too, specifically from Whatsapp. It seems the shared stream_uri is only the file, not the actual path. Sharing from Picsay pro, also have the same. But there are some difference.
If I share from Picsay, I can use Init Variable Image File on the stream_uri provided by Picsay, then it will loaded up fine. Of course I have to use another action Save Variable in Image File, save to a location and use that saved path as the attachment.
But if I share from Whatsapp, I will get permission denied. Something like this (I pass thru MiXplorer first)
Code: Select all
Permission Denial: opening provider com.whatsapp.MediaProvider from ProcessRecord{2a95c426 21221:com.mixplorer/u0a511} (pid=21221, uid=10511) that is not exported from uid 10160
Using query content provider also won't work, same permission denied. It seems the app only allow the share uri to be used once only. If passed thru automagic, it become locked down again.
The whatsapp problem has been there since I haven't started using automagic. One of the update last year, started making Es File Explorer (at that time I still use EFE) can't save the image shared from Whatsapp. But MiXplorer can handle the uri fine (I am amazed, that's one of the reason I switch). If I share from Whatsapp to "Copy To" intent from MiXplorer, we can choose the save path and paste it there. The saved image is ok and file name is correct. If I saved using Automagic - Store as file, the file saved correctly, but file name is based on whatsapp provider id. So MiXplorer somehow can query the file name from Whatsapp provider. (don't know what is the trick, gonna ask the dev later).
Because MiX works, i try to use the Copy Action from it. Using the send broadcast, I include the stream_uri as the path. At Whatsapp, it doesn't work, and give the permission denied above. But If I share using Picsay, the file saved fine using Mixplorer Copy Action intent. So I can init image, save image, copy image from Picsay share. But I can't do the same from Whatsapp share. Shared directly to MiXplorer (without passing thru automagic), it can handle both perfectly. There must be something Mixplorer do under the hood, so It can handle those kind of content.
I am still investigating on this. For mean time, you can install MiXplorer. Share to the copy action first. Choose the location to temporary save the file. And then from Mixplorer, you can share one more time and choose Automagic intent received. The stream_uri share from MiXplorer is always the file:/// format