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

πŸŽˆβ™»οΈ ↝ Thirdweb SDK -> "Switch network" function in thirdweb-button loop error #9

Closed
Gizmotronn opened this issue Jan 9, 2023 — with Huly for GitHub · 0 comments
Assignees
Labels
bug Something isn't working documentation Improvements or additions to documentation

Comments

Copy link
Member

Gizmotronn commented Jan 9, 2023

image (Demo screen clip taken during proposal creation).

Currently, if the user's connected and on the Polygon -> Mumbai network, their profile picture shows. However, all Lens interactions require the user to be on Polygon -> Mainnet (at least for now, in the future we'll build on top of the Lens Mumbai network as well). I've taken a look through the constants scripts and can't find anything (this could be related to the Supabase issue where the [...thirdweb].js supabase interaction wasn't working because it was forcefully connecting to the Rinkeby network: Signal-K/sytizen#16).

@Gizmotronn Gizmotronn added bug Something isn't working documentation Improvements or additions to documentation labels Jan 9, 2023
@Gizmotronn Gizmotronn self-assigned this Jan 9, 2023
Gizmotronn added a commit that referenced this issue Jan 9, 2023
…en using it

Issue: Image files aren't being sent from the client to IFPS to Lens in the protocol post
I've created a duplicate file of `useCreatePost` called `useCreatePostProposalEdit.coffee` which showcases a proposed metadata addition for tagging candidate assets as per the flow in Signal-K/Silfur#26

Here's the console output for when the post was created on the client:
https://lenster.xyz/posts/0xa952-0x06 (comment by `u/parselay.lens`)

Other related issues:
https://github.com/Signal-K/polygon/issues#:~:text=ago%20by%20Gizmotronn-,Migrate%20Proposal%20board%20from%20Vite%20to%20Next.js,-truffle%2Dganache
Signal-K/Silfur#25
Signal-K/Silfur#24
Signal-K/Silfur#22
Signal-K/Silfur#21

Discovered this issue with the thirdweb package:
Signal-K/Silfur#12
#9
Gizmotronn added a commit to Gizmotronn/comments that referenced this issue Jan 17, 2023
…cloud Supabase instance

Next step -> creating frontend component for users to update their profile information from (will merge with Signal-K/client@7d5dd61 contents later)

Signal-K/sytizen#16

More styling issues in both `/test` and the root vite app - overlapping with Signal-K/client#12 Signal-K/client#9 Signal-K/client#8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation
Projects
Status: Done
Development

No branches or pull requests

1 participant