Skip to content

fix: show explicit target tick expired error on transfer send#139

Open
alez04 wants to merge 5 commits intodevfrom
fix/bug/137-target-tick-expired-error
Open

fix: show explicit target tick expired error on transfer send#139
alez04 wants to merge 5 commits intodevfrom
fix/bug/137-target-tick-expired-error

Conversation

@alez04
Copy link
Copy Markdown
Contributor

@alez04 alez04 commented Mar 31, 2026

Summary

  • classify send failures caused by expired target tick before falling back to network error mapping
  • apply the same handling in both transfer and transfer-rights flows
  • add localized targetTickExpired error messages for all supported locales

Issue

Closes #137

Validation

  • npm run lint
  • npm run build

@alez04 alez04 requested review from ahmed-tarek-salem and sallymoc and removed request for sallymoc March 31, 2026 10:06
@sallymoc
Copy link
Copy Markdown
Contributor

sallymoc commented Apr 2, 2026

@alez04 please have a look on the feedback given via DM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Transfer with manual target tick close to current tick shows misleading "Network error" message

2 participants