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

isSuccess seems to never be true #560

Open
Nan0ck opened this issue Feb 8, 2025 · 2 comments
Open

isSuccess seems to never be true #560

Nan0ck opened this issue Feb 8, 2025 · 2 comments
Labels

Comments

@Nan0ck
Copy link

Nan0ck commented Feb 8, 2025

Hi guys, I have been playing with the useConnect hook, I noticed that the isSuccess variable never turns True, same with connection Status I only get idle and pending but never success; on top of that I always get undefined data

Do you guys have any insight?
I'm implementing a basic connection, calling connect() and then printing status and data just to see the result
The connection is successful tho, I get an account in the useAccount hook

@fracek fracek added the bug label Feb 9, 2025
@fracek
Copy link
Contributor

fracek commented Feb 9, 2025

Thanks for reporting this issue! Will check why that's happening and report back.

@emdevelopa
Copy link

I am excited to apply for the "Fix useConnect Hook Issue" task on OnlyDust. With my expertise in React, Next.js, and Web3 integrations, I can debug and resolve issues with the useConnect hook, ensuring proper status updates and data retrieval.

🔹 My Approach:
✅ Investigate why isSuccess and connectionStatus are not updating, checking hook behavior and state changes.
✅ Debug potential issues related to async state updates, dependencies, and reactivity.
✅ Ensure the connect() function correctly updates state and provides accurate connection data.
✅ Cross-check integration with useAccount, ensuring seamless user authentication.

🔹 Why Me?
✔ Experience in Web3 & Wallet Connections, familiar with wagmi, ethers.js, and other libraries.
✔ Strong Debugging Skills, ensuring accurate state handling in hooks.
✔ Focused on Stability & Performance, ensuring a smooth user authentication experience.

I would love the opportunity to resolve this issue effectively. Looking forward to your response!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants