Skip to content

Conversation

@GabrielTozatti
Copy link
Collaborator

@GabrielTozatti GabrielTozatti commented Jan 27, 2026

Description

Fixes the pending state handling to ensure that any initiated operation (transaction, swap, bridge, or stake) blocks the creation of new actions while there is an open pending operation. Also ensures the account state is updated in real time, without requiring a manual page refresh.

Summary

  • Unified pending state validation across all operation types (transaction, swap, bridge, stake)
  • Implemented a global lock to prevent new actions while a pending operation exists
  • Added a clear user-facing warning when there is an open pending operation
  • Fixed account state synchronization to reflect pending operations without manual refresh
  • Prevented multiple simultaneous pending transactions from being created
  • Ensured account state consistency across all operation flows

Screenshots

Video: Link

Checklist

  • I reviewed my PR code before submitting
  • I ensured that the implementation is working correctly and did not impact other parts of the app
  • I implemented error handling for all actions/requests and verified how they will be displayed in the UI (or there was no error handling needed).
  • I mentioned the PR link in the task

Copy link
Member

@guimroque guimroque left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review - Summary

What was done

This PR fixes pending state handling by ensuring that pending transaction state is properly synchronized across all operation types (bridge, liquid stake, and swap). The changes add pendingSignerTransactions.refetch() calls after transaction operations to update the global pending state without requiring manual page refresh.

Positive Points

  • ✅ Consistent approach across all operation types (bridge, swap, liquid stake)
  • ✅ Proper integration with existing transaction context
  • ✅ Small, focused changes that address the specific issue
  • ✅ Follows existing code patterns and conventions
  • ✅ Addresses real-time state synchronization problem

Issues Found

  • No critical issues found
  • Code follows project standards and naming conventions
  • Changes are minimal and focused on the specific problem
  • Proper error handling is already in place from existing code

Total comments: 0 (0 critical, 0 important)

@aws-amplify-us-east-1
Copy link

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-809.db1b4e2lqk8yl.amplifyapp.com

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.

3 participants