Site build fails due to missing asset object in image parsing

This is almost certainly a GROQ projection issue where your query isn't including the nested asset field. The good news is this has nothing to do with Studio v2 deprecation or plan limits—it's just how the query is written.

The Problem

When you write a GROQ projection like this:

*[_type == "page"]{
  content[]{
    ...,
    file{
      altText
    }
  }
}

You're explicitly telling GROQ to only return altText from the file object. The asset reference gets excluded because you didn't ask for it in your projection.

The Solution

You need to explicitly include the asset field in your projection. Here are a few ways to fix it:

Option 1: Add the asset field explicitly

file{
  altText,
  asset
}

Option 2: Use the spread operator to get everything

file{
  ...
}

Option 3: Use the spread operator plus additional fields

file{
  ...,
  altText
}

The spread operator (...) includes all fields from the original document, so you'll get both asset and altText.

Why This Happens

GROQ projections are designed to give you precise control over what data gets returned, which optimizes response size and performance. When you specify a projection with { }, you're building a new object with only the fields you list. If you don't list asset, it won't be included—even though it exists in the Studio.

About Your Other Concerns

Studio v2: This isn't a deprecation issue. Studio v2 still works, though you should consider upgrading to Studio v3 when possible for better performance and features.

Free plan limits: Exceeding bandwidth or usage limits wouldn't cause missing fields in responses—you'd typically get rate limiting errors or service interruptions instead. The data structure itself wouldn't change.

Debugging Tip

Compare your GROQ query with what you see in the Studio's Vision plugin (or the data inspector). If fields appear in Vision but not in your build, the issue is definitely in how your query is projecting the data.