Content Copy source question for Automate app access

354 views
Skip to first unread message

johnl...@gmail.com

unread,
Sep 2, 2017, 11:18:48 AM9/2/17
to Automate
I'm trying to backup an Automate app using the Content Copy process block. I'm using the source "content://com.llamalabs.Automate.provider/automate-app" where 'automate-app' is the name of the desired app.

Unfortunately, I get a "File not found" error when the block runs,

Thanks in advance for any insight you may provide.

Henrik "The Developer" Lindqvist

unread,
Sep 3, 2017, 10:43:25 AM9/3/17
to Automate, johnl...@gmail.com
An Automate app? Do you mean an Automate flow?
If so the URI to it is:
content://com.llamalab.automate.provider/flows/<id of flow>/data

johnl...@gmail.com

unread,
Sep 3, 2017, 5:00:53 PM9/3/17
to Automate
I've made the suggested changes, and the Content Copy flow block still fails. Here is the log:

2017-09-03 16:46:55.953 INFO 131@2: Content copy
2017-09-03 16:46:56.013 FAIL 131@2: java.io.FileNotFoundException: No files supported by provider at content://com.llamalab.automate.provider/flows/Daily Automate Backup/data

It so happens that it's attempting to extract the currently running flow, if that makes any difference.

Thanks again for any help.

Henrik "The Developer" Lindqvist

unread,
Sep 4, 2017, 3:33:16 AM9/4/17
to Automate, johnl...@gmail.com
The <id of flow> is should be a number, not the flow title.

johnl...@gmail.com

unread,
Sep 5, 2017, 8:40:11 AM9/5/17
to Automate
Where can I find the id-number of a given flow?

Henrik "The Developer" Lindqvist

unread,
Sep 5, 2017, 10:04:35 AM9/5/17
to Automate, johnl...@gmail.com
You can see the Flow URI in the Flow beginning block, the first number in it is the id.

johnl...@gmail.com

unread,
Sep 6, 2017, 8:56:58 AM9/6/17
to Automate
Each flow's Flow Beginning block has the same number, 1. This appears to be a block-id, rather than a flow-id.

Only by trial and error was I able to produce the following partial cross-reference of pre-installed flows:

1-Flashlight
2-Intruder photo
3-Home Wi-Fi
etc.

Perhaps you could sort the list of flows by flow-id, rather than flow-name.

Henrik "The Developer" Lindqvist

unread,
Sep 6, 2017, 9:35:34 AM9/6/17
to Automate, johnl...@gmail.com
The *first* number in the Flow URI is the id, e.g.:
content://com.llamalab.automate.provider/flows/9/statements/1

9 is the id, 1 is the block.

johnl...@gmail.com

unread,
Sep 6, 2017, 1:11:20 PM9/6/17
to Automate
My apologies. I did not scroll down when viewing the Flow Beginning block. Thanks for your patience.

I am now having issue with the Gdrive upload action block. I have tried specifying either a <path> or a <fully-qualified-filename> for the Google Drive Remote Path, and received two differing error messages as shown:

2017-09-06 12:49:43.920 INFO 167@3: Google Drive upload
2017-09-06 12:49:48.145 FAIL 167@3: com.llamalab.fs.gdrive.AmbiguousPathException: /phone/Automate Backups/Daily Automate Backup


2017-09-06 12:55:22.324 INFO 169@3: Google Drive upload
2017-09-06 12:55:24.734 FAIL 169@3: com.llamalab.fs.FileSystemException: /phone/Automate Backups/Daily Automate Backup/Daily Automate Backup.flo: Parent directory not found

I had to specify a <fully-qualified-filename> for the Local Path to get this far.

The directory structure is pre-existing in Google Drive.

Thanks in advance, as always.

Henrik "The Developer" Lindqvist

unread,
Sep 7, 2017, 5:18:56 AM9/7/17
to Automate
The AmbiguousPathException is raised when there's multiple directories with the same name, in the same directory. Visit the Google Drive web page and fix the issue: https://drive.google.com
Reply all
Reply to author
Forward
0 new messages