Process completed with exit code 1.

clang: error: linker command failed with exit code 1 (use -v to see invocation)

ld: framework 'libsql_experimental' not found

clang: error: linker command failed with exit code 1 (use -v to see invocation)

ld: framework 'libsql_experimental' not found

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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@v4, actions/checkout@v4, actions/setup-java@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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@v4, actions/checkout@v4, actions/setup-java@v3, actions/setup-node@v3, gradle/actions/setup-gradle@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Failed to restore gradle-home-v1|Linux|android[b8a35c2f917259958c9abe8f2ff1b5ff]-9566fd0c94e544a510158ad460855717a0f6f73e: Error: Cache service responded with 400

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-java@v3, actions/setup-node@v3, gradle/actions/setup-gradle@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Failed to restore gradle-home-v1|Linux|android-sqlcipher[b8a35c2f917259958c9abe8f2ff1b5ff]-9566fd0c94e544a510158ad460855717a0f6f73e: Error: Cache service responded with 400

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

'RCTSurface' is deprecated: This API will be removed along with the legacy architecture.

'RCTSurface' is deprecated: This API will be removed along with the legacy architecture.

'RCTRootShadowView' is deprecated: This API will be removed along with the legacy architecture.

'RCTScrollView' is deprecated: This API will be removed along with the legacy architecture.

'RCTRootView' is deprecated: This API will be removed along with the legacy architecture.

'RCTModalHostView' is deprecated: This API will be removed along with the legacy architecture.

'RCTModalHostView' is deprecated: This API will be removed along with the legacy architecture.

[CP] libsql_experimental.xcframework: Unable to find matching slice in 'ios-arm64 ios-arm64-simulator' for the current build architectures (arm64 x86_64) and platform (-iphonesimulator).

parameter '<ReturnT>' not found in the function declaration [-Wdocumentation]

parameter '<ReturnT>' not found in the function declaration [-Wdocumentation]

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

'RCTModalHostView' is deprecated: This API will be removed along with the legacy architecture.

'RCTModalHostView' is deprecated: This API will be removed along with the legacy architecture.

variable 'errorMessage' may be uninitialized when used here [-Wconditional-uninitialized]

variable 'errorMessage' may be uninitialized when used here [-Wconditional-uninitialized]

variable 'errorMessage' may be uninitialized when used here [-Wconditional-uninitialized]

variable 'errorMessage' may be uninitialized when used here [-Wconditional-uninitialized]

variable 'errorMessage' may be uninitialized when used here [-Wconditional-uninitialized]

variable 'errorMessage' may be uninitialized when used here [-Wconditional-uninitialized]

parameter '<ReturnT>' not found in the function declaration [-Wdocumentation]

parameter '<ReturnT>' not found in the function declaration [-Wdocumentation]

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

'SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION' macro redefined [-Wmacro-redefined]

'SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION' macro redefined [-Wmacro-redefined]

variable 'errorMessage' may be uninitialized when used here [-Wconditional-uninitialized]

variable 'errorMessage' may be uninitialized when used here [-Wconditional-uninitialized]

variable 'errorMessage' may be uninitialized when used here [-Wconditional-uninitialized]

'SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION' macro redefined [-Wmacro-redefined]

'SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION' macro redefined [-Wmacro-redefined]

'SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION' macro redefined [-Wmacro-redefined]

parameter '<ReturnT>' not found in the function declaration [-Wdocumentation]

parameter '<ReturnT>' not found in the function declaration [-Wdocumentation]

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

'SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION' macro redefined [-Wmacro-redefined]

'SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION' macro redefined [-Wmacro-redefined]

variable 'errorMessage' may be uninitialized when used here [-Wconditional-uninitialized]

variable 'errorMessage' may be uninitialized when used here [-Wconditional-uninitialized]

variable 'errorMessage' may be uninitialized when used here [-Wconditional-uninitialized]

'SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION' macro redefined [-Wmacro-redefined]

'SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION' macro redefined [-Wmacro-redefined]

'SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION' macro redefined [-Wmacro-redefined]

parameter '<ReturnT>' not found in the function declaration [-Wdocumentation]