What happened?
Description
I am using the gemini-cli with 4diac files. The file extension .adp refers to "Adapter Type" definitions, which are plain XML text files. https://github.com/eclipse-4diac/4diac-ide/blob/release/data/typelibrary/events-3.0.0/typelib/ATimeOut.adp
However, the CLI seems to automatically detect .adp as an audio format (likely Active Streaming Format) and attempts to treat it as binary.
Steps to Reproduce
- Have a text-based file named
test.adp in the directory (valid XML content).
- Run
gemini and ask a question about this file.
- The process fails with an API error.
Observed Output
The API returns a 400 INVALID_ARGUMENT error.
Debug logs show the request fails because the CLI is likely streaming binary data (or declaring an audio mime-type) to an endpoint expecting text.
Workaround
Renaming the file from .adp to .xml fixes the issue immediately, and Gemini can read the file correctly.
Suggested Fix
Please update the mime-type detection to treat .adp as text/xml or allow a mechanism to override mime-type detection for specific extensions.
What did you expect to happen?
I expected the CLI to recognize the .adp file as text/XML (since it contains plain XML content) and process it normally, instead of treating it as binary audio and failing with an error.
Client information
Client Information
Run gemini to enter the interactive CLI, then run the /about command.
> /about
# paste output here
│ About Gemini CLI │
│ │
│ CLI Version 0.24.0 │
│ Git Commit 48ee9bb30 │
│ Model auto-gemini-3 │
│ Sandbox no sandbox │
│ OS win32 │
│ Auth Method OAuth │
│ User Email <mine>
Login information
Google Account
Anything else we need to know?
Context:
The .adp files are standard XML files used in Eclipse 4diac (Industrial Automation) to define "Adapter Types". They are not audio files.
Debug Info:
The API consistently returns a 400 INVALID_ARGUMENT error, indicating a mismatch between the sent content type (likely binary/audio) and the actual content needed by the model.
Error Snippet:
{
"error": {
"code": 400,
"message": "Request contains an invalid argument.",
"status": "INVALID_ARGUMENT"
}
}
What happened?
Description
I am using the
gemini-cliwith 4diac files. The file extension.adprefers to "Adapter Type" definitions, which are plain XML text files. https://github.com/eclipse-4diac/4diac-ide/blob/release/data/typelibrary/events-3.0.0/typelib/ATimeOut.adpHowever, the CLI seems to automatically detect
.adpas an audio format (likely Active Streaming Format) and attempts to treat it as binary.Steps to Reproduce
test.adpin the directory (valid XML content).geminiand ask a question about this file.Observed Output
The API returns a
400 INVALID_ARGUMENTerror.Debug logs show the request fails because the CLI is likely streaming binary data (or declaring an audio mime-type) to an endpoint expecting text.
Workaround
Renaming the file from
.adpto.xmlfixes the issue immediately, and Gemini can read the file correctly.Suggested Fix
Please update the mime-type detection to treat
.adpastext/xmlor allow a mechanism to override mime-type detection for specific extensions.What did you expect to happen?
I expected the CLI to recognize the .adp file as text/XML (since it contains plain XML content) and process it normally, instead of treating it as binary audio and failing with an error.
Client information
Client Information
Run
geminito enter the interactive CLI, then run the/aboutcommand.Login information
Google Account
Anything else we need to know?
Context:
The
.adpfiles are standard XML files used in Eclipse 4diac (Industrial Automation) to define "Adapter Types". They are not audio files.Debug Info:
The API consistently returns a
400 INVALID_ARGUMENTerror, indicating a mismatch between the sent content type (likely binary/audio) and the actual content needed by the model.Error Snippet:
{ "error": { "code": 400, "message": "Request contains an invalid argument.", "status": "INVALID_ARGUMENT" } }