"You cannot add (Google Drive name) to the root of the Shared drives"

Bugs and issues Windows
#1

“You cannot add Google Drive name to the root of the Shared drives, as this is not allowed by Google Drive. To remove this error, move (Google Drive name) out of the root location”

I couldn’t upload files (no download) to the shared drive until now, and when I did, I tried uploading a folder with two sub-directories in it. However, it not only didn’t upload the main folder, but it only (tried and failed) uploaded the sub-directories, and then this error was thrown. Now that shared drive doesn’t show again.

This is odd because a drive shared with me by a friend I can upload (1-way-sync) to it. Is it because I’m the owner of this shared drive?

#2

Hi! This means that you cannot add a file/folder to the root of a Shared Drive folder from local to cloud; it needs to be uploaded within an existing Shared Drive folder.

I would suggest creating a new folder via Shared Drive web first, then you can upload these local folders to that directory. Let me know if the issue persists.

#3

I’m not sure if this affecting it, however, it keeps telling me “the base folder located at {location} is missing. Please locate the base folder to continue syncing.” I’ve changed the base folder, but it doesn’t seem to be changing it completely and it is stuck at that location.

Edit: Well, after re-creating the folders for Insync to recognize, I had to unsync it for it to stop throwing errors and that, unfortunately, caused Insync to delete everything from my Google Drive.

#5

Hi @Firon,

My apologies for the trouble you experienced. Recreating the location with an empty folder will indeed lead to a cloud deletion since Insync registers that empty folder as the user removing all the contents from the local folder. From what I’m understanding however, you recreated the folders the way they were, contents and all?

It’s interesting you mentioned that unsyncing led to a deletion. Did you mean that it removed your files from the local Google Drive (which is the expected outcome) or were the files deleted from the cloud as well?

Moving forward, if you experience a base folder is missing error, it’s best to remove the account and re-add it afterwards.

#6

To sum up and highlight the answer to your questions:

From what I’m understanding however, you recreated the folders the way they were, contents and all?

I only created the main folder and not sub-directories.

Did you mean that it removed your files from the local Google Drive (which is the expected outcome) or were the files deleted from the cloud as well?

It deleted it locally and in the cloud.

I only created the main folder and not sub-directories. However, for that specific folder, I wanted only one-way syncing (Local to Cloud) I didn’t want to download from the cloud. That same folder is the one mentioned in this original post. I’m not sure why it would delete the files from the cloud if it’s only uploading to the cloud and not downloading.

Also, I only had a certain folder/files in there, which also confuses me on why it would delete other files it has no associations with.

Honestly, the program itself looks wonderful and can be great, however, issues like this (big and small), are making me want to switch back to a previous program I was using. At least until a lot of these bugs are ironed out. I hope these issues can be dealt with before any new features. Just my two cents.

Thank you for that suggestion, I will keep that in mind. However as I stated previously, these are poor solutions and should not have to be a problem in the first place to be dealt with.

Edit: After logging out and back in, I still get the error that the base folder is missing.

Edit 2: When trying to one-way sync a folder/zip to the cloud, it just makes the shared drive disappear. However, the other shared drive I have does not disappear, but it does not allow me to upload It to that one either.

Edit 3: Trying to two-way sync a folder I created on Google Drive (2-way sync) threw some type of error and outputted the error below to the log:

C:\Users\Firon\AppData\Roaming\Insync\App\ideskui\appui.py:599: RuntimeWarning: coroutine ‘APIFunction.call’ was never awaited
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
Python WNDPROC handler failed
Traceback (most recent call last):
File “ideskwin\htmlui_impl.py”, line 357, in __OnClose
File “ideskui\htmlui.py”, line 76, in hide
File “ideskwin\htmlui_impl.py”, line 54, in hide
File “ideskui\appui.py”, line 599, in on_hide
File “ideskasync\coreloop.py”, line 131, in wrapper
File “ideskasync\coreloop.py”, line 45, in run
File “asyncio\tasks.py”, line 813, in run_coroutine_threadsafe
AttributeError: ‘NoneType’ object has no attribute ‘call_soon_threadsafe’

I’ve tried reinstalling.

#7

Hello @Firon! Do you mind sending the following to support@insynchq.com with the link to this post:

  • logs.db
  • out.txt
  • “data” folder
  • “live” folder
  • file path of the missing base folder (screenshot will do)
  • name of local folder you tried to 1-way sync and which cloud folder you wanted to sync it to
  • name of folder you tried to 2-way sync that threw the error

The first 4 items above should be in %AppData%\Insync on your machine. Thank you!

#8

I got the same issue as the second part:

Error: “The base folder located at {location} is missing. Please locate the base folder to continue syncing."

Then there are red crosses in front of some of my folders. I could identify that all concerned folders are shared from my first Google account, and have been added to the root of my second account’s drive as true folders, at the time where Google allowed us to do that (it was fully supported, then only available via Ctrl+Z, then unsupported and only symlinks are now allowed).

My hypothesis is that after Google’s change, insync doesn’t support detecting old-style true folder sharing and will stop updating such folders, only permitting symlinks. Note that unlike the OP, everything is located in the original root folder, not the default Shared folder.

For some reason, the error only shows on Windows though. Maybe because I haven’t been there for a while and it has trouble identifying every folder? (that said said folders have been there for a while too, my Windows session should know at least the oldest ones)

On Linux, insync keeps syncing things as normal.

It seems that changes in these folders are ignored from both sides, the folder sync has completely stopped. I may have to completely switch to the new Shared folders system. Problem is, all these folders already added are not visible in Shared with me in addition, I’d have to remove them from root sharing first; and if I do this, back on Linux, I will have all my existing and working folders removed, and I’ll have to resync them locally to some custom shared folder location…

#9

Hi @huulong!

Thanks so much for reaching out to us about this, and my apologies for the trouble!

I will bring this up with our engineers and highlight the specific case (that it was set up this way before Google implemented the changes and that Insync is unable to recognize that).

Am I also understanding that neither cloud nor local changes (both directions) are being synced after this issue popped up?

#10