ability to select which shortcuts can accept shared files, etc

[ketas]

file upload is bit problematic

only supports one file?

and i can't select which shortcuts are even shown at share

i would also prefer not to be prompted at all if there's only one file upload shortcut. tho this seems bit bad, and i wish i could have separate share action targets for them

currently using it to easily select photos and send them to my blog from my phone. blog is built on nginx so i could change other side too but ui needs improvement

i use http shortcuts daily and i like it's easy extensive scriptability for dudes like me who don't want to code app for one feature. android makes it a huge hassle to even build an app "normally". http shortcuts, along with termux, droidpad, etc removes this ass backwards limitation and allows me to simply whip together a easy request. i love it

[EarMot]

也许可以参考，用一个Shortcut多选文件里面用脚本分发到 另一个Shortcut负责上传
Perhaps we can refer to using a Shortcut to select multiple files and distribute them to another Shortcut responsible for uploading using a script
#571

[ketas]

i'm aware of multifile hack but what about being able to share into shortcut?

instead of share into app and select it from there

[Waboodoo]

only supports one file?

Sharing multiple files is already possible today. Is that not working for you? Could you describe in more detail what you tried there and what didn't work?

and i can't select which shortcuts are even shown at share

When sharing into the app, the app will show all shortcuts that can receive the shared content. You can exclude specific shortcuts by disabling the "Allow receiving files from share dialog" option on the shortcut's "Trigger & Execution Settings" screen.

i would also prefer not to be prompted at all if there's only one file upload shortcut.

This should also already be the case. If you're sharing a file into the app and there's only a single shortcut that can receive it, no prompt should be displayed and it should immediately select the one shortcut. Does this not work?

and i wish i could have separate share action targets for them

This is unfortunately not technically possible on Android. Share targets are declared statically, so there is no way for the app to offer custom or additional share targets. There is an option which may help with this, but it behaves differently on different devices and may not work at all: in your shortcut's "Trigger & Execution Settings", make sure that "Show as app shortcut on launcher" is enabled. This will make the app advertise the shortcut as a Direct Share target, which may do what you want but might also not, as the details are vendor specific. That is as close to sharing directly into shortcuts instead of the app as a whole as you can get.

[ketas]

i managed to exclude one shortcut from share and now it won't prompt

but i select multiple files and

selectedFiles.length

is still 1

a device issue here?

i do have those hacks

setVariable('file', selectedFiles[0].name.toLowerCase().replace(/[^a-z0-9_.-]/g, '-'));

showToast('[' + shortcut.name + '] ' + getVariable('file'));

and then i http put it into

https://domain/path/{{file}}

but if there is only one file, i can't even enqueue them into another shortcut. if you say it can work?

does the usage of put limit the files to 1 here?

maybe there's way that one shortcut will just keep putting

or well i can make two too, one processes filenames and one uploads the results

[Waboodoo]

Could you share an export of your affected shortcuts, so I can better understand your exact setup?

[ketas]

it exports shortcut with all sorts of data sadly

so i came up with this manual json:

      "shortcuts": [
        {
          "bodyContent": "",
          "codeOnPrepare": "setVariable(\u0027file\u0027, selectedFiles[0].name.toLowerCase().replace(/[^a-z0-9_.-]/g, \u0027-\u0027));",
          "codeOnSuccess": "showToast(\u0027[\u0027 + shortcut.name + \u0027] \u0027 + getVariable(\u0027file\u0027));",
          "fileUploadOptions": {},
          "headers": [
            {
              "key": "x-api-key",
              "value": "example"
            }
          ],
          "iconName": "bitsies_upload_000000",
          "method": "PUT",
          "name": "upload",
          "proxy": "HTTP",
          "requestBodyType": "file",
          "responseHandling": {
            "jsonArrayAsTable": false,
            "successOutput": "none",
            "uiType": "dialog"
          },
          "url": "https://example.com/directory/{{file}}"
        }
      ]

note that i know that i only handle file 0 there but i'm not sure how to handle multiple files

file count is always 1?

what's fun is, if i select multiple files, what i selected first is uploaded, rest are silently ignored

android version / device specific issue?

i also don't know how to use supposedly working chain loading of extensions

i can't seem to upload multiple files raw, e.g. without processing names?

in case of put, where's the current active file name since it needs it in url

so yeah if you say multiple ones work, do you mean i need to post them instead?

otherwise i don't know how to make it work

maybe it is indeed a feature request

the documentation is awesome but i can't find a way

[Waboodoo]

Your request body type is set to "File", which means the shortcut expects a single file and uses its contents as the raw body for the HTTP request. If you want to upload multiple files, you probably want to change the request body type to "Parameters (form-data)" and add a file parameter with the "File Data Source" set to "Open File Picker (Multi Selection)", or add multiple file parameters with "File Data Source" set to "Open File Picker". The details, such as the parameter names, depend on what your server expects. With this, you should be able to share multiple files into the shortcut.

[ketas]

hmm then i need to accept that from server side then

seems more complex

is there any way to command other shortcut to do this?

i get that this doesn't quite work well

[Waboodoo]

If your server can't accept multiple files in a single request then you could try sending multiple requests with one file each. You can achieve this by creating 2 shortcuts. The first shortcut (let's call it A) would accept multiple files (by having a file parameter with "Open File Picker (Multi Selection)"). The second shortcut (call it B) would handle a single file upload. From A you can now use the the enqueueShortcut function to enqueue B, and send a file to it using the "$files" pseudo variable. Afterwards you can abort A. So your shortcut A would just have a dummy URL (e.g. https://example.com), its method set to PUT or POST, its request body set to a file parameter with multi-select, and its "Run before Execution" block on the Scripting screen to something like this:

for (let i = 0; i < selectedFiles.length; i++) {
    enqueueShortcut("B", {
        "$files": selectedFiles[i].id,
    });
}
abort();

However, this might not work just yet, as there is a bug in the app that limits the forwarding of files from one shortcut to another (#571). A fix for it will be released soon.

[ketas]

i tried to add form data uploader to nginx but it had some issues with max size limits that i couldn't adjust

as for chaining, i think my confusion was about that if first one sends data too but with abort it won't

maybe scripting shortcuts could accept files too?

i mean i love how powerful http shortcuts overall is and how easy it is to basically write an app in it

[ketas]

i can indeed now upload multiple files

i think this need improvement, tho :)

[Waboodoo]

Glad to hear you got it working. The way files are currently handled is certainly not ideal, or all that intuitive. The feature has grown over the years. Maybe one day when I have to time, energy and the right ideas about it I'll rethink and rebuild it as a whole. But for now, I think usecases like yours are too rare and specific to be worth the effort to optimize for.

Closing this now since a solution has been found. Let me know if you still encounter problem.