[Google Workspace] "Search Google Drive Files", yield no results

[bbrandtom]

Extension

https://www.raycast.com/raycast/google-workspace

Raycast Version

1.88.4

macOS Version

15.0

Description

Search does not yield results.

Steps To Reproduce

1. In raycast
2. Open "Search Google Drive Files" extension
3. ⌘+P and select "In full text in My Drive"
4. Search anything.

Current Behaviour

no results.

Expected Behaviour

results.

[raycastbot]

Thank you for opening this issue!

🔔 @thomaslombart @mathieudutour @marcmagn1 @mepearso @jbjanot @ridemountainpig you might want to have a look.

💡 Author and Contributors commands

The author and contributors of raycast/google-workspace can trigger bot actions by commenting:

• @raycastbot close this issue Closes the issue.
• @raycastbot close as not planned Closes the issue as not planned.
• @raycastbot rename this issue to "Awesome new title" Renames the issue.
• @raycastbot reopen this issue Reopens the issue.
• @raycastbot assign me Assigns yourself to the issue.
• @raycastbot good first issue Adds the "Good first issue" label to the issue.
• @raycastbot keep this issue open Make sure the issue won't go stale and will be kept open by the bot.

[bbrandtom]

Just to update, when I let it run for enough time, I got this error -

Error:

Be: request to https://www.googleapis.com/drive/v3/files?q=name+contains+%27travel%27+and+trashed+%3D+false&fields=files%28id%2C+name%2C+mimeType%2C+webViewLink%2C+webContentLink%2C+size%2C+modifiedTime%2C+thumbnailLink%2C+starred%2C+capabilities%28canTrash%29%2C+parents%29&corpora=allDrives&supportsAllDrives=true&includeItemsFromAllDrives=true&orderBy=recency+desc failed, reason: Client network socket disconnected before secure TLS connection was established
    at ClientRequest.<anonymous> (/Users/brandtom/.config/raycast/extensions/79cbf884-c9cc-4913-8482-b28f6da5684f/search-google-drive-files.js:43:133578)
    at ClientRequest.emit (node:events:519:28)
    at ClientRequest.emit (node:domain:488:12)
    at TLSSocket.socketErrorListener (node:_http_client:500:9)
    at TLSSocket.emit (node:events:519:28)
    at TLSSocket.emit (node:domain:488:12)
    at emitErrorNT (node:internal/streams/destroy:169:8)
    at emitErrorCloseNT (node:internal/streams/destroy:128:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

[thomaslombart]

Does this happen consistently? What if you log out and log back in?

[thomaslombart]

I'm closing this issue to maintain a clean backlog. Feel free to comment it if you still have the problem.