UICollectionView | simple pinterest like layout using UICollectionView | Grid library

Here are a few things I would think about / consider changing in trying to implement what you want and which might be the reason we see this strange cell behavior:

1. Use indexPath.item rather indexPath.row when dealing with collection views

2. In you prepareForReuse, you actually discard the playerView so when you try to restore the player again from cache playerView?.player = player - the playerView is most likely nil and needs to be reinitialized

3. You don't need to hang onto the the cell as a whole, this might work, however I think we should let collection view do its business of recycling the cell. Hang onto just the player instead

4. I have not done it, however, think about how handle removing notification observers when discarding the cells as you might be subscribing to a notification more than once and this could cause issues down the line

5. I also haven't done this, but remember to remove the video from your cache when you the video finishes since you don't want the cell to react anymore

Here are some small changes I made:

CustomCell

You should reload collectionView after setting new data.

It seems like there is a problem with your array. It's created dynamically and has conflicts with UICollectionView's implementation.

Try replacing your array with the following static array.

The UICollectionReusableView is set up fine I believe and I think an automatic inset is applied to the UICollectionView because of the safe area.

Try one of the two options below in your viewDidLoad and it might work

I suspect and I could be wrong, you have set delaysContentTouches to false for the UICollectionView.

This would make any touch be interpreted as a button tap.

Instead of removing the button from the cell, here is my set up which sounds similar to yours and gives the desired end result:

Custom UICollectionView with a label and button that spans the whole collection view cell

As far as I can see, the method is getting called not when you just rotate the device, but when the layout changes. Meaning, if you change from Landscape Left to Landscape Right the delegate method is not called — however if you rotating from any Landscape to Portrait or other way around, it is working fine.

For maintaining the centered collection view cell, add the targetContentOffset(forProposedContentOffset:) method. This is called after a rotation, and is not the same as your current targetContentOffset(forProposedContentOffset:withScrollingVelocity:) method. In your final code, you should use both of these methods. To summarize:

• targetContentOffset(forProposedContentOffset:) is called after a layout change
• targetContentOffset(forProposedContentOffset:withScrollingVelocity:) is called when the user lifts their finger

So, in your PagingFlowLayout class, paste the following code:

To automatically scroll to the rightmost element you can use the scrollTo function of the ScrollViewReader view.

You should set an id to each element of the ForEach loop and use the onAppear modifier of the ForEach to scroll to the rightmost element (the last id). This should be done only if language direction is right to left (Locale.characterDirection gives this information).

The code below illustrates this:

One way to do this is to keep two image arrays, defaultImages of type [UIImage] and inputImages of type [UIImage?]. The defaultImages will hold your camera and photo images, and inputImages will hold images selected by the user. Initialize the images as:

Somewhere in your program someone is probably calling scrollToItems(at:,scrollPosition:). They either don't know the collection is empty and are just passing in (row:0, item:0) as the index path instead of just skipping the scroll call altogether. Or they think your collection contains at least one item.

To further diagnose the issue, I would either set a breakpoint on exceptions or set a breakpoint on the UIScrollView function and look at the backtrace to see who is making the call.

You also want to check your Data Source to make sure it's been updated with the correct number of items at the time the scroll happens.

But having a backtrace to find out who or what is causing the scrollview to scroll would be a great first step.