After thinking a bit more, I understand the problem. the decoder already is set to use Dates in Seconds from Epoch format, as the JSON includes the timestamp. Then any other dates as part of the attributes, need the same format Which looking back, makes total sense. It was difficult to build the live activity without knowing that the date was the problem and no other property

I did a test where I changed the type of startDate to String and the decoding error didn't appear anymore. This was just a lucky guess, I didn't find anywhere that the date was wrong

In the GitHub discussion, someone mentioned Did you compare the supported languages between your local simulator and CI simulator? The line height increases when you add a language like Hindi or Arabic as a supported language. Which reminded me that I hadn't set up a test plan for the project. A test plan is one way to configure the language/region of the the app, which I set the same as I had locally on my machine, then, with this configuration, the test passed as expected

At the end I managed to solve this issue. I wrote a blog post about it in https://tech.sats.com/ios/2023/10/15/setting-ios-app-version-with-git-tags-in-xcode-cloud.html

as a compliment to my question. A couple years ago, there was a talk https://developer.apple.com/wwdc21/10003 that mentioned sharing the OAuth token with Synced Keychain Items. That implies sharing the OAuth token, which I cannot do, but also has the effect (depending on the implementation) that if you log in on iOS, you will be logged in on the iPad and Mac if the app is present in those platforms, the same goes with log out. Also, some of our users actually share Apple ID, which caused some issues for those users as well

I experience the same issue (no solution found yet). As extra context in my case I use Keychain to sync an OAuth token between my iOS and watchOS apps.

Still the same issue

For my team this is happening still with Xcode 14.1 RC2 even though I removed the apple watch paired to the simulator I use. I assume the workaround doesn't really work because of the new simulator selector.. as in there is another simulator picked by default with an Apple Watch paired with it. I will try by removing Apple Watch paired to all simulators

Feedback reported ID: FB11678756 Mmm.. while development I casually added a line, which made importing the SATSCore framework in the file. That framework was implicitly available already through the @_exported import SATSCore call in the app’s entry point. It may seem that this issue may be related to implicitly imported libraries

I should add this only fails with Xcode previews, not when running the app in simulator/device. I use a M1 Max MacBook pro

In the post I originally linked someone posted the solution for this problem https://developer.apple.com/forums/thread/707994?answerId=717730022#717730022 deleted /Library/Developer/PrivateFrameworks installed Xcode.app/Contents/Resources/Packages/XcodeSystemResources.pkg on my system at least, XcodeSystemResources.pkg creates the /Library/Developer/PrivateFrameworks folder. anyway that fixed "Toggle Appearance" in the Simulator for me! thanks for the tip!

I didn't mentioned in the post, but I am talking about the simulator. I also have the same behavior described by @DoxxerApple 👇

One thing I think it may be related is some local Xcode files you would normally add to .gitignore. I cloned the project again in a different folder, then it works to open that copy of the project

For me too. this started happening fairly recently.

I was able to build. First, I manually set the version in the project to 4.7.0 for both Apple Watch, Extension and Main app. I got some errors after that, but they seem "random errors" on the builds. Then I noticed our workflow was using "the latest Xcode" which meant Xcode 13.3 Beta 1. Instead I set it to Xcode 12.2.1 I got some random errors after. I tried the build hours later and finally it worked. Since I did more than one approach trying to fix this at a time, I cannot tell what "fix" my issue. I will report later when I make a new build and if I get more info