Automate rclone

I'm trying to use the Rclone Automate flow (with history) and I'm running into an error.
At first I thought it might be the binary, since I'm on a chromebook, so I've tried swapping that out. No joy.

I'm running the Automate flow, selecting Run Any, then trying to run rclone config just as a test.

I'm getting this output:

2019-06-30 10:18:13.425 INFO 7@97: Flow beginning
2019-06-30 10:18:13.426 INFO 7@111: Atomic load
2019-06-30 10:18:13.429 INFO 7@139: Variable set
2019-06-30 10:18:13.429 INFO 7@112: Dialog input?
2019-06-30 10:18:16.677 INFO 7@121: Variable set
2019-06-30 10:18:16.678 INFO 7@131: Array add
2019-06-30 10:18:16.678 INFO 7@132: Atomic store
2019-06-30 10:18:16.715 INFO 7@154: Go to
2019-06-30 10:18:16.716 INFO 7@200: Label
2019-06-30 10:18:16.717 INFO 7@198: Variable set
2019-06-30 10:18:16.718 INFO 7@196: Atomic store
2019-06-30 10:18:16.727 INFO 7@186: Variable set
2019-06-30 10:18:16.728 INFO 7@176: Variable set
2019-06-30 10:18:16.729 INFO 7@177: File exists?
2019-06-30 10:18:16.741 INFO 7@179: HTTP request
2019-06-30 10:18:17.612 FAIL 7@179: com.llamalab.safs.NoSuchFileException: /data/data/com.llamalab.automate/files/rclone
2019-06-30 10:18:17.615 INFO 7@179: Stopped by failure

Is this a problem with the flow? Do I need to change it from rcloneexe to rclone somewhere?

EDIT: Since I don't have root, I'm not able to verify if the file actually exists or not, or whether the download is successful. Maybe I just need to specify a different path?

I think @calisro should be able to help you with this

We're using automate's data directory so we don't need root to execute binaries. I've found that sometimes that 'files' directory doesn't exist. You can probably just create it with automate but try changing the rcloneexe to this instead (I had to this on nvidea shield devices):

/data/data/com.llamalab.automate/rclone

(removing the files directory).

I probably should just add a 'create directory' for files directort if it doesn't exist.

EDIT: I'm not familiar with a chrome-book enough to know if that path is actually okay. I know on androids that works but you may need to use a different path alltogether on chromebook.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.