✨ [feat] iCloud 동기화 기능 추가 (#65) #126
Conversation
- NSPersistentCloudKitContainer에 CloudKit 컨테이너 옵션 설정 - 원격 변경사항 알림 처리 추가 (NSPersistentStoreRemoteChange) - 자동 병합 정책 설정 (automaticallyMergesChangesFromParent) - 히스토리 추적 활성화 (NSPersistentHistoryTrackingKey) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
📝 WalkthroughWalkthroughImplements a full Core Data + CloudKit stack in Changes
Sequence Diagram(s)sequenceDiagram
%% Styling hints: new/changed interactions highlighted with notes
participant App as App Init
participant CDS as CoreDataStorage
participant PSC as NSPersistentContainer
participant PS as NSPersistentStore (CloudKit)
participant CloudKit as CloudKit
participant Main as Main Thread
App->>CDS: shared init / setupPersistentContainer()
activate CDS
CDS->>PSC: create container & loadPersistentStores()
PSC->>PS: configure NSPersistentStoreDescription (CloudKit options, history, remote-change)
PS->>CloudKit: CloudKit sync (background)
deactivate CDS
Note over CloudKit,PS: Remote changes synced to local store
PS->>CDS: NSPersistentStoreRemoteChange notification
activate CDS
CDS->>CDS: handleRemoteChange -> enqueue history processing
CDS->>PS: fetch persistentHistory since last token
PS-->>CDS: history transactions
CDS->>CDS: apply merges, advance token, purge old history
CDS->>Main: post Notification.Name.didReceiveRemoteChanges (main)
deactivate CDS
Estimated code review effort🎯 4 (Complex) | ⏱️ ~45 minutes Suggested labels
Poem
Pre-merge checks and finishing touches❌ Failed checks (2 warnings)
✅ Passed checks (3 passed)
✨ Finishing touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
Animal-Crossing-Wiki/Projects/App/Sources/CoreDataStorage/CoreDataStorage.swift (1)
101-104: Potential duplicateUserCollectionEntityafter multi-device sync.With iCloud sync, if two devices both call
getUserCollectionbefore their first sync, each will create a separateUserCollectionEntity. After sync, both entities will exist, and.firstreturns an arbitrary one (no sort descriptor).Consider:
- Adding a unique constraint or identifier to
UserCollectionEntityto prevent duplicates.- Adding deduplication logic that merges or removes duplicates when multiple entities are detected.
- Using a stable sort descriptor so behavior is at least deterministic.
🔎 Verification script to check UserCollectionEntity model
#!/bin/bash # Check if UserCollectionEntity has any unique constraints defined in the Core Data model fd -e xcdatamodeld -x find {} -name "*.xcdatamodel" -exec cat {}/contents \; 2>/dev/null | grep -A 20 "UserCollectionEntity"
🧹 Nitpick comments (1)
Animal-Crossing-Wiki/Projects/App/Sources/CoreDataStorage/CoreDataStorage.swift (1)
79-84: Consider debouncing rapid remote change notifications.When multiple remote changes arrive in quick succession (e.g., initial sync of many items), this will post multiple
didReceiveRemoteChangesnotifications, potentially causing redundant UI refreshes.This is a minor optimization concern—the current implementation is functionally correct. If performance issues arise, consider coalescing notifications with a small delay.
📜 Review details
Configuration used: defaults
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
Animal-Crossing-Wiki/Projects/App/Sources/CoreDataStorage/CoreDataStorage.swift
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: Check Build
🔇 Additional comments (2)
Animal-Crossing-Wiki/Projects/App/Sources/CoreDataStorage/CoreDataStorage.swift (2)
35-66: LGTM! CloudKit container setup looks correct.The configuration follows Apple's recommended pattern for
NSPersistentCloudKitContainer:
- History tracking and remote change notifications are properly enabled before loading stores.
automaticallyMergesChangesFromParentandNSMergeByPropertyObjectTrumpMergePolicyare set after store loading, which is the correct sequence.One consideration:
NSMergeByPropertyObjectTrumpMergePolicymeans in-memory changes always win over remote changes during conflicts. This aligns with the test plan ("동시 수정 시 병합 정책"), but be aware that whichever device syncs last will have its changes persisted when the same property is modified on multiple devices.
89-91: LGTM!Clean and idiomatic pattern for defining custom notification names.
- CoreDataStorage CloudKit 통합 개선 - 히스토리 추적 및 중복 병합 로직 강화 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
- performBackgroundTask에서 guard를 if 문으로 변경 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
There was a problem hiding this comment.
Actionable comments posted: 3
🧹 Nitpick comments (4)
Animal-Crossing-Wiki/Projects/App/Sources/Extension/String+extension.swift (1)
27-38: Consider usingcontainsfor cleaner and more efficient membership check.The
filter+isEmptypattern allocates an intermediate array unnecessarily. A more idiomatic Swift approach would usecontains:🔎 Suggested refactor
var isChosung: Bool { - var isChosung = false - for char in self { - if !hangul.filter({ $0.contains(char)}).isEmpty { - isChosung = true - } else { - isChosung = false - break - } - } - return isChosung + guard !isEmpty else { return false } + return allSatisfy { hangul.contains(String($0)) } }This leverages
allSatisfywhich short-circuits on the first non-matching character and avoids the intermediate array allocation fromfilter.Animal-Crossing-Wiki/Projects/App/Sources/Presentation/Catalog/Views/ItemSeasonView.swift (1)
75-81: Good refactoring to useisoperator for type checking.The change from an optional cast check to the
isoperator is more idiomatic Swift and slightly more efficient. The logic correctly prevents duplicateCalendarViewinstances in the stack.One minor observation: this refactor appears unrelated to the iCloud sync feature that is the main focus of the PR. Consider grouping unrelated cleanups in separate commits or PRs for easier review tracking.
Animal-Crossing-Wiki/Projects/App/Sources/CoreDataStorage/CoreDataStorage.swift (2)
385-401: Consider returning failure feedback to caller.When the store isn't loaded and timeout occurs, the method silently returns without executing the block. The caller has no way to know whether their task was executed or skipped.
Consider adding a completion handler or throwing an error to provide feedback:
🔎 Proposed signature with error feedback
Option 1: Throw error
-func performBackgroundTask(_ block: @escaping (NSManagedObjectContext) -> Void) { +func performBackgroundTask(_ block: @escaping (NSManagedObjectContext) -> Void) throws { if !isStoreLoaded { logger.warning("performBackgroundTask called before store is loaded. Waiting...") guard waitForStoreLoad(timeout: 5.0) else { logger.error("Store still not loaded after waiting. Skipping background task.") - return + throw CoreDataStorageError.storeNotReady } } // ... }Option 2: Completion handler
-func performBackgroundTask(_ block: @escaping (NSManagedObjectContext) -> Void) { +func performBackgroundTask(_ block: @escaping (NSManagedObjectContext) -> Void, completion: ((Bool) -> Void)? = nil) { if !isStoreLoaded { logger.warning("performBackgroundTask called before store is loaded. Waiting...") guard waitForStoreLoad(timeout: 5.0) else { logger.error("Store still not loaded after waiting. Skipping background task.") + completion?(false) return } } persistentContainer.performBackgroundTask { context in context.mergePolicy = NSMergeByPropertyObjectTrumpMergePolicy context.transactionAuthor = Bundle.main.bundleIdentifier ?? "ACNHWiki" block(context) + completion?(true) } }
42-54: Runtime iCloud state changes are not actively monitored.
isCloudKitEnabledis a computed property that checksFileManager.default.ubiquityIdentityToken != nil, so it reflects the current state on each access. However, CloudKit configuration is only checked during initial persistent store setup (line 119) and error recovery (line 142). If a user signs out of iCloud while the app is running, these checks won't trigger again unless an error occurs or the app restarts.To handle account changes gracefully, consider observing
NSUbiquityIdentityDidChangenotifications and updating the data store configuration accordingly.
📜 Review details
Configuration used: defaults
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (6)
Animal-Crossing-Wiki/Projects/App/Sources/CoreDataStorage/CoreDataStorage.swiftAnimal-Crossing-Wiki/Projects/App/Sources/Extension/String+extension.swiftAnimal-Crossing-Wiki/Projects/App/Sources/Presentation/Catalog/ViewControllers/ItemsViewController.swiftAnimal-Crossing-Wiki/Projects/App/Sources/Presentation/Catalog/ViewModels/ItemsReactor.swiftAnimal-Crossing-Wiki/Projects/App/Sources/Presentation/Catalog/Views/CategoryRow.swiftAnimal-Crossing-Wiki/Projects/App/Sources/Presentation/Catalog/Views/ItemSeasonView.swift
💤 Files with no reviewable changes (1)
- Animal-Crossing-Wiki/Projects/App/Sources/Presentation/Catalog/Views/CategoryRow.swift
🧰 Additional context used
🧬 Code graph analysis (2)
Animal-Crossing-Wiki/Projects/App/Sources/Presentation/Catalog/ViewModels/ItemsReactor.swift (2)
Animal-Crossing-Wiki/Projects/App/Sources/Utility/Items.swift (1)
updateItem(401-411)Animal-Crossing-Wiki/Projects/App/Sources/Presentation/Dashboard/ViewModels/ProgressReactor.swift (1)
mutate(33-44)
Animal-Crossing-Wiki/Projects/App/Sources/Presentation/Catalog/Views/ItemSeasonView.swift (2)
Animal-Crossing-Wiki/Projects/App/Sources/Presentation/Catalog/ViewControllers/ItemDetailViewController.swift (1)
setUpSaeson(203-213)Animal-Crossing-Wiki/Projects/App/Sources/Presentation/Catalog/Views/CalendarView.swift (2)
configure(59-86)months(10-105)
🪛 SwiftLint (0.57.0)
Animal-Crossing-Wiki/Projects/App/Sources/CoreDataStorage/CoreDataStorage.swift
[Warning] 137-137: Conditional statements should always return on the next line
(conditional_returns_on_newline)
[Warning] 174-174: Conditional statements should always return on the next line
(conditional_returns_on_newline)
[Warning] 227-227: Conditional statements should always return on the next line
(conditional_returns_on_newline)
[Warning] 253-253: Conditional statements should always return on the next line
(conditional_returns_on_newline)
[Warning] 327-327: Conditional statements should always return on the next line
(conditional_returns_on_newline)
[Warning] 343-343: Conditional statements should always return on the next line
(conditional_returns_on_newline)
[Warning] 356-356: Conditional statements should always return on the next line
(conditional_returns_on_newline)
[Warning] 575-575: Conditional statements should always return on the next line
(conditional_returns_on_newline)
[Warning] 589-589: Conditional statements should always return on the next line
(conditional_returns_on_newline)
[Warning] 83-83: Computed read-only properties should avoid using the get keyword
(implicit_getter)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: Check Build
🔇 Additional comments (15)
Animal-Crossing-Wiki/Projects/App/Sources/Presentation/Catalog/ViewModels/ItemsReactor.swift (1)
303-303: LGTM!Whitespace normalization in the function signature improves code style consistency.
Animal-Crossing-Wiki/Projects/App/Sources/Presentation/Catalog/ViewControllers/ItemsViewController.swift (1)
397-430: LGTM! Good use of Swift conventions.Both closures correctly use
_to indicate theactionparameter is intentionally unused, improving code clarity.Animal-Crossing-Wiki/Projects/App/Sources/CoreDataStorage/CoreDataStorage.swift (13)
8-38: LGTM! Error handling is comprehensive.The new error cases (
initializationFailed,persistentStoreDescriptionNotFound,storeNotReady) appropriately cover CloudKit initialization and store loading scenarios.
66-104: LGTM! Thread safety implementation is well-designed.The use of serial queues (
stateQueue,historyProcessingQueue) and computed properties for thread-safe state access is appropriate. The semaphore-based signaling pattern for store load completion is correctly initialized.
119-164: LGTM! CloudKit integration and merge policies are well-configured.The conditional CloudKit setup based on iCloud availability, remote change notifications, history tracking, and merge policy (
NSMergeByPropertyObjectTrumpMergePolicy) are all correctly implemented for conflict resolution in a multi-device sync environment.
192-237: LGTM! Fallback logic is well-implemented.The local-only fallback correctly removes/destroys the existing store before retrying without CloudKit options. Error logging at each step provides good observability.
241-261: LGTM! Remote change notification handling is thread-safe.Serializing history processing via
historyProcessingQueueprevents concurrent modifications. The earlyisStoreLoadedcheck and background context with merge policy are appropriate.
265-316: LGTM! Persistent history processing is correctly implemented.Token management is thread-safe, changed entity tracking enables granular UI updates, and posting notifications on the main queue is appropriate. Error handling gracefully logs failures without disrupting the app.
318-338: LGTM! History purging is appropriately throttled.The 24-hour check prevents excessive purging, and 7-day retention balances storage with conflict resolution needs.
342-367: LGTM! Token persistence uses secure coding correctly.Using
NSKeyedArchiverwithrequiringSecureCoding: trueis appropriate forNSPersistentHistoryToken.
372-376: LGTM! Public notification API is well-documented.Clear documentation of the
userInfostructure helps consumers handle remote changes correctly.
403-441: LGTM! User collection fetch APIs are well-designed.The separation between
getUserCollection(fetch-or-create) andfetchExistingUserCollection(fetch-only) provides flexibility. ThefetchLimit = 1optimization and clear documentation about duplicate entities are excellent.
449-497: LGTM! Merge logic handles iCloud duplicates comprehensively.The strategy of selecting the collection with the most relationships and merging others into it is sound. Duplicate relationship filtering prevents data loss during the merge.
500-564: LGTM! Relationship merging is idempotent and comprehensive.Using identifier Sets to prevent duplicates and reassigning via back-references follows Core Data best practices. All relationship types are covered.
571-592: LGTM! Context save methods provide appropriate error handling options.Offering both throwing and non-throwing variants gives callers flexibility based on their error handling needs. The
hasChangescheck prevents unnecessary I/O.
| guard let description = container.persistentStoreDescriptions.first else { | ||
| // description이 없는 경우는 심각한 설정 오류이므로 로그 후 빈 컨테이너 반환 | ||
| // 이후 isStoreLoaded가 false로 유지되어 안전하게 처리됨 | ||
| logger.critical("Failed to retrieve a persistent store description. Core Data operations will fail.") | ||
| return container | ||
| } |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# Search for all accesses to persistentContainer to understand usage patterns
rg "persistentContainer" --type swift -B 2 -A 2Repository: leeari95/ACNH-wiki
Length of output: 5521
🏁 Script executed:
# Search for isStoreLoaded checks to see if they gate access to persistentContainer
rg "isStoreLoaded" --type swift -B 2 -A 2Repository: leeari95/ACNH-wiki
Length of output: 7172
🏁 Script executed:
# Look at the full persistentContainer lazy var implementation to understand its initialization
fd "CoreDataStorage.swift" --type f -x head -150 {} | tail -60Repository: leeari95/ACNH-wiki
Length of output: 2725
Replace the guard block with fatalError to properly signal unrecoverable configuration failure.
Returning an empty container when persistentStoreDescriptions.first is nil creates a safety gap. Storage classes access persistentContainer.viewContext directly without checking isStoreLoaded, so they will attempt operations on an uninitialized container if this guard fails. Since a missing store description is a fatal configuration error that cannot be recovered gracefully, use fatalError instead of returning a useless container.
🤖 Prompt for AI Agents
In
Animal-Crossing-Wiki/Projects/App/Sources/CoreDataStorage/CoreDataStorage.swift
around lines 111–116, the guard that returns an empty container when
container.persistentStoreDescriptions.first is nil should be replaced with a
fatalError to signal an unrecoverable configuration failure; change the guard to
call fatalError with a clear message (including context that
persistentStoreDescriptions.first was nil and Core Data cannot be initialized)
so execution halts instead of returning a partially uninitialized container.
| /// 스토어 로드가 완료될 때까지 대기합니다. | ||
| /// - Parameter timeout: 최대 대기 시간 (초) | ||
| /// - Returns: 타임아웃 발생 시 false | ||
| @discardableResult | ||
| func waitForStoreLoad(timeout: TimeInterval = 10.0) -> Bool { | ||
| // 이미 로드되었으면 즉시 반환 | ||
| if isStoreLoaded { return true } | ||
|
|
||
| // persistentContainer에 접근하여 lazy 초기화 트리거 | ||
| _ = persistentContainer | ||
|
|
||
| // 로드 완료 대기 | ||
| let result = storeLoadedSemaphore.wait(timeout: .now() + timeout) | ||
| if result == .timedOut { | ||
| logger.error("Timed out waiting for store to load.") | ||
| return false | ||
| } | ||
| // 다음 대기자를 위해 다시 signal (semaphore를 바이너리 세마포어처럼 사용) | ||
| storeLoadedSemaphore.signal() | ||
| return isStoreLoaded | ||
| } |
There was a problem hiding this comment.
Fix semaphore reuse pattern - potential race condition.
The pattern of re-signaling the semaphore (line 186) to allow "the next waiter" is problematic. If multiple threads call waitForStoreLoad concurrently:
- Thread A waits, store loads, A receives signal, A re-signals (value = 1)
- Thread B waits, immediately passes (value = 0), B re-signals (value = 1)
- Semaphore value keeps increasing with each waiter
This defeats the purpose of the semaphore and could cause threads to pass before the store is actually loaded.
🔎 Recommended fix using a condition or simpler pattern
Option 1: Remove re-signaling and use single-use semaphore
@discardableResult
func waitForStoreLoad(timeout: TimeInterval = 10.0) -> Bool {
if isStoreLoaded { return true }
_ = persistentContainer
let result = storeLoadedSemaphore.wait(timeout: .now() + timeout)
if result == .timedOut {
logger.error("Timed out waiting for store to load.")
return false
}
- // 다음 대기자를 위해 다시 signal (semaphore를 바이너리 세마포어처럼 사용)
- storeLoadedSemaphore.signal()
return isStoreLoaded
}Option 2: Use DispatchGroup instead
Replace storeLoadedSemaphore with:
-private let storeLoadedSemaphore = DispatchSemaphore(value: 0)
+private let storeLoadGroup = DispatchGroup()In init():
private init() {
+ storeLoadGroup.enter()
loadHistoryToken()
}In loadPersistentStores callback:
logger.info("Persistent store loaded successfully...")
self.setStoreLoaded(true)
- self.storeLoadedSemaphore.signal()
+ self.storeLoadGroup.leave()In waitForStoreLoad:
func waitForStoreLoad(timeout: TimeInterval = 10.0) -> Bool {
if isStoreLoaded { return true }
_ = persistentContainer
- let result = storeLoadedSemaphore.wait(timeout: .now() + timeout)
- if result == .timedOut {
+ let result = storeLoadGroup.wait(timeout: .now() + timeout)
+ if result == .timedOut {
logger.error("Timed out waiting for store to load.")
return false
}
- storeLoadedSemaphore.signal()
return isStoreLoaded
}📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| /// 스토어 로드가 완료될 때까지 대기합니다. | |
| /// - Parameter timeout: 최대 대기 시간 (초) | |
| /// - Returns: 타임아웃 발생 시 false | |
| @discardableResult | |
| func waitForStoreLoad(timeout: TimeInterval = 10.0) -> Bool { | |
| // 이미 로드되었으면 즉시 반환 | |
| if isStoreLoaded { return true } | |
| // persistentContainer에 접근하여 lazy 초기화 트리거 | |
| _ = persistentContainer | |
| // 로드 완료 대기 | |
| let result = storeLoadedSemaphore.wait(timeout: .now() + timeout) | |
| if result == .timedOut { | |
| logger.error("Timed out waiting for store to load.") | |
| return false | |
| } | |
| // 다음 대기자를 위해 다시 signal (semaphore를 바이너리 세마포어처럼 사용) | |
| storeLoadedSemaphore.signal() | |
| return isStoreLoaded | |
| } | |
| /// 스토어 로드가 완료될 때까지 대기합니다. | |
| /// - Parameter timeout: 최대 대기 시간 (초) | |
| /// - Returns: 타임아웃 발생 시 false | |
| @discardableResult | |
| func waitForStoreLoad(timeout: TimeInterval = 10.0) -> Bool { | |
| // 이미 로드되었으면 즉시 반환 | |
| if isStoreLoaded { return true } | |
| // persistentContainer에 접근하여 lazy 초기화 트리거 | |
| _ = persistentContainer | |
| // 로드 완료 대기 | |
| let result = storeLoadedSemaphore.wait(timeout: .now() + timeout) | |
| if result == .timedOut { | |
| logger.error("Timed out waiting for store to load.") | |
| return false | |
| } | |
| return isStoreLoaded | |
| } |
🧰 Tools
🪛 SwiftLint (0.57.0)
[Warning] 174-174: Conditional statements should always return on the next line
(conditional_returns_on_newline)
🤖 Prompt for AI Agents
In
Animal-Crossing-Wiki/Projects/App/Sources/CoreDataStorage/CoreDataStorage.swift
around lines 168–188, the current pattern re-signals storeLoadedSemaphore after
a waiter returns which allows the semaphore value to grow and creates a race;
replace this with a single-use notification strategy: remove the
storeLoadedSemaphore.signal() call from waitForStoreLoad, ensure the semaphore
is initialized to 0 and only signaled once from the persistent store load
completion path when the store actually finishes loading, or alternatively
replace storeLoadedSemaphore with a DispatchGroup (call group.enter() before
load, group.leave() in the load completion, and group.wait(timeout:) in
waitForStoreLoad); update waitForStoreLoad to simply wait and return
isStoreLoaded without re-signaling.
| if mainCollection.islandReputation == 0 { | ||
| mainCollection.islandReputation = duplicateCollection.islandReputation | ||
| } |
There was a problem hiding this comment.
Check if islandReputation == 0 is a valid value.
The code treats islandReputation == 0 as "empty" and overwrites it with the duplicate's value. If 0 is a valid reputation value (e.g., starting reputation), this could incorrectly overwrite intentional data.
Consider whether this check should be removed or adjusted:
🔎 Potential fix
If 0 is a valid value, remove this merge logic:
- if mainCollection.islandReputation == 0 {
- mainCollection.islandReputation = duplicateCollection.islandReputation
- }Or if there's a "not set" sentinel value (e.g., -1), use that instead:
- if mainCollection.islandReputation == 0 {
+ if mainCollection.islandReputation == -1 {
mainCollection.islandReputation = duplicateCollection.islandReputation
}📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| if mainCollection.islandReputation == 0 { | |
| mainCollection.islandReputation = duplicateCollection.islandReputation | |
| } |
🤖 Prompt for AI Agents
In
Animal-Crossing-Wiki/Projects/App/Sources/CoreDataStorage/CoreDataStorage.swift
around lines 487-489, the merge logic treats islandReputation == 0 as "empty"
and overwrites mainCollection with duplicateCollection's value; if 0 is a valid
reputation this is incorrect. Change the check to use a true "unset" sentinel
(e.g., -1) or remove the overwrite entirely: either stop treating 0 as empty and
leave mainCollection.islandReputation unchanged, or adjust the code so it only
overwrites when islandReputation equals the agreed-upon sentinel (and ensure any
existing records use that sentinel when uninitialized).
Summary
NSPersistentCloudKitContainer에 CloudKit 컨테이너 옵션 설정NSPersistentStoreRemoteChange)automaticallyMergesChangesFromParent,NSMergeByPropertyObjectTrumpMergePolicy)NSPersistentHistoryTrackingKey)주의사항
iCloud.com.leeari95.ACNHWiki)는 프로젝트 설정에 맞게 조정 필요Test plan
Closes #65
🤖 Generated with Claude Code
Summary by CodeRabbit
New Features
Bug Fixes / Reliability
UI/Behavior
✏️ Tip: You can customize this high-level summary in your review settings.