bosonprotocol / boson-dcl

Boson Protocol - Metaverse Toolkit - Decentraland SDK
Apache License 2.0
3 stars 0 forks source link

issue on production deployment - no kiosks are visible #76

Closed levalleux-ludo closed 11 months ago

levalleux-ludo commented 11 months ago

ticket 389 opened in DCL discord https://discord.com/channels/417796904760639509/1166338804349681724

I didn't make any change in the code. I've deployed the scenes 3 weeks ago and they were okay. Yesterday, I've jumped back to my land and seen there is an issue. I've checked the scene again on Catalyst and they were okay on it, but not on production. I've deployed them again on prod, and on catalyst, and same result: it's working fine on catalyst but not on production. When looking at the error, I've seen this failed request on production (GET https://realm-provider.decentraland.org/lambdas/collections/wearables-by-owner/0x1b05ba94acc29d0d66a0114a0bc7daa139153be5) followed by an error in the console: SyntaxError: Unexpected token 'N', "Not found" is not valid JSON. I don't have such errors on Catalyst and the request to the wearables runs OK. Another clew: when I say my scene is not working okay, I mean the 3D stuff is loading, but the web3 logic is not loading as it should be. A bit like if I run without ENABLE_WEB3 on the preview. So something related with the web3 provider. Sounds consistent with the error got when fetching data about the connected wallet.

levalleux-ludo commented 11 months ago

I've extracted the lines of codes causing the issue. I'm now quite sure it comes from avatar.getUserInventory() (@dcl/crypto-scene-utils v1.1.2). Here is a basic scene with the problem: https://github.com/levalleux-ludo/dcl-issue-20231024. It's deployed on catalyst https://play.decentraland.org/?CATALYST=peer-testing.decentraland.org&position=-86%2C108 where you can see it's working as expected. However the problem happens on production https://play.decentraland.org/?position=-86%2C108

levalleux-ludo commented 11 months ago

All scenes have been patched and redeploy to avoid side-effects caused by this issue.

Waiting for feedback from Decentraland team