Okay! I have nailed the issue on my side, and you can easily check if that's the same on yours. Do you see your Live Activity blinking before the system kills it? If so, you have an infinite refresh loop in your SwiftUI view. Meaning your Live Activity never settles on how it should be rendered. After a certain number of rendering attempts, the system will kill your Live Activity. The solution is to simplify the views inside your Live Activity. You might have a view that is pretty complex to draw, for which the layout never truly settles. If you are unsure, try to comment out each component one by one until you pinpoint the faulty one. Hope that helps. I was able to solve my issue.

I am also experiencing this issue. I wish I add more information to provide, but no.

I know that's an old thread, but has anyone tried local notification via UNUserNotificationCenter? I am planning to try this approach tonight. When starting the live activity in the app, we maybe can schedule a local notification and catch it from the live activity?

Is there a way to attach the debugger to the Live Activity extension to use breakpoints or debug print?

I've opened a thread on the Swift Forum. I hope we can get some help there. https://forums.swift.org/t/fatal-cannot-use-bare-repository/75588 Also, the solution mentioned by ndebei79 works if that can help some.

I could reproduce on a brand new project with https://github.com/apple/swift-log.git

I am also facing this issue right now. wth is that?

@mitchtreece Was your package crashing with XCode 14 or this only occurred after moving to XCode 15? I am also experiencing a similar issue, with an old framework written in Objective-C that I am using my project. When compiling with XCode 14, no problem at all the code works just fine, but when compiling with XCode 15, the package crash at the first instantiation of a class, with no obvious reason.

Summary In case it can help someone, here my solution. Our team uses a "self-hosted" Sentry instance, so I had to provide the URL to sentry-cli. Instead of passing the parameters directly as arguments to the binary, I used the Environment Variable panel in XCode Cloud. SENTRY_URL, SENTRY_ORG, SENTRY_PROJECT, SENTRY_AUTH_TOKEN. The advantage is that your variables do not appear in the script, and also you can set the SENTRY_AUTH_TOKEN as secret. Another advantage of XCode Cloud is that you can use Homebrew to install dependencies. See documentation. Scripts ci_scripts/ci_post_clone.sh #!/bin/sh brew install getsentry/tools/sentry-cli ci_scripts/ci_post_xcodebuild.sh #!/bin/sh if which sentry-cli >/dev/null; then ERROR=$(sentry-cli upload-dif --include-sources "$CI_ARCHIVE_PATH/dSYMs" 2>&1 >/dev/null) if [ ! $? -eq 0 ]; then echo "warning: sentry-cli - $ERROR" fi else echo "warning: sentry-cli not installed, download from https://github.com/getsentry/sentry-cli/releases" fi

Not that I can offer an explanation, but I am experiencing the same, no matter what value I send to https://appleid.apple.com/auth/revoke it always returns HTTP 200 ¯_(ツ)_/¯