· By Maya Chen · Platform Infrastructure

Reliable 1.2 GB+ Resumable Mobile Build Uploads Without Long-Running Daemons

Designing deterministic 5 MB chunked uploads, session-persisted resume fingerprints, and cron-backed fallback assembly for unstable QA networks.

Uploading a 900 MB Unreal or Flutter release candidate over hotel Wi-Fi—or from a CI runner behind a strict reverse proxy—should never fail at 94% and force a complete restart.

Why single-request multipart uploads fail in the real world

Standard shared-hosting environments typically cap upload_max_filesize and post_max_size around 16M to 64M, and load balancers routinely terminate single HTTP POST bodies that stay open longer than 60 seconds.

Deterministic 5 MB chunking & preflight resume checks

BuildDrop solves both constraints by slicing every .ipa, zipped .app, and .apk into 5 MB (5,242,880-byte) chunks in the browser and over /api/upload/chunk:

  1. Deterministic upload fingerprint: When a developer drops a file, the uploader hashes (name, size, lastModified) in sessionStorage so refreshing or retrying reuses the same upload_id.
  2. Preflight chunk discovery: GET /upload/chunk?upload_id=… returns the exact array of zero-indexed chunks already verified on disk under storage/app/private/tmp/{uploadId}/.
  3. Zero re-transmission on retry: If chunk 28 of 40 drops due to a network blip, clicking Retry skips chunks 0..27 immediately and transmits only the remaining slices.
  4. Enforced plan caps before and after: Both client-side preflight validation and server-side stream assembly verify total bytes against Entitlements::for($user)->maxUploadBytes(), ensuring server storage stays strictly bounded.