Process completed with exit code 127.

The process '/usr/bin/gpg' failed with exit code 2

Process completed with exit code 127.

The process '/usr/bin/gpg' failed with exit code 2

Failed to create NSXPCConnection

Failed to create NSXPCConnection

Failed to create NSXPCConnection

Failed to create NSXPCConnection

Failed to create NSXPCConnection

Failed to create NSXPCConnection

Failed to create NSXPCConnection

Failed to create NSXPCConnection

Failed to create NSXPCConnection

Failed to create NSXPCConnection

Failed to create NSXPCConnection

Failed to create NSXPCConnection

Failed to create NSXPCConnection

Failed to create NSXPCConnection

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

code after 'throw' will never be executed

'unregisterRemoteNotifications' is deprecated: Please migrate to the new SpeziNotifications package: https://github.com/StanfordSpezi/SpeziNotifications

'registerRemoteNotifications' is deprecated: Please migrate to the new SpeziNotifications package: https://github.com/StanfordSpezi/SpeziNotifications

'unregisterRemoteNotifications' is deprecated: Please migrate to the new SpeziNotifications package: https://github.com/StanfordSpezi/SpeziNotifications

'registerRemoteNotifications' is deprecated: Please migrate to the new SpeziNotifications package: https://github.com/StanfordSpezi/SpeziNotifications

'unregisterRemoteNotifications' is deprecated: Please migrate to the new SpeziNotifications package: https://github.com/StanfordSpezi/SpeziNotifications

'registerRemoteNotifications' is deprecated: Please migrate to the new SpeziNotifications package: https://github.com/StanfordSpezi/SpeziNotifications

'nonisolated(unsafe)' has no effect on property 'storage', consider using 'nonisolated'

'nonisolated(unsafe)' has no effect on property 'storage', consider using 'nonisolated'

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

'unregisterRemoteNotifications' is deprecated: Please migrate to the new SpeziNotifications package: https://github.com/StanfordSpezi/SpeziNotifications

'registerRemoteNotifications' is deprecated: Please migrate to the new SpeziNotifications package: https://github.com/StanfordSpezi/SpeziNotifications

'unregisterRemoteNotifications' is deprecated: Please migrate to the new SpeziNotifications package: https://github.com/StanfordSpezi/SpeziNotifications

'registerRemoteNotifications' is deprecated: Please migrate to the new SpeziNotifications package: https://github.com/StanfordSpezi/SpeziNotifications

'unregisterRemoteNotifications' is deprecated: Please migrate to the new SpeziNotifications package: https://github.com/StanfordSpezi/SpeziNotifications

'registerRemoteNotifications' is deprecated: Please migrate to the new SpeziNotifications package: https://github.com/StanfordSpezi/SpeziNotifications

'nonisolated(unsafe)' has no effect on property 'storage', consider using 'nonisolated'

'nonisolated(unsafe)' has no effect on property 'storage', consider using 'nonisolated'

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

code after 'throw' will never be executed

code after 'throw' will never be executed

'unregisterRemoteNotifications' is deprecated: Please migrate to the new SpeziNotifications package: https://github.com/StanfordSpezi/SpeziNotifications

'registerRemoteNotifications' is deprecated: Please migrate to the new SpeziNotifications package: https://github.com/StanfordSpezi/SpeziNotifications

'unregisterRemoteNotifications' is deprecated: Please migrate to the new SpeziNotifications package: https://github.com/StanfordSpezi/SpeziNotifications

'registerRemoteNotifications' is deprecated: Please migrate to the new SpeziNotifications package: https://github.com/StanfordSpezi/SpeziNotifications

'nonisolated(unsafe)' has no effect on property 'storage', consider using 'nonisolated'

'nonisolated(unsafe)' has no effect on property 'storage', consider using 'nonisolated'

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

'#require(_:_:)' is redundant because 'Text("Spezi")

'#require(_:_:)' is redundant because 'Text("Spezi")

'#require(_:_:)' is redundant because 'Text("Spezi")

