We have identified an issue with our Gemini API call , which is caused by recent Gemini 1.5 Flash update that took place on Aug 28 (after submission Google Gemini updates: Custom Gems and improved image generation with Imagen 3) - JSON schema not reading correctly.
To address this, we would like to update our code to rectify the error caused by the update. We propose including the revised code within the same drive where our original submission was made.
Could you please advise on the appropriate steps we should take to ensure that our submission will be evaluated based on this updated code? We want to ensure that the correct version is considered during the review process.
Thank you for your understanding and support. We look forward to your guidance on this matter. @Lloyd_Hightower
During preliminary verification by our team, it was confirmed before the submission date that JSON mode does not work with 1.5-flash depending on the implementation method, so we modified it to use 1.5-Pro.
(To satisfy the condition that there are no bugs in the rules)
I heard that there was an issue with a recent update, and since I’m technically curious, could you please tell me about the implementation of JSON mode in 1.5 flash?
I found a similar bug that started with a recent update too, but on Node. Here’s a snippet that reproduces it half the time: Gemini response schema bug · GitHub
It seems that when the schema includes an array type, it will go on and on in a loop until it hits the token limit. Sometimes the response will exclude the array. Removing the schema or even the array makes the bug stop.
I’ll push the update for the live demo (no point having a demo that doesn’t work). But the code in Google Drive still has the bug.