GenerateImagesConfig AddWatermark should be present always

[sousandrei]

AddWatermark currently has omitempty, which in turns makes so that the API is called without the field set to false. Since the watermarks are enable by default, there is no way we can disable it in the config

This is specially problematic if you call it with a seed for example. Some models do not support having a watermark together with a seed.

Environment details

• Programming language: golang
• OS: macos
• Language runtime version: 1.26
• Package version: 1.49

Steps to reproduce

1. set GenerateImagesConfig.AddWatermark to false
2. observe as your config is ignored by the api call

[Sivasankaran25]

To help us understand the issue with @sousandrei , could you please share a code snippet of what you've tried so far? If you have a link to the relevant documentation, that would also be very helpful. Thanks!

[sousandrei]

Just a simple snippet

package main

import (
	"context"
	"crypto/rand"
	"encoding/binary"

	"google.golang.org/genai"
)

func main() {
	ctx := context.Background()

	client, err := genai.NewClient(ctx, &genai.ClientConfig{
		Location: "global",
	})
	if err != nil {
		panic(err)
	}

	var seed int32
	if err := binary.Read(rand.Reader, binary.BigEndian, &seed); err != nil {
		panic(err)
	}

	_, err = client.Models.GenerateImages(
		ctx,
		"imagen-4.0-ultra-generate-001",
		"generate me a pretty mountain pic",
		&genai.GenerateImagesConfig{
			NumberOfImages:    1,
			SafetyFilterLevel: genai.SafetyFilterLevelBlockOnlyHigh,
			PersonGeneration:  genai.PersonGenerationAllowAll,
			OutputMIMEType:    "image/png",
			AspectRatio:       "9:16",
			Seed:              &seed,
			AddWatermark:      false,
		},
	)
	if err != nil {
		panic(err)
	}
}

Does return the following error

panic: Error 400, Message: Image generation failed with the following error: Seed is not supported when watermark is enabled., Status: INVALID_ARGUMENT, Details: []

goroutine 1 [running]:
main.main()
	/±redacted±/main.go:42 +0x194
exit status 2

[Sivasankaran25]

Thank you for bringing this to our attention. We truly appreciate you flagging this issue, we will file a bug internally.