Add timeout and retry to transaction confirmation

[Jim8y]

Problem

SendingPage polls for confirmation every 15s up to 10 times (~2.5 min). If the transaction never appears in a block within that window (or RPC keeps erroring), the loop just ends and the page stays on an indefinite spinner / 'Confirming…' with no timeout, error, or way out.

Fix

Add an explicit timed-out state: when the polling window exhausts without a result, stop the spinner and show a 'Still waiting for confirmation' message + a Retry button (re-runs the poll). Adds TransactionStillPending/Pending/Retry strings in all three locales.

Note

This stacks on #58 (it builds on that PR's confirmation state machine), so this PR's diff currently includes #58. Review/merge after #58; it then rebases down to just the timeout change. No new dependency.

Verified by static review (no MAUI workload locally); please confirm in CI.

[Copilot]

Pull request overview

This PR improves the SendingPage transaction confirmation UX by extending confirmation from “block included” to “execution succeeded/failed” and by adding a timeout state with a user-driven retry, preventing the page from getting stuck indefinitely on “Confirming…”.

Changes:

• Add Succeeded / TimedOut state and update the SendingPage UI to show Confirming / Succeeded / Failed / Pending (timed out) with a Retry button.
• After block inclusion, call getapplicationlog and require VMState.HALT to report success; otherwise report failure.
• Add new localized strings (Failed, TransactionFailed, Pending, Retry, TransactionStillPending) in EN / zh-Hans / zh-Hant.

Reviewed changes

Copilot reviewed 5 out of 6 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
OneGateApp/Properties/Strings.resx	Adds new EN strings for failed/pending/retry confirmation states.
OneGateApp/Properties/Strings.zh-Hans.resx	Adds Simplified Chinese strings for failed/pending/retry confirmation states.
OneGateApp/Properties/Strings.zh-Hant.resx	Adds Traditional Chinese strings for failed/pending/retry confirmation states.
OneGateApp/Properties/Strings.Designer.cs	Exposes the new string resource accessors.
OneGateApp/Pages/SendingPage.xaml	Updates UI bindings to new state properties and adds Failed/Pending UI + Retry button.
OneGateApp/Pages/SendingPage.xaml.cs	Implements timeout + retry behavior and execution-result validation via getapplicationlog.

Files not reviewed (1)

• OneGateApp/Properties/Strings.Designer.cs: Generated file

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Jim8y]

Handled the open #59 review threads.

Changes:

• Added a polling re-entrancy guard so Retry cannot start overlapping QueryTransactionStatus() loops.
• Missing or unparsable execution status now falls back to confirmed/unknown instead of a false failed state. FAULT still reports failure when vmstate is present.
• Added the PR transaction-status resource keys across all locale files; resource parity is now 15 files / 288 keys.
• Merged current origin/master into the branch with no conflicts.

Validation:

• git diff --check
• Conflict scan with rg -n "<<<<<<<|=======|>>>>>>>" OneGateApp
• Resource parity checked: 15 resource files, 288 keys
• iOS simulator build/install/launch verified, then Wallet -> Send UI verified
• Android emulator build/install/launch verified, then Wallet -> Send UI verified
• Android crash buffer remained empty after launch and navigation

Screenshots:

• iOS: https://github.com/Jim8y/OneGateApp/releases/download/pr-59-screenshots-20260621/onegate-pr59-ios-send.png
• Android: https://github.com/Jim8y/OneGateApp/releases/download/pr-59-screenshots-20260621/onegate-pr59-android-send.png

[erikzhang]

Conflicts

[Jim8y]

Resolved the conflict reported by Erik.

What changed in this follow-up:

• Merged latest origin/master into this branch.
• Resolved localized .resx conflicts by keeping this PR's pending/retry/failure strings while preserving master's newer localized strings.

Validation on branch head 88c0b17:

• No conflict markers remain.
• Localized .resx key parity passed: 310 keys across 15 files.
• git diff --check passed.
• Android build passed: dotnet build OneGateApp/OneGateApp.csproj -f net10.0-android -r android-arm64 ....
• iOS simulator build passed: dotnet restore ... -p:TargetFramework=net10.0-ios -r iossimulator-arm64 + dotnet build ... -f net10.0-ios -r iossimulator-arm64 --no-restore ....

Notes: builds still report existing SQLitePCLRaw NU1903 warnings and existing iOS duplicate asset warnings, with no errors.

[erikzhang]

Conflicts

[Jim8y]

Resolved latest master conflicts.

Changes pushed:

• Re-merged latest master.
• Kept this PR's timeout/retry pending-state UI.
• Preserved master transaction-failure semantics based on VMState.HALT.
• Resolved resource conflicts without dropping either side's strings.

Validation:

• iOS simulator build passed: dotnet build -f net10.0-ios -r iossimulator-arm64 -p:EnableCodeSigning=false
• Android build passed: dotnet build -f net10.0-android -r android-arm64 -p:EmbedAssembliesIntoApk=true

Notes:

• Build warnings are existing SQLitePCLRaw NU1903 advisories.
• The local keychain has no valid Apple signing identities, so iOS validation used simulator build with code signing disabled.