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

[BUG] fcl v1.11.0 Quicknode Invoke bug #1916

Open
btspoony opened this issue Jul 10, 2024 · 2 comments
Open

[BUG] fcl v1.11.0 Quicknode Invoke bug #1916

btspoony opened this issue Jul 10, 2024 · 2 comments
Assignees
Labels
Bug Something isn't working

Comments

@btspoony
Copy link
Contributor

btspoony commented Jul 10, 2024

Current Behavior

When using fcl v1.11.0 to call the getAccount function on Quicknode's Flow AN endpoint, it will throw a 404 NotFound error (from Quicknode).
Rolling back to version v1.10.0 of fcl resolves the issue.

--

If you use the flow public AN Endpoint, everything works.

Expected Behavior

fix the problem。
The use of Quicknode's nodes and public nodes should have the same effect.

Steps To Reproduce

set config "accessNode.api" with quicknode endpoint.

Environment

What are you currently working on that this is blocking?

No response

@btspoony btspoony added the Bug Something isn't working label Jul 10, 2024
@jribbink jribbink self-assigned this Jul 10, 2024
@jribbink
Copy link
Contributor

Hey @btspoony, thanks for creating an issue - I had made a PR introduced in FCL v1.11.0 that was supposed to address issues with QuickNode in v1.10.0 https://github.com/onflow/fcl-js/pull/1882/files.

Can you share the specific accessNode.api configuration so it is easier for me to reproduce (e.g. things like http/https protocol, path components, trailing slashes) could be a part of this issue so this would be really helpful.

@btspoony
Copy link
Contributor Author

It is:
https://{appId}.flow-mainnet.quiknode.pro/{accessKey}/

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
Status: 🔖 Ready for Pickup
Development

No branches or pull requests

2 participants