Closed mburger81 closed 2 months ago
I've seen the issue is happening at
await core.start({
apiKey: MORALIS_API_KEY,
});
So it doesn't even matter the nft.getWalletNFTs
call, its already failing initialising the modules.
In my opinion also the documentation from here https://docs.moralis.io/web3-data-api/advanced-sdk-setup and what I see in the README.MD
file of this project is not exactly the same. So its a little bit confusing, what is the right way to go for using the advanced sdk mode.
The documentation is talking about using @moralisweb3/core
and the readme is talking about @moralisweb3/common-core
but both examples are not working.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. for your contributions. If this issue is still affecting you, please leave any comment, and we'll keep it open We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment! Thank you.
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you!
Probably it will solve issue https://github.com/MoralisWeb3/docs/pull/476
New Bug Report
Checklist
Issue Description
Using moralis sdk instead of the Moralis monolith to fetch nfts for wallet I get the error "apiKey" is unregistered.
Steps + code to reproduce
This code snipped for Moralis SDK doesnt work
but using the monolith works fine with the expected output
I think he first part of this forum request is raising up the same type of issue https://forum.moralis.io/t/moralis-sdk-installed-from-parts-packages-errors/20353/2
Actual Outcome
Using sdk instead of monolith is running into an issue bug: SDK Core Error: [C0013] Key "apiKey" is unregistered. Have you registered all required modules?
In my opinion we are doing exactly how described from the documentation
Expected Outcome
It should work, or if we do something wrong maybe you should adapt your documentation as well
Client
macOSx
latest chrome
Logs