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.

まず、sample app の accountChange 処理、.zoneNotFound のリカバリ、sync-engine の起動経路を追跡します。起動時のゾーン作成と、レコードのアップロード前の作成を比較し、そのうえで、最初のアップロード時のエラーと CloudKit ダッシュボードのテレメトリに照らして、選択した動作を検証します。

索引モデルが issue の本文から書いたものです。