Skip to content
New issue

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

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

Already on GitHub? # to your account

Reown fails in iOS if connected network is not Sepolia and tries to switch #1264

Open
juans-chainsafe opened this issue Dec 16, 2024 · 2 comments · Fixed by #1270
Open

Reown fails in iOS if connected network is not Sepolia and tries to switch #1264

juans-chainsafe opened this issue Dec 16, 2024 · 2 comments · Fixed by #1270
Assignees
Labels
Priority: P0 Added to issues and PRs relating to a critical severity bugs. Type: Bug Added to issues and PRs if they are addressing a bug

Comments

@juans-chainsafe
Copy link
Contributor

juans-chainsafe commented Dec 16, 2024

Describe the bug
If the network that you have in Metamask is not Sepolia, and you connect with Reown, it will try to switch to Sepolia but it fails

Steps
Steps to reproduce the behavior:

  1. Build in iOS
  2. Connect with Reown
  3. Connect with Metamask
  4. Sign message in Metamask
  5. Go back to Unity app
  6. It will switch you back to Metamask
  7. Nothing happens in Metamask
  8. Go back to Unity app

Expected behavior
Network is switched to Sepolia

Console errors

Web3Exception: HTTP.POST to ‘https://rpc.walletconnect.com/v1?chainId=eip155:8333&projectId=f4bff60eb260841f46b1c77588cd8acb’ responded with error: {“status”:“FAILED”,“reasons”:[{“field”:“chainId”,“description”:“We don’t support the chainId you provided: eip155:8333. See the list of supported chains here: https://docs.walletconnect.com/cloud/blockchain-api#supported-chains”}]}
 at ChainSafe.Gaming.Web3.Core.Unity.UnityHttpClient.UnityWebRequestToNetworkResponse (UnityEngine.Networking.UnityWebRequest request) [0x00000] in <00000000000000000000000000000000>:0
 at ChainSafe.Gaming.Web3.Core.Unity.UnityHttpClient+<>c__DisplayClass3_0.<PostRaw>b__0 () [0x00000] in <00000000000000000000000000000000>:0
 at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <00000000000000000000000000000000>:0
 at System.Runtime.CompilerServices.AsyncMethodBuilderCore+MoveNextRunner.Run () [0x00000] in <00000000000000000000000000000000>:0
 at IEnumeratorAwaitExtensions+InstructionWrappers+<ReturnSelf>d__2`1[T].MoveNext () [0x00000] in <00000000000000000000000000000000>:0
 at UnityEngine.SetupCoroutine.InvokeMoveNext (System.Collections.IEnumerator enumerator, System.IntPtr returnValueAddress) [0x00000] in <00000000000000000000000000000000>:0
--- End of stack trace from previous location where exception was thrown ---

Mobile (please complete the following information):

  • Chainsafe SDK version: [dev]
  • Platform: [iOS]
  • Device Type: [Real device]
  • OS Version: [latest]
@juans-chainsafe juans-chainsafe added Priority: P0 Added to issues and PRs relating to a critical severity bugs. Type: Bug Added to issues and PRs if they are addressing a bug labels Dec 16, 2024
@kantagara
Copy link
Contributor

kantagara commented Jan 8, 2025

This one is on the reown team. I'll update the dependency to their latest .NET version. it's stated that everything is fixed there in regards to that message.

@juans-chainsafe
Copy link
Contributor Author

The initial error doesn't appear anymore, but we still have the issue present with the same reproducible steps.
Now, sometimes, switches the network in Metamask, but the message "Switching the network to: Sepolia..." doesn't disappear in our app, making the user close the app and open it again.

Image

cc @kantagara

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Priority: P0 Added to issues and PRs relating to a critical severity bugs. Type: Bug Added to issues and PRs if they are addressing a bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants