Skip to content

Raw provider codes shown in USDT deposit details and Copy Details #1503

Closed

Description

@jvsena42

Raw provider identifiers reach users in two places on the USDT cross-network deposit screens.

  1. Deposit details: UsdtDepositsScreen.kt:474 renders detail.statusCode verbatim under the refund field. For a deposit that needs attention, users see standing_route_unavailable.
  2. Copy Details text: UsdtSupportActions.kt:48 and :63 add Status: $status, which puts the enum name (BRIDGE_NEEDS_ATTENTION) in the text the user copies or sends to support.

Found during the device gate of #1494. The code is already on master.

Steps (local USDT fixture)

  1. Create an Orchestra deposit and move it to needs attention with code standing_route_unavailable.
  2. Open USDT Receive → Network → Cross-Network Deposits and open the deposit. The raw code appears under the refund field.
  3. On a failed or needs-attention bridge, tap Copy Details. The clipboard holds Status: BRIDGE_NEEDS_ATTENTION.

Expected: a localized, human-readable reason in the UI. The copied text can keep the raw code for support if that is intended, but it should sit beside the readable status, not replace it.

Activity

  1. added this to the 3.0.0 milestone on Oct 15, 2026
  2. modified the milestones: 3.0.0, 3.0.5 on Oct 15, 2026
  3. jvsena42 commented on Oct 15, 2026

    @jvsena42
    MemberAuthor

    iOS shows the same raw standing_route_unavailable text on a deposit that needs attention (seen in the bitkit-ios #942 simulator gate). The fix should cover both platforms.

  4. ben-kaufman commented on Oct 15, 2026

    @ben-kaufman
    Contributor

    Fixed on Android in #1506 and on iOS in synonymdev/bitkit-ios#948. Deposit details now show existing localized support guidance. Copy Details retains technical status and provider codes beside the readable status for support. The Android UI test checks that standing_route_unavailable is absent from the screen; both platforms have diagnostic-text assertions.

  5. modified the milestones: 3.0.5, 3.0.0 on Oct 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions