Fix CoreData Thread Safety in retryCachedData

[sergiothinks2]

Problem

Some customers are experiencing crashes when the upload was not successful and the data was cached. The crash occurs on app relaunch when retryCachedData() is called, specifically when trying to access CoreData managed object properties on a different thread than the managed object context.

Changes

Modified retryCachedData() method to handle CoreData objects safely

• Removed direct property access of CoreData managed objects across threads
• Added conversion of managed objects to value types before processing
• Maintained existing thread safety mechanisms (semaphore, queue handling)
• Verified that test_fetchAllUploadData() is passing

Before

The original implementation accessed CoreData managed object properties (uploadData.type, uploadData.data, etc.) directly while iterating through them on a different thread than where they were fetched.

After

The new implementation:

• Uses existing fetchAllUploadData() method which properly handles CoreData context
• Immediately converts managed objects to value types using map
• Processes these thread-safe value types in the upload loop

[notion-workspace]

iOS SDK causing crash at app startup due to uploadData and managedObjectContext on different threads

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details

Scanned Files

[github-actions]

	Warnings
⚠️	No CHANGELOG entry added.
⚠️	No tests added / modified.

Generated by 🚫 Danger Swift against bb829ab

[NachoEmbrace]

Were you able to reproduce the crash?