Menu

Your USDZ will be rejected by an iPhone — three packaging rules Apple doesn't negotiate
📰

Your USDZ will be rejected by an iPhone — three packaging rules Apple doesn't negotiate

DEV Community: ios·cy cy·15 days ago
#cogHDXje
#devtoios#devto#dev#usdz#model
Reading 0:00
15s threshold

Last week I wrote about a GLB that shipped as a 134-meter headphone. This week is the sequel: we converted that same model to USDZ — the format Apple's AR Quick Look actually loads — and the auditor caught a different set of bombs. Same model, different container, new ways to embarrass yourself in front of a client.

Here are the three USDZ packaging rules that trip up pipelines, each with a ~15-line stdlib check. All verified against Apple's published USDZ packaging spec.

1. USDZ is a zip, but it's not your zip

The temptation: "it's a zip, let me deflate it." Apple's spec requires every entry stored uncompressed ( ZIP_STORED ). Compressed entries are the classic build-machine-works-phone-fails bug:

import zipfile

with zipfile . ZipFile ( path ) as zf : for info in zf . infolist (): if info . compress_type != zipfile . ZIP_STORED : fail ( " container/compression " , f "' { info .…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.