Creating a zone on first launch

The sample app creates a custom zone when the accountChange event is triggered or if a .zoneNotFound error occurs while sending records. This naturally leads to .zoneNotFound errors on the first upload(s) until it fixes itself.

Is there a specific reason it's done this way? Would it be possible to call
`self.syncEngine.state.add(pendingDatabaseChanges: [ .saveZone(CKRecordZone(zoneName: Self.zone.zoneID.zoneName)) ])
`at app launch and have it finish before any other sync operations can occur?

Or is the approach in this sample project the recommended way and you just have to live with those error occurring once. This makes it especially hard to use the Telemetry Error feature in the CloudKit dashboard because you can never be sure if those errors are genuine.

Inizia tracciando la gestione di accountChange della sample app, il recupero di .zoneNotFound e il percorso di avvio del sync-engine. Confronta la creazione delle zone durante l'avvio con la creazione prima dei caricamenti dei record, quindi verifica il comportamento scelto rispetto agli errori del primo caricamento e alla telemetria della dashboard CloudKit.

Scritto dal modello di indicizzazione a partire dal testo della issue.