From 339899a13cab89e30a8560ed94c48181083876e6 Mon Sep 17 00:00:00 2001 From: CPS Date: Tue, 24 Mar 2026 11:57:37 +0100 Subject: [PATCH 1/4] ix(google-genai): Correct Vertex AI Veo Base64 URI generation and fallback # Bug Report / PR Proposal: Vertex AI Veo 2.0 Plugin Issues in @genkit-ai/google-genai **Environment:** - **Genkit Core / Genkit CLI:** `v1.30.1` - **Plugin (`@genkit-ai/google-genai`):** `v1.30.1` - **Node.js:** `v24.14.0` This document outlines the issues discovered and our proposed solutions/fallbacks for the official Genkit SDK. ## Issue 1: Malformed Base64 Data URI from `fromVeoOperation` **Description:** When Veo 2.0 generates an output and returns the artifact as a Raw Base64 JSON payload, the SDK maps this payload cleanly but introduces a fatal typo in the URI string prefix. Browsers strictly parse Data URIs using a semicolon delimiter (`;base64,`), but the SDK explicitly constructs it using a colon (`:base64,`). **Location:** `node_modules/@genkit-ai/google-genai/src/vertexai/converters.ts` at `fromVeoOperation()` mapping logic (specifically around `line 457`). **Expected Structure:** `data:video/mp4;base64,AAAA...` **Actual Output:** `data:video/mp4:base64,AAAA...` **Impact:** Because of this `\:` vs `\;` error, standard frontend `