Publish permanently fails with "The provided source archive is corrupted" — app cannot deploy, production users affected

Google AI Studio
, , ,
1

Summary

My AI Studio app can no longer be published. Every attempt fails at the packaging/upload
stage with “The provided source archive is corrupted.” The app is live with real users,
so I am currently unable to ship any fix or update.

Identifiers
App ID 9cd3260b-625e-40ed-9092-b353.......
App URL https://jotdown.ai.studio
Cloud Run service service
Region us-west1
GCP project jotbolt
Linked Firebase project gen-lang-client-04510.....
Failing revisions service-00083-9k8, service-00084-8nj

Symptoms

  • Clicking Publish in AI Studio shows “Failed to publish app”.

  • Cloud Run logs show, roughly 40–50 seconds after each attempt:

    Ready condition status changed to False for Service service with message: The provided source archive is corrupted.

  • This has now happened on 8+ consecutive attempts between 2026-08-05 23:17 and
    2026-08-06 04:44 (HKT).

  • The currently deployed revision is healthy — the container starts normally,
    the startup probe succeeds on port 3000, and the app serves traffic. Only new
    deployments fail.

  • On the very first failure the log additionally showed:

    Project has exceeded the quota limit for the number of bytes of source code that can be deployed per minute.
    That message has not reappeared since, but “source archive is corrupted” persists.

What I have already tried

  1. Reduced source size — re-encoded PWA splash images, bringing public/ from
    1.1 MB to 380 KB. Total repository is now ~2.1 MB across 95 files.
  2. Waited for the per-minute source-bytes quota to reset, then retried with several
    minutes between attempts (not rapid retries).
  3. Restored a corrupted config file — firebase-applet-config.json in the project
    root had somehow become 0 bytes. I restored its original 426-byte content.
  4. Rebuilt the git repository — git fsck reported many objects with
    inflate: data stream error. I deleted .git, ran git init, and re-committed.
    git fsck now reports zero errors.
  5. Verified the working tree — no non-ASCII filenames, no symlinks, no zero-byte
    files, no unusually large files.
  6. Verified package.json, and confirmed npm run build succeeds locally.

None of these changed the outcome.

What this looks like from the outside

The failure is at packaging/upload, before the build ever starts — it is not a
build error, a dependency error, or a runtime error. That suggests the archive
AI Studio produces and hands to Cloud Run is itself malformed, rather than anything
being wrong with my source.

This matches several existing reports:

In the first of those, the suggested remedy was to restore the app to the last working
version from the chat window. [EDIT THIS LINE — see note below.]

What I am asking for

  1. Can someone from the AI Studio team inspect the server-side state of app
    9cd3260b-625e-40ed-9092-b353...... and confirm whether the project record is
    damaged?
  2. If it is, can it be repaired or reset without losing the current source?
  3. Is there a supported way to export the project and re-create it as a new app while
    keeping the existing Cloud Run service and custom domain mapping?

Happy to provide any additional logs or identifiers. Thank you.

1 Like