The frontend might have only sent the image’s ‘path’ or a ‘null reference’ to the underlying engine, without actually including the image data stream. When the engine tried to read it, it found that the payload is not inline data (there’s no actual data inside), which caused it to crash while calculating tokens and throw an INVALID_ARGUMENT (code 400): Unable to process input image error to the Google API, ultimately leading to the EOF network interruption we saw earlier.
Please fix this bug as soon as possible.(Developers who want to use images can first disable updates and roll back to version 2.1.1.)