Play Console release notes parser error: whatsnew file too long failed upload fix

TL;DR

Shorten each per-language whatsnew file to within the Play limit of 500 characters per language, counting characters in the file exactly as written, then re-upload. fastlane supply reads the whatsnew text files and Play rejects the release when any locales file exceeds the limit. Trim marketing copy, keep the most important changes first, and add a length check to the release script so the next notes fail locally instead of at upload.

whatsnew file too long - Play Console release notes parser error

Use this when

• A Play upload fails with a release notes or whatsnew length error.
• Release notes were written once for all stores, and App Store allows far longer notes.
• A locale file with translations grew past the limit while the default language stayed under.

Not for this skill when

• The file is missing for a language rather than too long. Missing files produce a different supply warning.
• Notes contain disallowed content rather than excessive length. Policy rejections name the content issue.

Steps

1. Measure every whatsnew file in the metadata folder tree, one per language, with a character count, not a word count. Verify: each files length is listed and the over-limit files are identified
2. Trim each over-limit file to comfortably under 500 characters, front-loading the changes users care about. Verify: all files measure under the limit with margin
3. Check for hidden length: trailing whitespace, multi-byte characters pasted from rich text, and duplicated paragraphs. Verify: the trimmed files are plain text with no duplication
4. Add a pre-upload check in the release script that fails when any whatsnew file exceeds the limit. Verify: the script blocks a deliberately over-long test file
5. Re-run supply for the release. Verify: Play accepts the release notes and the release saves
6. Store a short template in the repo reminding writers of the per-language limit. Verify: the template exists where the notes are authored
7. Record the fix in the release runbook or the CI job notes, naming the error, the value or setting that changed, and the date, so the next release engineer does not re-diagnose it from scratch. Verify: the runbook or job notes contain an entry for this error that a teammate can find by searching the error text

Why it happens

Play enforces a strict 500 character limit per language for release notes, much shorter than App Stores allowance, and supply uploads notes as part of the release metadata. Teams draft notes once, reuse them across stores, and discover the limit at upload time, often in a translated locale nobody re-measured after editing.

In practice this failure is rarely a one-off. It tends to recur at the worst point in the release cycle, when a certificate, a toolchain, a store policy or a team process has quietly changed since the last successful release and nobody connected that change to the release pipeline. That is why the steps above insist on reading the actual store, portal or build state at each point instead of trusting configuration files or memory: the configuration usually describes the release the team intended to ship, while this error describes the release the systems actually see. Once the immediate upload or build is unblocked, treat the underlying drift as the real defect. Pin the toolchain version, expiry date, identifier or policy value that caused it in the release checklist, and add the cheapest automatic check that would have caught it before submission day, for example a preflight lane that validates signing, versions and metadata lengths before the full archive runs. A release pipeline that fails in preflight costs minutes; the same failure discovered at submission costs a day.

Variants and edge cases

whatsnew file too long fastlane supply fix

Supply phrasing; measure every locale file. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

Play Console release notes 500 character limit error

Limit phrasing for Console-side uploads. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

Edge case: per-language surprises

A concise English note can become over-limit in German or Finnish. Measure after translation, not before. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstBaol2KH1B9-NPD6fOZQMA