`gws drive files download` reports success but does not create `--output` file

Open
#789 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

  • #805 by @Lubrsy706 — closed without merging

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
rust
Domain
cli

Research direction

Start by reproducing gws drive files download with the reported --params and --output values, then trace the Drive download command's output-file handling. Check why a successful done: true response and downloadUri do not result in a file being written. Done when the command creates the requested non-empty csv/test-download.csv while retaining correct success reporting.

Written by the indexing model from the issue text.

Description

gws drive files download returns done: true and a valid downloadUri, but no file is written to the path passed with --output.

Repro:

gws drive files download --params '{"fileId":"...","mimeType":"text/csv"}' --output "csv/test-download.csv"

Expected:
csv/test-download.csv exists and is non-empty.

Actual:
Command prints success JSON (done: true), but csv directory is empty.

Environment:

  • macOS 26.4.1
  • zsh
Dominant language
Rust
Stars
32.3k
Forks
2k
Avg merge
16h 3m
Merged PRs (30d)
1

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from googleworkspace/cli

All issues in googleworkspace/cli

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.