iPhone file transfer

How it works

HEIC and Live Photos surprise desktop tools. Optimized storage sends a preview. AirDrop stays on Apple devices. A link works to anyone. Background browser uploads still suspend.

A client AirDrops 30 JPEGs to a producer laptop. Originals were requested. Optimized storage had kept originals on the phone and sent previews. They export originals through Files and upload those.

How it differs

iPhone file transfer is not iCloud sharing. A shared album is ongoing access. A transfer is a copy.

Live Photos arrive as a still plus a movie. Say if you need both.

Export explicitly.

On the ticket

• The practical close is a log line: time, actor, byte count, result.
• Without that line the transfer is a story.
• With it, the next person can see whether this door did what the ticket claimed.
• If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
• On a real ticket, write down the door, the byte count, and the clock.
• For iphone file transfer, that means naming the host or bucket, the expected size, and the time the other side must have a complete file.
• A progress bar is not that record.
• A 200 response that arrives before the complete call is not that record.
• If a retry is allowed, say how many and whether it resumes.
• If a person must approve the send, name the person.
• Partners who receive iphone file transfer files should match on hash or size before they import.
• A same-length corrupt file passes a size check and fails a hash.
• Keep the published hash off the only channel an attacker can edit, or treat it as a corruption check rather than a substitution check.
• When the path changes, new key, new region, new cap, update the profile the same day so the next run does not use a stale limit.