Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Fix] Couldn't connect to Torii on IOS/Android #2726

Merged
merged 2 commits into from
Nov 26, 2024

Conversation

caillef
Copy link
Contributor

@caillef caillef commented Nov 26, 2024

I am using dojo.c on Unreal Engine 5 to make an IOS mobile app. I got a transport error issue when trying to connect to Torii.
As I already worked on the connect issue on other platforms that web, I searched for other flags that could help and stubbled upon this:
dashpay/platform#1828

I've added this flag, recompile dojo.c and not it works, my IOS app can connect to Torii 🥳

Summary by CodeRabbit

  • New Features

    • Enhanced TLS capabilities for gRPC communication through an updated tonic dependency.
  • Bug Fixes

    • No reported bugs fixed in this release.
  • Documentation

    • No new documentation changes.

Copy link

coderabbitai bot commented Nov 26, 2024

Walkthrough

Ohayo, sensei! The changes in this pull request focus on the Cargo.toml file of a Rust workspace. The primary modification involves updating the tonic dependency to include a new feature, tls-webpki-roots, which enhances its TLS capabilities for gRPC communication. The overall structure of the file remains intact, with no other alterations to workspace members or dependencies.

Changes

File Change Summary
Cargo.toml Updated tonic dependency to include tls-webpki-roots feature while retaining existing features.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Server
    participant Tonic

    Client->>Tonic: Initiate gRPC request
    Tonic->>Server: Forward request with TLS
    Server-->>Tonic: Send response
    Tonic-->>Client: Return response
Loading

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 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 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.

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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)
Cargo.toml (1)

244-244: Ohayo sensei! Consider adding documentation about mobile requirements 📝

Since this change specifically addresses mobile platform requirements, it would be valuable to document this dependency in the project's mobile setup guide or README. This will help future developers understand why this feature is necessary for mobile deployments.

Would you like me to help draft the documentation explaining the mobile TLS requirements?

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between cc82661 and 36c7fd2.

📒 Files selected for processing (1)
  • Cargo.toml (1 hunks)
🔇 Additional comments (1)
Cargo.toml (1)

244-244: Ohayo sensei! The tonic feature addition looks good! ✨

Adding the tls-webpki-roots feature to tonic is a solid solution for fixing the iOS/Android connectivity issues. This feature ensures proper TLS certificate validation on mobile platforms by using the webpki roots for certificate verification.

Let's verify if this change resolves similar issues in other mobile-related code:

✅ Verification successful

Ohayo sensei! The tonic TLS feature addition is verified and good to go! 🌟

The search results show that the TLS/certificate handling in the codebase is primarily focused on WebRTC certificates in the libp2p implementation, which is separate from the gRPC/tonic TLS configuration. The addition of tls-webpki-roots feature to tonic is an independent enhancement that specifically addresses mobile platform connectivity without conflicting with or requiring changes to other parts of the codebase.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for any mobile-specific TLS or connection handling code
rg -i "ios|android|mobile|tls|certificate" --type rust

Length of output: 1852

Copy link

codecov bot commented Nov 26, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 56.24%. Comparing base (cc82661) to head (36c7fd2).
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2726      +/-   ##
==========================================
+ Coverage   56.23%   56.24%   +0.01%     
==========================================
  Files         415      415              
  Lines       53206    53206              
==========================================
+ Hits        29922    29928       +6     
+ Misses      23284    23278       -6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Collaborator

@glihm glihm left a comment

Choose a reason for hiding this comment

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

Seems to not break anything else, let's iterate with that. 👍

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.

2 participants