benwhiting

The Drive update is working pretty well for me, though the frequency bias that Alfred assigns to regularly accessed items is still learning because I haven't accessed these files through normal file search before.

I just wanted to say a huge thank you to you, @vitor for your work on this workflow. It was incredibly helpful to me while Google figured things out, as it allowed me to continue using Alfred for all my files, and it even helped me learn more about workflows in general so I could make small customizations. You're amazing!

@vitor

I added the new locations to the Alfred search scope, and after allowing some time to pass, my Drive items are now appearing in a regular Alfred file search. 👍

So I felt helpless to access files for a while when nothing was indexed, but now it looks like this might work pretty well for me...

My Google Drive implemented a change this morning that relocated the shared folders to "Locations" within Finder.

Apparently this broke the workflow, as I cannot rebuild the cache and my search will not open any formerly cached items now.

It looks like perhaps this new location is being indexed by macOS, because I can find items in Spotlight now. But I changed the location in my workflow settings, and rebuild cache still isn't working.

Is the Google Drive new "Locations" setup incompatible with this workflow?

Thanks for the extra help. I've disabled as much background access as I comfortably can. We'll see if that sorts things out.

23 hours ago, vitor said:

I have other workflows which use the same technique, in case you want to share the files you have in that folder.

There were only about 5 files in that folder. I deleted all but the ones for Canva and Tunnelbear.

Should I be looking somewhere else for the cause of this notification?

@vitor

Okay, thanks for your help. I guess I'll start searching online forums to try to narrow down what might be causing these notifications.

Once again, thanks so much for creating and maintaining this workaround while Google Drive gets their act together.

I actually don't see any googledrive files in that folder.

@vitor

Yes, :gdrebuildcache

I changed the auto_refresh to 0 and rebooted my machine, but I still had 3 script notifications this morning.

@vitor

I've definitely rebooted multiple times, and the notification bug is persisting.

When does the auto-cache normally run?

When I run it manually, I've been getting an alert from our corporate malware software—it doesn't like something about that script and may be interfering with the process.

@vitor Thanks so much for creating and maintaining this awesome workflow. My hotkey for this is now firmly engrained in my muscle memory, and I use it dozens of times a day.

Everything was working swimmingly for me, but with the upgrade to macOS Ventura I am now seeing repeated notifications for a background script, which seems to be related to this workflow (see attached). This especially happens any time my computer sleeps—when I wake it back up, I have several background script notifications. Have you seen that with this workflow before?

### Workflow version
2022.12

### Alfred version
4.7

### macOS version
13.0

### Architecture
i386

### Workflow environment variables
Dict {
    auto_refresh = 1
    google_drive_path = /Volumes/GoogleDrive/My Drive, /Volumes/GoogleDrive/Shared Drives/Voss Fixtures Team
    result_limit = 50
    ignore_list = 
}

### Full Disk Access
Granted

### Google drive paths
Exists: /Volumes/GoogleDrive/My Drive
6032 paths
Exists: /Volumes/GoogleDrive/Shared Drives/Voss Fixtures Team
48546 paths

### Cache dir
cache.db

### Cache file
16777220 123536149 -rw-r--r-- 1 benwhiting staff 0 10063872 "Nov  7 10:59:03 2022" "Nov  7 10:49:17 2022" "Nov  7 10:49:17 2022" "Nov  7 10:45:05 2022" 4096 20488 0 /Users/benwhiting/Library/Caches/com.runningwithcrayons.Alfred/Workflow Data/com.alfredapp.googledrive/cache.db

### Temporary cache
Does NOT exist

### Build progress
NOT running

### Launchd job
Loaded: -    0    com.alfredapp.googledrive
NOT installed