Post

Replies

Boosts

Views

Activity

Reply to PHPickerViewController crashes when configuration has preselectedAssetIdentifiers
I'm having a similar issue even with selectionLimit > 1. The issue seems to be that the PickerResults itemIdentifers don't have the UTTypes for thepreselectedAssetIdentifiers that are passed in // For an id that was passed into `preselectedAssetIdentifiers` <PUPhotosFileProviderItemProvider: 0x60000306d3b0> {types = ( )} // For a newly selected photo <PUPhotosFileProviderItemProvider: 0x60000306de60> {types = ( "public.jpeg", "com.apple.private.photos.thumbnail.standard", "com.apple.private.photos.thumbnail.low" )} Haven't found a solution but to remove the preselectedAssetIdentifiers Hope this helps Killian
Mar ’24
Reply to Crash in iOS18
I came across this crash as well. It seemed to be because we were manually dequeuing supplementary view in the func collectionView(collectionView:layout:referenceSizeForHeaderInSection:) -> CGSize. Once I found a way to use supplementaryView instead of dequeueReusableSupplementaryView, the issue was resolved let headerView = collectionView.supplementaryView(forElementKind: UICollectionView.elementKindSectionHeader, at: indexPath) Xcode 16 was also complaining/suggesting to use dequeueConfiguredReusableSupplementary instead of dequeueReusableSupplementaryView(ofKind:withReuseIdentifier:for:). We had a mix of iOS 14+ registration APIs for regular cells but older registration style for supplementary views. I updated to use UICollectionView.SupplementaryRegistration at the same time, which might've helped the issue as well Hope these help
Sep ’24
Reply to Live Activities Random Loading Spinner
I came across similar issue. We are also using a countdown timer in live activity and dynamic island. Due to this issue with Text(date, style: .timer) in a dynamic island we leveraged the workaround provided here. This workaround caused issues in the live activity, mainly caused by the frame modifier on the Text view. This issue only occurred in dynamic island, so I just stopped using the workaround for our Live Activity and the issue went away Hope this helps!
Oct ’24