Yes. Typically, you would use Apple's TestFlight to distribute builds to your testers.

Your new json file has several errors (the first is at line 1009). Use an on-line json checker, to help you to fix it up. Parsing a large json file on app startup is probably a bad idea... but fix the json first!

This method can cause UI unresponsiveness if invoked on the main thread. Instead, consider waiting for the -locationManagerDidChangeAuthorization: callback and checking authorizationStatus first.

regarding the verification I have already done it with this online software That may be so, but the json in your link still contains errors. I suggest you try an alternative online json validator. do you have a better idea Yes, but let's get the app working first.

MenuItem.example is only defined for a DEBUG build. Uploading to the App Store uses a Release build, so MenuItem.example does not exist. Try replacing: #if DEBUG static let example = MenuItem(id: UUID(), name: "Maple French Toast", recipe: "Breakfast Icecream", ingredient: "Sweet, fluffy, and served piping hot, our French toast is flown in fresh every day from Maple City, Canada, which is where all maple syrup in the world comes from. And if you believe that, we have some land to sell you…", instruction: "Cook it", emTipTitle: "Energy management", emTip: "Practice 5 minute rule") #endif with: static let example = MenuItem(id: UUID(), name: "Maple French Toast", recipe: "Breakfast Icecream", ingredient: "Sweet, fluffy, and served piping hot, our French toast is flown in fresh every day from Maple City, Canada, which is where all maple syrup in the world comes from. And if you believe that, we have some land to sell you…", instruction: "Cook it", emTipTitle: "Energy management", emTip: "Practice 5 minute rule")

Rather than adding your code as a screenshot, use the formatting tools, to format your code as a Code Block. Then we will be able to read it, and see if we can help you.

And once again, the Forum is entirely overrun by spam. Spam which seems particularly easy to spot. It's extra-annoying when the spammers mark their own answer as correct, to improve their rating.

It may depend on your deployment target, as Clock requires iOS 16. (So if your deployment target is less that 16, the compiler will throw an error.)

Your error message says you must do one of: rebuild it with bitcode enabled. obtain an updated library from the vendor. disable bitcode for this target. When you tried those 3 solutions, what was the outcome?

Please don't repeat post. This is a forum for serious developers.

As I said, option 1: rebuild it with bitcode enabled

On iOS 16 I see: Settings > Privacy & Security > Developer Mode ...which shows a Switch, to turn it on. Which requires a restart. Then after restarting, I had to confirm turning Developer Mode on.

Did that fix it for you, @arasharcher?

It's not clear at this stage, but discussions on the wider Internet suggest that this may be a bug in Xcode 14.

Yes, we seem to be in yet another period of excessive spam posts. A proper solution is needed.