feat: handle redirect uri when on unsupported browsers

[kushagrasarathe]

• fixes TASK-13323 : redirect uri when copying from a unsupported browser
• also fixes confirm bank claim view ui for iban claims made by guest users

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
peanut-wallet	Ready	Preview	Comment	Aug 21, 2025 9:14am

[notion-workspace]

🪲 Bug: copy link in not supported browsers is the incorrect link

[coderabbitai]

Walkthrough

Start/setup navigation now preserves current claim context by appending a redirect_uri built from the current URL. UnsupportedBrowserModal was refactored to render content inside a Suspense boundary and uses Next.js search params for redirect_uri-aware copy behavior. DynamicBankAccountForm alters the second argument passed to onSuccess for IBAN flows.

Changes

Cohort / File(s)	Summary of changes
Setup redirect with context src/components/Claim/Link/Initial.view.tsx, src/components/Common/ActionList.tsx	Replace direct router.push('/setup') with router.push('/setup?redirect_uri=<encoded current URL>') where redirect_uri = encodeURIComponent(pathname + search + hash); keep saveRedirectUrl() and add clarifying comments.
UnsupportedBrowserModal refactor & query handling src/components/Global/UnsupportedBrowserModal/index.tsx	Move modal logic into UnsupportedBrowserModalContent, export wrapper UnsupportedBrowserModal that renders content inside Suspense; use useSearchParams() to read redirect_uri; copy-to-clipboard prefers origin + decoded(redirect_uri) else current URL; add error handling and import Suspense. Public wrapper signature changed to accept props and delegate to content.
IBAN/BIC rawData change on submit src/components/AddWithdraw/DynamicBankAccountForm.tsx	On submit, second argument passed to onSuccess now explicitly sets accountNumber: '' when isIban is true and ensures bic is included (spreading other fields); primary payload (first arg) unchanged.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

Possibly related PRs

• fix: bic fetching #1050 — Related changes to DynamicBankAccountForm handling of BIC/IBAN in submission payloads.
• prod to staging #1092 — Related refactor/usage of UnsupportedBrowserModal in pages and modal behavior.
• Feat/claimflow #772 — Related edits to claim link/CTA navigation and setup redirect flow in Initial.view.

Suggested reviewers

• jjramirezn
• Zishan-7

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 442fb39 and 5b2519e.

📒 Files selected for processing (1)