'nonisolated(unsafe)' has no effect on property 'storage', consider using 'nonisolated'

'nonisolated(unsafe)' has no effect on property 'storage', consider using 'nonisolated'

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

'#require(_:_:)' is redundant because 'Text("Spezi")

'nonisolated(unsafe)' has no effect on property 'storage', consider using 'nonisolated'

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

'#require(_:_:)' is redundant because 'Text("Spezi")

'nonisolated(unsafe)' has no effect on property 'storage', consider using 'nonisolated'

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

'#require(_:_:)' is redundant because 'Text("Spezi")

'#require(_:_:)' is redundant because 'Text("Spezi")

'#require(_:_:)' is redundant because 'Text("Spezi")

will never be executed

will never be executed

will never be executed

'nonisolated(unsafe)' has no effect on property 'storage', consider using 'nonisolated'

'nonisolated(unsafe)' has no effect on property 'storage', consider using 'nonisolated'

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

will never be executed

'#require(_:_:)' is redundant because 'Text("Spezi")

'nonisolated(unsafe)' has no effect on property 'storage', consider using 'nonisolated'

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

'#require(_:_:)' is redundant because 'Text("Spezi")

'#require(_:_:)' is redundant because 'Text("Spezi")

'#require(_:_:)' is redundant because 'Text("Spezi")

'nonisolated(unsafe)' has no effect on property 'storage', consider using 'nonisolated'

'nonisolated(unsafe)' has no effect on property 'storage', consider using 'nonisolated'

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

'#require(_:_:)' is redundant because 'Text("Spezi")

'#require(_:_:)' is redundant because 'Text("Spezi")

'#require(_:_:)' is redundant because 'Text("Spezi")

'nonisolated(unsafe)' has no effect on property 'storage', consider using 'nonisolated'

'nonisolated(unsafe)' has no effect on property 'storage', consider using 'nonisolated'

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

'unregisterRemoteNotifications' is deprecated: Please migrate to the new SpeziNotifications package: https://github.com/StanfordSpezi/SpeziNotifications

'registerRemoteNotifications' is deprecated: Please migrate to the new SpeziNotifications package: https://github.com/StanfordSpezi/SpeziNotifications

'unregisterRemoteNotifications' is deprecated: Please migrate to the new SpeziNotifications package: https://github.com/StanfordSpezi/SpeziNotifications

'registerRemoteNotifications' is deprecated: Please migrate to the new SpeziNotifications package: https://github.com/StanfordSpezi/SpeziNotifications

'nonisolated(unsafe)' has no effect on property 'storage', consider using 'nonisolated'

'nonisolated(unsafe)' has no effect on property 'storage', consider using 'nonisolated'

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

'#require(_:_:)' is redundant because 'Text("Spezi")

'nonisolated(unsafe)' has no effect on property 'storage', consider using 'nonisolated'

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

'#require(_:_:)' is redundant because 'Text("Spezi")

'#require(_:_:)' is redundant because 'Text("Spezi")

'#require(_:_:)' is redundant because 'Text("Spezi")

'nonisolated(unsafe)' has no effect on property 'storage', consider using 'nonisolated'

'nonisolated(unsafe)' has no effect on property 'storage', consider using 'nonisolated'

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

'#require(_:_:)' is redundant because 'Text("Spezi")

'#require(_:_:)' is redundant because 'Text("Spezi")

'#require(_:_:)' is redundant because 'Text("Spezi")

'nonisolated(unsafe)' has no effect on property 'storage', consider using 'nonisolated'

'nonisolated(unsafe)' has no effect on property 'storage', consider using 'nonisolated'

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

'#require(_:_:)' is redundant because 'Text("Spezi")

'nonisolated(unsafe)' has no effect on property 'storage', consider using 'nonisolated'

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

'#require(_:_:)' is redundant because 'Text("Spezi")

'nonisolated(unsafe)' has no effect on property 'storage', consider using 'nonisolated'

Skipped TestAppUITests.LifecycleHandlerTests.testServiceModule