Having a similar issue with Xcode 14 release from the App Store. It shows something about watch metadata, then stops after failing to prepare the phone (says the OS version is not compatible).
Met with App Review today, the spirit of the rule is that if you have an account creation feature, you need to have a matching deletion feature. Account deletion does not necessarily need to be instant, but the timeline and what happens with the customer's data must be clear. In any case, the deletion needs to begin in the app (IMO this prevents linking to Safari or Mail since that does not actually start the process, just navigates to where you can start).
I understand you are not dealing with static sized cells, but for anyone else who stumbles upon this...
This may sound obvious, but in my experience the jumping only occurs when a cell size changes during a layout reset. So instead of using .estimated, I used .absolute with the same value (it was a static sized cell) and the jumping stopped.
Having a similar issue with Xcode 14 release from the App Store. It shows something about watch metadata, then stops after failing to prepare the phone (says the OS version is not compatible).
Met with App Review today, the spirit of the rule is that if you have an account creation feature, you need to have a matching deletion feature. Account deletion does not necessarily need to be instant, but the timeline and what happens with the customer's data must be clear. In any case, the deletion needs to begin in the app (IMO this prevents linking to Safari or Mail since that does not actually start the process, just navigates to where you can start).
I understand you are not dealing with static sized cells, but for anyone else who stumbles upon this...
This may sound obvious, but in my experience the jumping only occurs when a cell size changes during a layout reset. So instead of using .estimated, I used .absolute with the same value (it was a static sized cell) and the jumping stopped.