We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug A clear and concise description of what the bug is.
SDK Version
To Reproduce Steps to reproduce the behavior:
🔐 [Serializer.swift]: {"id":1736308856526071,"jsonrpc":"2.0","error":{"code":1,"message":"Invalid Id"}} - decode(sealbox:symmetricKey:) - line: 152 🔐 [Serializer.swift]: keyNotFound(CodingKeys(stringValue: "method", intValue: nil), Swift.DecodingError.Context(codingPath: [], debugDescription: "No value associated with key CodingKeys(stringValue: "method", intValue: nil) ("method").", underlyingError: nil)) - handleType0Envelope(::) - line: 101 RPCResponse 🔐 [Serializer.swift]: Decoded: RPCResponse(jsonrpc: "2.0", id: Optional(1736308856526071), outcome: JSONRPC.RPCResult.error(JSONRPC.JSONRPCError(code: 1, message: "Invalid Id", data: nil))) - handleType0Envelope(::) - line: 97
Additionally on the initial connect the AppMetadata is not being passed to metamask. Metamask shows the connection as "null wants to connect".
Expected behavior Connection and socket communication between metamask and wallet connect should work.
Screenshots
Device (please complete the following information):
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
WK-473 Swift Example not working
Sorry, something went wrong.
Facing same issue with below method
try await AppKit.instance.request(.eth_sendTransaction(...))
-: ERROR :-
🔐 [Serializer.swift]: {"id":1737432118410326,"jsonrpc":"2.0","error":{"code":1,"message":"Invalid Id"}} - decode(sealbox:symmetricKey:) - line: 152 - 2025-01-21 09:32:00 🔐 [Serializer.swift]: keyNotFound(CodingKeys(stringValue: "method", intValue: nil), Swift.DecodingError.Context(codingPath: [], debugDescription: "No value associated with key CodingKeys(stringValue: "method", intValue: nil) ("method").", underlyingError: nil)) - handleType0Envelope(::) - line: 101 - 2025-01-21 09:32:00 RPCResponse 🔐 [Serializer.swift]: Decoded: RPCResponse(jsonrpc: "2.0", id: Optional(1737432118410326), outcome: JSONRPC.RPCResult.error(JSONRPC.JSONRPCError(code: 1, message: "Invalid Id", data: nil))) - handleType0Envelope(::) - line: 97 - 2025-01-21 09:32:00
No branches or pull requests
Describe the bug
A clear and concise description of what the bug is.
SDK Version
To Reproduce
Steps to reproduce the behavior:
🔐 [Serializer.swift]: Decoded: RPCResponse(jsonrpc: "2.0", id: Optional(1736308856526071), outcome: JSONRPC.RPCResult.error(JSONRPC.JSONRPCError(code: 1, message: "Invalid Id", data: nil))) - handleType0Envelope(::) - line: 97
🔐 [Serializer.swift]: {"id":1736308856526071,"jsonrpc":"2.0","error":{"code":1,"message":"Invalid Id"}} - decode(sealbox:symmetricKey:) - line: 152
🔐 [Serializer.swift]: keyNotFound(CodingKeys(stringValue: "method", intValue: nil), Swift.DecodingError.Context(codingPath: [], debugDescription: "No value associated with key CodingKeys(stringValue: "method", intValue: nil) ("method").", underlyingError: nil)) - handleType0Envelope(::) - line: 101
RPCResponse
🔐 [Serializer.swift]: Decoded: RPCResponse(jsonrpc: "2.0", id: Optional(1736308856526071), outcome: JSONRPC.RPCResult.error(JSONRPC.JSONRPCError(code: 1, message: "Invalid Id", data: nil))) - handleType0Envelope(::) - line: 97
Additionally on the initial connect the AppMetadata is not being passed to metamask. Metamask shows the connection as "null wants to connect".
Expected behavior
Connection and socket communication between metamask and wallet connect should work.
Screenshots
Device (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: