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

Issue with Trust Wallet Connectivity Integration in TypeScript Code #330

Open
shubhamanandspeqto opened this issue May 16, 2024 · 1 comment

Comments

@shubhamanandspeqto
Copy link

Dear Trust Wallet Support Team,

I hope this message finds you well. I am writing to bring to your attention an issue I've encountered while integrating Trust Wallet into TypeScript code. Despite following the integration instructions meticulously, I am experiencing a redirection problem.

Description of the Issue:
When attempting to integrate Trust Wallet into our TypeScript codebase, the expected behavior is to seamlessly interact with Trust Wallet's functionalities. However, upon clicking the Trust Wallet link within our application, instead of interfacing with the Trust Wallet app, users are redirected to a download page for Trust Wallet.

Steps Taken:

  • We followed the integration guidelines provided by Trust Wallet for TypeScript.
  • We ensured that all dependencies were correctly installed and configured within our project.
  • We tested the integration thoroughly across different environments and devices to rule out any local issues.

Additional Information:

  • We are using TypeScript for our project.
  • The issue persists even after importing Trust Wallet into a Chrome extension.
  • Our team has reviewed the code multiple times to check for any misconfigurations or errors, but we couldn't identify any issues on our end.
    Request for Assistance:
    We kindly request your assistance in resolving this issue. As our application heavily relies on Trust Wallet integration, it's crucial for us to ensure seamless connectivity with your platform. Any guidance, troubleshooting steps, or insights you can provide to help rectify this issue would be greatly appreciated.

Please let us know if you require any further information or if there are specific steps we should take to diagnose the problem more effectively.

Thank you for your attention to this matter. We look forward to your prompt response and assistance.

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

No branches or pull requests

4 participants
@shubhamanandspeqto and others