Add dApp load failure and retry states

[Jim8y]

Summary

• Add explicit loading, failure, and retry states around the dApp WebView runtime page.
• Add a 30-second timeout so stalled navigations do not leave a permanent blank screen.
• Keep the existing app-link/new-window behavior and wallet bridge intact.
• Handle app-link metadata network and JSON failures in-app, with retry support.
• Reuse the localized Retry resource already present on current master.

Validation

• Android build: passed.
• iOS simulator build: passed.
• Android emulator: verified the offline app-link path remains alive and shows the recoverable failure state.
• iOS simulator: verified the loading state and successful N3 Governance load.

Current blocker

Android retry reaches the current master DocumentLinkActivity, but that second window can hit an ANR before its first draw. This is outside this PR's load-state implementation, so the PR remains draft until that master behavior is fixed and the retry success path is revalidated on Android.

Scope

This PR does not change wallet signing, permissions, dAPI, the dApp catalog, or app-link navigation semantics.

[Jim8y]

Current head: 94becf3

The load-state changes are verified on both simulators:

Android offline error and retry state	iOS loading state	iOS loaded state

Android retry now survives the metadata failure and starts the existing app-link flow. The current master DocumentLinkActivity can then ANR before its first draw, so I moved this PR back to draft until that independent Android window-startup issue is fixed and the complete retry-success path is revalidated.

[Copilot]

Pull request overview

Adds explicit loading and load-failure UI states to the dApp runtime WebView so users can retry without leaving the page, and introduces new localized string resources to support the new error/retry copy.

Changes:

• Add loading overlay, load-failure overlay, and retry button to LaunchDAppPage around the dApp WebView lifecycle.
• Track dApp load state and errors in LaunchDAppPage.xaml.cs and surface them via bindings.
• Add new resource keys (DAppLoadFailed, DAppLoadFailedText, Retry) across localization files and update the generated Strings.Designer.cs.

Reviewed changes

Copilot reviewed 17 out of 18 changed files in this pull request and generated 13 comments.

Show a summary per file

File	Description
OneGateApp/Pages/LaunchDAppPage.xaml.cs	Adds loading/error/retry state management for WebView navigation and formats error copy.
OneGateApp/Pages/LaunchDAppPage.xaml	Wraps WebView with loading and error overlays and wires up retry UX.
OneGateApp/Properties/Strings.resx	Adds base (English) strings for dApp load failure and retry.
OneGateApp/Properties/Strings.Designer.cs	Adds generated strongly-typed accessors for the new string keys.
OneGateApp/Properties/Strings.de.resx	Adds localized keys for new dApp load failure UI (currently English values).
OneGateApp/Properties/Strings.es.resx	Adds localized keys for new dApp load failure UI (currently English values).
OneGateApp/Properties/Strings.fr.resx	Adds localized keys for new dApp load failure UI (currently English values).
OneGateApp/Properties/Strings.id.resx	Adds localized keys for new dApp load failure UI (currently English values).
OneGateApp/Properties/Strings.it.resx	Adds localized keys for new dApp load failure UI (currently English values).
OneGateApp/Properties/Strings.ja.resx	Adds localized keys for new dApp load failure UI (currently English values).
OneGateApp/Properties/Strings.ko.resx	Adds localized keys for new dApp load failure UI (currently English values).
OneGateApp/Properties/Strings.nl.resx	Adds localized keys for new dApp load failure UI (currently English values).
OneGateApp/Properties/Strings.pt-BR.resx	Adds localized keys for new dApp load failure UI (currently English values).
OneGateApp/Properties/Strings.ru.resx	Adds localized keys for new dApp load failure UI (currently English values).
OneGateApp/Properties/Strings.tr.resx	Adds localized keys for new dApp load failure UI (currently English values).
OneGateApp/Properties/Strings.vi.resx	Adds localized keys for new dApp load failure UI (currently English values).
OneGateApp/Properties/Strings.zh-Hans.resx	Adds Simplified Chinese strings for dApp load failure and retry.
OneGateApp/Properties/Strings.zh-Hant.resx	Adds Traditional Chinese strings for dApp load failure and retry.

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]

Review feedback fixes pushed in 9c48987.

Validation after the update:

• Android: dotnet build OneGateApp/OneGateApp.csproj -f net10.0-android -c Debug -p:AndroidSdkDirectory=/opt/homebrew/share/android-commandlinetools -p:JavaSdkDirectory=/opt/homebrew/Cellar/openjdk@17/17.0.19/libexec/openjdk.jdk/Contents/Home -p:EmbedAssembliesIntoApk=true passed with existing SQLitePCLRaw NU1903 warnings only.
• Android emulator: installed with adb install --no-incremental, launched on emulator-5554, PID 14126, AndroidRuntime crash buffer empty.
• iOS: DEVELOPER_DIR=/Applications/Xcode-26.5.0.app/Contents/Developer dotnet build OneGateApp/OneGateApp.csproj -f net10.0-ios -c Debug -p:RuntimeIdentifier=iossimulator-arm64 -p:CodesignKey=- -p:CodesignProvision= -p:ProvisioningType=automatic passed with existing SQLitePCLRaw NU1903 warnings only.
• iOS Simulator: installed and launched on iPhone 17 Pro / iOS 26.5, PID 31430.

Screenshots:

[Jim8y]

Game-load follow-up pushed in 7326d43.

What changed:

• Added a lightweight post-navigation “Preparing DApp” hint so heavy game dApps no longer look blank while their own assets continue initializing.
• On Android, in-app dApp/game launches now route through the existing Shell launch route instead of starting a separate DocumentLinkActivity; external app links and home-screen shortcuts still keep the document activity behavior.
• This removes the focus-change ANR path seen when Chromium/WebView cold-started while the previous MainActivity was being backgrounded.

Validation:

• git diff --check passed.
• Resource key parity checked: every Strings*.resx file has 292 keys.
• Android restore/build passed for net10.0-android / android-arm64 with the existing SQLitePCLRaw NU1903 warning only.
• Android emulator emulator-5554: installed, launched, opened Gaming -> Pixudi. After the fixed launch path, logcat from 06-23 12:58:46 showed no DocumentLinkActivity, no ANR, and no input-dispatch timeout. Latest /data/anr file remained the older 12:44 run.
• iOS restore/build passed for net10.0-ios / iossimulator-arm64 with the existing SQLitePCLRaw NU1903 warning only.
• iOS Simulator OneGate-PR51-iPhone17 / iOS 26.5: installed, launched, opened Gaming -> Pixudi, and verified the dApp content renders and remains stable.

Screenshots:

Android 3s:

Android 15s:

iOS 3s:

iOS 15s:

Note: Pixudi still logs an upstream AxiosError: Request failed with status code 401 from https://game.pixudi.com/. This PR fixes the OneGate container loading/Android launch-path issue, but Pixudi wallet/provider adaptation still needs a dApp-side or provider-compat follow-up.

[Jim8y]

Addressed Erik's review request in 28d3bb7.

Changes:

• Android dApp launches no longer reuse the current AppShell route.
• Android now consistently opens the OneGate app link through DocumentLinkActivity with ACTION_VIEW and NEW_DOCUMENT, so dApp/game launches use the app-link document flow.
• Kept the existing non-Android fallback behavior unchanged.
• Moved the launch-parameter helper into the non-Android branch to avoid a new Android-only unused-function warning.

Validation:

• git diff --check passed.
• Localized .resx key parity passed across all 15 resource files.
• Android build passed: dotnet build OneGateApp/OneGateApp.csproj -f net10.0-android -r android-arm64 ....
• iOS simulator build passed: dotnet restore/build OneGateApp/OneGateApp.csproj -f net10.0-ios -r iossimulator-arm64 ....

No screenshots were committed to the repository.

[Jim8y]

Addressed Erik's review feedback in 58047bc.

Change:

• Reverted the Commands.cs launch-parameter extraction that Erik asked to revert.
• The launch fallback now uses the original inline parameter construction again.

Validation:

• git diff --check passed.
• Android build passed for net10.0-android/android-arm64.
• iOS simulator build passed for net10.0-ios/iossimulator-arm64.
• Installed/launched on iOS simulator and Android emulator; screenshots captured outside the repo:
  • /tmp/onegate-review-monitor-20260705/pr67-dapp-load-state-ios.png
  • /tmp/onegate-review-monitor-20260705/pr67-dapp-load-state-android.png

Existing SQLitePCLRaw NU1903 warnings remain unrelated.

[Jim8y]

Current head already addresses the open dApp load-state feedback.

Checked in this pass:

• WebNavigationResult is shown as a numeric status code instead of a localized user-facing enum name.
• DAppLoadFailed, DAppLoadFailedText, and Retry are translated across the existing locale files.

No additional commit was needed in this pass.

[Jim8y]

Additional check for the Commands.cs review thread:

• Commands.cs no longer differs from master in this PR.
• The Android/app-link window behavior mentioned in the old review thread is not part of the current PR diff.
• I did not change this further because altering code that now matches master would conflict with the current baseline rather than only fixing this PR.

[Jim8y]

The Android document-window startup blocker is isolated in #93. That PR preserves the required app-link/new-document architecture and verifies two independent dApp windows without ANRs. This PR will remain draft until #93 is merged into master and the full Android retry-success path is revalidated against it.

[Jim8y]

Updated the branch to current master in aa8c014.

• Commands.cs remains identical to master; the previously rejected launch/navigation change is not part of this PR.
• The remaining scope is limited to dApp loading, timeout, error, preparation, and retry states.
• Removed the internal numeric navigation status from the user-facing error copy.
• Android and iOS Debug builds completed with 0 warnings and 0 errors.

Simulator validation:

• Android 16 / API 36: the app link opened a separate document task while the main OneGate task remained available; timeout/error copy rendered without an internal status code; Retry loaded Super Monkey Ball successfully.
• iPhone 17 / iOS 26.5: the loading state rendered and Super Monkey Ball completed loading successfully.
• No fatal or unhandled app exceptions were observed.

Android loading	Android loaded

iOS loading	iOS loaded

[Jim8y]

Synced this branch with current master (e2acd991) in 916fc8fa.

The LaunchDAppPage conflict was resolved by preserving both the remote-debug lifecycle from master and this PR's preparation/load cancellation behavior.

Validation:

• Android build: 0 warnings, 0 errors
• iOS simulator build: succeeded; the remaining duplicate asset warnings are the existing issue covered by Remove duplicate iOS asset inclusion #98
• Android emulator: preparation state and Super Monkey Ball load verified; process remained alive with an empty crash buffer
• iOS simulator: RetroPort loaded successfully inside OneGate

Android preparation:

Android loaded:

iOS loaded:

@erikzhang Please re-review when convenient.