fix(suite-native): suspicious device back button removed

[PeKne]

Description

• back button removed form SuspiciousDeviceScreen as requested here

Related Issue

#16279

Screenshots:

[coderabbitai]

Walkthrough

The changes adjust the layout of a screen by modifying the component tree that renders buttons. Previously, a nested vertical container wrapped two buttons: one for contacting support and another for navigating back. The update removes the nested container and eliminates the back button entirely, leaving only the contact support button within the primary container. The handling logic for the support button remains unchanged, but users no longer have the option to navigate back from the screen.

---

🪧 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.
  • Generate unit testing code for this file.
  • 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. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• 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 src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

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

Documentation and Community

• 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 (1)

suite-native/module-onboarding/src/screens/SuspiciousDeviceScreen.tsx (1)

52-66: Remove unused back navigation logic.

Since the back button has been removed per design specs, the handleBackButtonPress function is now only used in the ScreenHeader's closeAction. Consider:

1. Moving the navigation logic directly to the closeAction prop
2. Or removing the header's close action entirely if it's not needed per design

- const handleBackButtonPress = () => {
-     if (isNoPhysicalDeviceConnected) {
-         // Exit the onboarding flow if device was disconnected while was user on this screen.
-         navigation.navigate(RootStackRoutes.AppTabs, {
-             screen: AppTabsRoutes.HomeStack,
-             params: {
-                 screen: HomeStackRoutes.Home,
-             },
-         });
-
-         return;
-     }
-
-     navigation.goBack();
- };

  return (
-     <Screen header={<ScreenHeader closeAction={handleBackButtonPress} />}>
+     <Screen>

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1516375 and 8672827.

📒 Files selected for processing (1)

• suite-native/module-onboarding/src/screens/SuspiciousDeviceScreen.tsx (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: EAS Update
• GitHub Check: Setup and Cache Dependencies
• GitHub Check: Analyze with CodeQL (javascript)
• GitHub Check: prepare_android_test_app

🔇 Additional comments (1)

suite-native/module-onboarding/src/screens/SuspiciousDeviceScreen.tsx (1)

106-112: LGTM! Changes align with design specs.

The removal of the back button and simplification of the button layout matches the PR objectives and design specifications. The contact support button is properly positioned and maintains its functionality.

[github-actions]

🚀 Expo preview is ready!

• Project → trezor-suite-preview
• Platforms → android, ios
• Scheme → trezorsuitelite
• Runtime Version → 26
• More info

Learn more about 𝝠 Expo Github Action