-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Illegal input: Fields [promptTokenCount, totalTokenCount] are required for type with serial name #134
Comments
I'm experiencing the same problem. I suspect it's a server-side bug since everything was functioning normally yesterday. |
I have same. |
The problem has persisted for nearly 24 hours now. As many of us rely on these APIs for products, is there an SLA in place? Is this production ready? |
@mattttvaughn I discovered the same problem with all phones and emulators. Everything was working great earlier, but this morning I ran into this problem, and Google still could not figure it out. How disappointing |
The API just started populating that field yesterday, they are aware of the issue now and trying to get it fixed asap. |
Hey folks, thanks for your reports. We are working on getting the fix out ASAP, stay tuned! |
Also, exposes the data when available. Addresses issue #134
The new release is out https://github.com/google-gemini/generative-ai-android/releases/tag/v0.5.0 It contains the fix this issue. Additionally, we have rolled back the change in the backend that exposed the partial UsageMetadata. This means that even older versions of the SDK will start working again. Thanks for your patience! |
I was trying out the SDK and got everything looking GTG, but was unable to get past the error in the title. I then pulled down the sample project and I'm seeing the same error when running the summarization bit, only change is adding my API key to local.properties.
Idk if this is a server-side issue or not but figured I'd log an issue. I tried API keys from accounts with and without whatever Gemini pro access is called, if that's relevant.
OnePlus 8, Android 13
The text was updated successfully, but these errors were encountered: