Same issue here with a CKRecord created successfully. Fetching the record via query results in this same parse error. Attempting to fetch the record from iCloud fails with Record Not Found. I can fetch the record successfully in CloudKit Dashboard if I limit the fields. If I allow all I get this parse error.

• This is on both an iPhone 12 and the simulator. • This is the same code on both operating systems. • I was previously using Xcode 12, but upgraded to the the Xcode 13 RC. • I'm testing on the same model (both simulator and my personal dev device are iPhone 12s) • The code where I change first responder is pasted below. - (void)didPressNextButton {     if (currentReponderIndex == self.textFields.count - 1) {         NSNumber *tag = [self.textFields firstObject];         UITextField *field = [self.view viewWithTag:tag.integerValue];         [field becomeFirstResponder];     } else {         NSNumber *tag = [self.textFields objectAtIndex:currentReponderIndex + 1];         UITextField *field = [self.view viewWithTag:tag.integerValue];         [field becomeFirstResponder];     } }

• I don't recall seeing this issue in the two months of previous testing on iOS 14 using Xcode 12. • I'm using UICollectionViewCompositionalLayout with estimated heights that are about the same size as the rendered rows. I also have header and footer boundary elements. • I thought it could be a layout pass as well, but when scrolling to the fields on my own, I don't see any jitter. It's only when the keyboard is visible and the system attempts to scroll the view. • All the cells are the same size. • I have prepared a minimum example and the issue is reproducible. dropbox.com/s/fpqy2tx7gpvdd69/CollectionViewTesting.zip?dl=0 I have submitted a bug report to Apple with this example project. ID is FB9640529.

+1 to experiencing this issue on iOS 14 and iOS 15. I have constraints set on UICollectionViewCell with estimated heights and the layout jumps during scroll because cells are different than the "estimated" height.

Thanks for the tip! I may end up having to use that in order to move forward. I wonder if anyone from Apple can comment whether this is just a bug with the front-end.