[GH] ci_failure: dashpay/platform#3131 — Swift SDK workflow failed on test/rs-sdk-dpns-assertions

[thepastaclaw]

PR URL: Unknown (notification is for a branch CI run, not tied to a PR)

Repository: dashpay/platform
Branch: test/rs-sdk-dpns-assertions
Notification Type: ci_activity (failure)
Reviewer/Author: N/A
Snippet: CheckSuite ci_activity: Build Swift SDK and Example (no warnings) workflow run failed for test/rs-sdk-dpns-assertions branch

Action needed:

• Identify the PR associated with test/rs-sdk-dpns-assertions (if any).
• Investigate and fix the failing Build Swift SDK and Example (no warnings) workflow.
• Re-run CI and confirm green.

[thepastaclaw]

Starting investigation now: mapping branch to PR, inspecting failing 'Build Swift SDK and Example (no warnings)' runs, and determining whether failure is branch-specific or CI infrastructure.

[thepastaclaw]

Progress update: mapped branch to PR #3131 (dashpay/platform#3131). Investigated failing workflow logs and confirmed this is not branch-specific: recent runs of the same workflow across many unrelated branches are failing. Current likely root cause is brittle library/symbol validation in packages/swift-sdk/build_ios.sh (it assumes fixed xcframework library names/locations), while rs-sdk-ffi build can output different simulator library layouts (e.g., combined library vs separate libs), causing false negatives like missing simulator lib or missing SPV symbols.

[thepastaclaw]

New CI activity from GitHub notifications:

• Repo: dashpay/platform
• Branch: test/rs-sdk-dpns-assertions
• Event: Check rs-sdk gRPC coverage workflow failed
• Notification time: 2026-02-21T02:47:57Z
• Notification summary: CheckSuite ci_activity: Check rs-sdk gRPC coverage workflow run failed for test/rs-sdk-dpns-assertions branch

Action needed: investigate the failing workflow for this branch/related PR and push a fix or rerun as appropriate.

[thepastaclaw]

Found PR mapping for the branch in the notification:

• Branch test/rs-sdk-dpns-assertions -> PR test(rs-sdk): replace print-based DPNS tests with assertions, add identity error paths dashpay/platform#3131

Current CI on #3131 shows active failures on:

• Check gRPC query coverage
• JS NPM security audit

Build Swift SDK and Example was failing in an earlier branch workflow notification; current PR check set does not show a Swift build failure at this moment.

Keeping this issue in-progress to continue triage once the running checks settle.

[thepastaclaw]

Major progress: first patch (commit 3b03ff163 on PR #3131) made Swift-side simulator lib/symbol checks robust. New CI run shows that check now reports exactly what is wrong: only is present in ios-arm64-simulator, and required symbols are absent there. This indicates rs-sdk-ffi build is not actually merging in for simulator on CI. Next I’m patching to locate/merge dash-spv-ffi outputs robustly across target directory layouts used by CI.

[thepastaclaw]

Major progress: first patch (3b03ff163 on PR #3131) made Swift-side simulator lib/symbol checks robust.

New CI run shows that check now reports exactly what is wrong: only librs_sdk_ffi.a is present in ios-arm64-simulator, and required dash_spv_ffi_* symbols are absent there.

This indicates rs-sdk-ffi build is not actually merging in libdash_spv_ffi.a for simulator on CI. Next I’m patching packages/rs-sdk-ffi/build_ios.sh to locate/merge dash-spv-ffi outputs robustly across target directory layouts used by CI.

[thepastaclaw]

Update: second patch (3f72ac0eb) fixed rs-sdk-ffi merge path resolution and CI now produces libDashSDKFFI_combined.a in the simulator slice, so SPV library inclusion is happening.

However the workflow still fails at symbol validation. Investigation indicates the symbols are likely present, but the current nm invocation is brittle with Rust 1.92 object files (non-zero exit / partial parse behavior), causing false “missing symbol” results under set -euo pipefail.

Next step: patch symbol validation to use a more robust nm strategy (tolerate partial nm failures and/or use llvm-nm fallback) so it confirms actual symbol presence rather than failing on toolchain/object-format quirks.

[thepastaclaw]

Heartbeat triage: mapped branch test/rs-sdk-dpns-assertions to PR https://github.com/dashpay/platform/pull/3131.\n\nAlso saw two stuck unacked ci_activity notifications for the same branch:\n- Tests workflow run cancelled\n- Check rs-sdk gRPC coverage workflow run failed\n\nTreating these as part of this same CI investigation (no new tracker issue created to avoid duplicates).

[thepastaclaw]

Update after rerun:

• The original SPV symbol-check failure is fixed.
• New run of Build Swift SDK and Example (no warnings) now gets past symbol verification and fails later in Swift compile with header errors from generated dash_sdk_ffi.h:
  • unknown type name 'Option'
  • examples around Option<HasPendingFn>, Option<GetHighestFoundIndexFn>, Option<DestroyProviderFn>

So this is now a different, deeper failure surfaced after unblocking the earlier check. I’m patching rs-sdk-ffi/cbindgen output compatibility so optional callback fields in AddressProviderVTable are emitted as valid C types.

[thepastaclaw]

Blocked update:

I fixed the original Swift workflow failure mode from the alert (SPV simulator symbol validation and lib discovery), and confirmed those checks now pass in CI.

However, the same workflow now fails on a deeper incompatibility between packages/swift-sdk and the current rust-dashcore headers:

• New run: https://github.com/dashpay/platform/actions/runs/22249220833/job/64369424597
• Failing step gets past symbol checks and then Swift compile fails with missing FFI types:
  • FFIDetailedSyncProgress
  • FFISyncStage
  • FFINetworks
  • FFIManagedAccountCollectionSummary

Evidence indicates this is not the original CI false-negative anymore:

• libDashSDKFFI_combined.a is now produced
• Required dash_spv_ffi_config_* symbols are found successfully
• Failure is now API/header compatibility (Swift bindings expecting older key-wallet/spv FFI surface)

I’m marking this tracker issue blocked because resolving this requires a broader Swift SDK ↔ rust-dashcore API compatibility update, not just CI-script stabilization.

Commits pushed on PR #3131 during this investigation:

• thepastaclaw/platform@3b03ff163
• thepastaclaw/platform@3f72ac0eb
• thepastaclaw/platform@b9b80d2c0
• thepastaclaw/platform@1f34d5b7d