• src/components/AddWithdraw/DynamicBankAccountForm.tsx (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

📓 Common learnings

Learnt from: Zishan-7
PR: peanutprotocol/peanut-ui#1072
File: src/app/(setup)/setup/page.tsx:173-175
Timestamp: 2025-08-07T12:53:50.946Z
Learning: In the peanut-ui setup flow at `src/app/(setup)/setup/page.tsx`, when handling unsupported scenarios, both device not supported and browser not supported cases should show the same "Unsupported browser" message using the `UnsupportedBrowserModal` component, rather than having distinct messaging for each scenario.

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Deploy-Preview

🔇 Additional comments (1)

src/components/AddWithdraw/DynamicBankAccountForm.tsx (1)

154-155: LGTM! Proper data transformation for IBAN flows.

The explicit field assignments correctly transform the raw data for IBAN flows by clearing the account number and ensuring the BIC field is properly set. This maintains data consistency between the payload and raw data structures passed to onSuccess.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/redirect-url

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (3)

src/components/Common/ActionList.tsx (1)

116-120: Preserving flow context via redirect_uri is correct; consider minor hardening and reuse.

• LGTM on intent and placement (inside an onClick in a client component).
• Small nit: prefer URLSearchParams to build the query string to avoid accidental encoding mistakes.
• This logic is duplicated in src/components/Claim/Link/Initial.view.tsx; consider extracting a tiny helper to keep behavior consistent.

Apply this minimal diff:

-// push to setup page with redirect uri, to prevent the user from losing the flow context
-const redirectUri = encodeURIComponent(
-    window.location.pathname + window.location.search + window.location.hash
-)
-router.push(`/setup?redirect_uri=${redirectUri}`)
+// push to setup page with redirect uri, to prevent the user from losing the flow context
+const redirectUri = encodeURIComponent(location.pathname + location.search + location.hash)
+const params = new URLSearchParams({ redirect_uri: redirectUri })
+router.push(`/setup?${params.toString()}`)

Optionally, I can factor this into a reusable utility (e.g., utils/navigation.ts: navigateToSetupWithRedirect(router)). Want me to open a follow-up PR?

src/components/Claim/Link/Initial.view.tsx (1)

779-784: Good consistency with ActionList; suggest the same minor hardening and reuse.

• The redirect handling mirrors ActionList and looks correct.
• Use URLSearchParams for safety and consider extracting a shared helper to avoid drift between call sites.

Apply this minimal diff:

-// push to setup page with redirect uri, to prevent the user from losing their claim context
-const redirectUri = encodeURIComponent(
-    window.location.pathname + window.location.search + window.location.hash
-)
-router.push(`/setup?redirect_uri=${redirectUri}`)
+// push to setup page with redirect uri, to prevent the user from losing their claim context
+const redirectUri = encodeURIComponent(location.pathname + location.search + location.hash)
+const params = new URLSearchParams({ redirect_uri: redirectUri })
+router.push(`/setup?${params.toString()}`)

If you’d like, I can add a small helper like navigateToSetupWithRedirect(router) and update both call sites.

src/components/Global/UnsupportedBrowserModal/index.tsx (1)

90-96: Sanitize and normalize redirect_uri before composing the copy URL.

Current logic works given our producers only ever set redirect_uri to path+query+hash. For extra robustness:

• Ensure it starts with “/” to avoid oddities if a query constructs a relative path.
• Construct the final URL via the URL constructor rather than string concat.

-// copy the redirect uri if it exists, otherwise copy the current url
-const redirectUri = searchParams.get('redirect_uri')
-const urlToCopy = redirectUri
-    ? `${window.location.origin}${decodeURIComponent(redirectUri)}`
-    : window.location.href
-await copyTextToClipboardWithFallback(urlToCopy)
+// copy the redirect uri if it exists, otherwise copy the current url
+const redirectUri = searchParams.get('redirect_uri')
+let urlToCopy = window.location.href
+if (redirectUri) {
+    try {
+        const decoded = decodeURIComponent(redirectUri)
+        const path = decoded.startsWith('/') ? decoded : `/${decoded}`
+        urlToCopy = new URL(path, window.location.origin).href
+    } catch {
+        // silently fall back to the current URL
+    }
+}
+await copyTextToClipboardWithFallback(urlToCopy)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 46200bf and 442fb39.

📒 Files selected for processing (3)

• src/components/Claim/Link/Initial.view.tsx (1 hunks)
• src/components/Common/ActionList.tsx (1 hunks)
• src/components/Global/UnsupportedBrowserModal/index.tsx (4 hunks)

🧰 Additional context used

🧠 Learnings (4)

📓 Common learnings

Learnt from: Zishan-7
PR: peanutprotocol/peanut-ui#1072
File: src/app/(setup)/setup/page.tsx:173-175
Timestamp: 2025-08-07T12:53:50.946Z
Learning: In the peanut-ui setup flow at `src/app/(setup)/setup/page.tsx`, when handling unsupported scenarios, both device not supported and browser not supported cases should show the same "Unsupported browser" message using the `UnsupportedBrowserModal` component, rather than having distinct messaging for each scenario.

📚 Learning: 2025-08-12T17:44:04.268Z

Learnt from: Zishan-7
PR: peanutprotocol/peanut-ui#1089
File: src/components/LandingPage/dropLink.tsx:35-42
Timestamp: 2025-08-12T17:44:04.268Z
Learning: In the Peanut UI project, opening the `/setup` route in a new tab from landing page CTAs is intentional design behavior to keep users on the marketing page while they start the setup process.

Applied to files:

• src/components/Common/ActionList.tsx
• src/components/Claim/Link/Initial.view.tsx

📚 Learning: 2025-07-24T13:26:10.290Z

Learnt from: Hugo0
PR: peanutprotocol/peanut-ui#1014
File: src/components/Claim/Link/Initial.view.tsx:413-413
Timestamp: 2025-07-24T13:26:10.290Z
Learning: In the peanut-ui repository, the change from `${SQUID_API_URL}/route` to `${SQUID_API_URL}/v2/route` in src/components/Claim/Link/Initial.view.tsx was a typo fix, not an API migration, as the codebase was already using Squid API v2.

Applied to files:

• src/components/Claim/Link/Initial.view.tsx

📚 Learning: 2025-08-07T12:53:50.946Z

Learnt from: Zishan-7
PR: peanutprotocol/peanut-ui#1072
File: src/app/(setup)/setup/page.tsx:173-175
Timestamp: 2025-08-07T12:53:50.946Z
Learning: In the peanut-ui setup flow at `src/app/(setup)/setup/page.tsx`, when handling unsupported scenarios, both device not supported and browser not supported cases should show the same "Unsupported browser" message using the `UnsupportedBrowserModal` component, rather than having distinct messaging for each scenario.

Applied to files:

• src/components/Global/UnsupportedBrowserModal/index.tsx

🧬 Code graph analysis (1)

src/components/Global/UnsupportedBrowserModal/index.tsx (1)

src/utils/general.utils.ts (1)

• copyTextToClipboardWithFallback (409-435)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Deploy-Preview

🔇 Additional comments (2)

src/components/Global/UnsupportedBrowserModal/index.tsx (2)

38-46: Refactor to Content component + useSearchParams is sound.

Wrapping the searchParam-driven content in a Suspense-aware inner component is a clean way to avoid hydration issues. The public export remains a default component that accepts the same prop names, so no breaking JSX usage expected.

---

134-141: All unsupported flows now route through the unified modal

• In src/app/(setup)/setup/page.tsx, both showBrowserNotSupportedModal and showDeviceNotSupportedModal flags immediately return a single <UnsupportedBrowserModal visible allowClose={false} /> instance, satisfying the “one modal for all unsupported scenarios” requirement.
• No other bespoke “device not supported” or “browser not supported” messaging exists elsewhere in the src/ tree.
• Parameter names are consistent—only redirect_uri is used (no redirect_url occurrences).