I have a separate datasource class that extends UICollectionViewDatasource and it contains cell registration. Sometimes, I want to get instance member inside my cell registration closure but the cell registration itself is in the initialization state so it can't get the instance member. To tackle that, I labeld my property as lazy so that it will get access to the instance member when it was used. I'm not sure this is a good way to do this but it works in XCode 12. When I build and run on XCode 13 beta, it crashed with NSInternalInconsistencyException.

Attempted to dequeue a cell using a registration that was created inside -collectionView:cellForItemAtIndexPath: or inside a UICollectionViewDiffableDataSource cell provider. Creating a new registration each time a cell is requested will prevent reuse and cause created cells to remain inaccessible in memory for the lifetime of the collection view. Registrations should be created up front and reused.

According to my understanding, lazy properties will be initialized as soon as they get called and only for once. So, I'm wondering if you could tell me if this is the problem with my XCode 13 or it's my problem. I'm also curious is it good to use lazy in that way? Or should I change them into static instead of instance properties? Thank you for reading till the end.