Performance is not the most critical aspect. RAM, disk space and screen size are, IMO, much more important. I work frequently on a 2015 iMac (3,3 GHz Intel Core i5 four core, so not a really powerful machine with today standards). I upgraded from 8 to 24 GB RAM (was much needed), got original 2 TB disk and 27" screen. It is perfect for Xcode development.

Thanks for feedback. Don't forget to close the thread my marking the correct answer. Good continuation.

Could you show the relevant code and the context of code (if possible full class which includes timer).

There is a misunderstanding. You should not remove the all declaration @Binding var id: UUID    just replace with var id: UUID

Note that @Binding does not seem necessary here.

I understand your frustration, but you give the answer yourself: "You need to submit an Appeal to expedite the process BUT you need to give a valid reason such as there is a bug happening in production or something..." That's the case everywhere when you appeal. There must be a reason for appealing that may justify a change in decision. In addition, when an app is rejected it is very important to explain clearly what you did to correct or why you think it is a misunderstanding. Not by considering the reviewer is dumb, but simply that he/she cannot spend 2 hours on the app and so needs easy to check information.

You market your answer as the correct answer,. So it seems you have found the solution ? What was the problem ? That could be of interest for others.

So it seems you have found the solution ? What was the problem ? That could be of interest for others.

You welcome. Sure several of us will try to help as soon as they get the complementary info.

You're probably right from previous post. But he/she should be more explicit…

Thanks for feedback. In fact the key was id = UUID(). It seems you never use index ? Otherwise, this is probably a typo: index: "2, id: 2"

Yes, using func is much easier. But your question was a challenge to find a way to express it as a var. Good continuation, don't forget to close the thread. It may be of interest of others to see there was a solution tou the question, even though too complex for the benefit.

If you can't rely on simulator running on Mac, you may need to find an iPhone with older iOS version.

Thanks for feed back. It was effectively a bug. You close by marking the answer you consider correct (the circle with the √ sign below the up and down arrow next to the answer. So you can also close your bug report.

No, it should support 15.4.1 as well. Contact support.