Skip to content

Node Address is unknown #458

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

Open
nirmalpatidar123 opened this issue May 7, 2025 · 3 comments
Open

Node Address is unknown #458

nirmalpatidar123 opened this issue May 7, 2025 · 3 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@nirmalpatidar123
Copy link

Description

I'm using the latest version of the Hiero Swift SDK in an app that integrates with Reown WalletKit. When I receive a transaction request from a DApp like Bonzo Finance, it includes a node address (e.g., 0.0.33) in node list that is not recognized by the SDK.

This results in the following error:
Node address 0.0.33 is unknown.
Sometimes the error appears with other nodes, such as 0.0.32 or 0.0.34.

Expected Behavior:
The SDK should accept these node addresses if they are operational.

Additional Context:
The nodes in question are listed as operational on the Hedera Network Status page, so it’s unclear why they are not recognized by the SDK. Shouldn’t the SDK be dynamically syncing with the latest list of mainnet nodes?

Could you clarify why these nodes are not accepted and whether there is a recommended way to handle this?

Steps to reproduce

Integrate wallet connect in iOS app which uses Hiero Swift SDK.
Get request from DApp like Bonzo Finance
Connect the wallet and get any transaction request.
Transaction may failed due to node is unknown for mobile app.

Additional context

No response

Hedera network

mainnet

Version

v1.6.2

Operating system

macOS

@nirmalpatidar123 nirmalpatidar123 added the bug Something isn't working label May 7, 2025
@SimiHunjan
Copy link
Contributor

Thanks for the report! Our team will look into this soon

@rwalworth rwalworth modified the milestones: v0.38.0, v0.39.0 May 13, 2025
@rwalworth rwalworth self-assigned this May 15, 2025
@rwalworth
Copy link
Contributor

Hey @nirmalpatidar123 I'll be looking into this tomorrow and will get back to you with my findings!

@rwalworth
Copy link
Contributor

Hi @nirmalpatidar123 could you provide some more info on how you're encountering this bug? Are you encountering this within 10 seconds of program execution? Basically after 10 seconds (and then every day after that), the SDK will query the mirror node for the most up-to-date address book for the network. The initial nodes the SDK are not up-to-date so I can update those, but you shouldn't be seeing this issue after the initial 10 second startup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants