Upload Over-The-Air patch mappings

Uploads mapping files for an Over-The-Air (OTA) patch, a remote update that ships new code without a new store build (for example CodePush for React Native, Shorebird for Flutter). It is driven by a patch_id (a UUID) and takes no app version, build number or build size.

Like PUT /builds, this API accepts metadata and returns pre-signed URLs for uploading the mapping files directly. Upload each file with a standard HTTP PUT using the returned upload_url and headers.

Usage notes:

• patch_id is required and must be a UUID. Tag your OTA patch with a UUID; it is echoed back on each mapping in the response.
• patch_version is optional. Set it to the human-facing version of the patch (max 256 characters); it is echoed back on each mapping in the response.
• The app is determined from your API key. Do not send an app identifier in the body.
• mappings is required and must contain at least one mapping. Mapping type can be proguard, dsym, elf_debug, or jsbundle (React Native).
• For React Native, upload the JS bundle and its sourcemap as two separate jsbundle mappings in the same request (same tarball and <bundle> / <bundle>.map conventions as PUT /builds).
• For mapping filename, only provide the filename, not a path.
• Each pre-signed URL expires at expires_at, and includes a headers object whose entries must all be added to the upload request, otherwise it will fail.
• File upload requests must use the PUT http method.

Response Body