on latest Mac OS, encrypted dms via chrome/metamask give this error
Wave
6529 Desktop
Generate Summary
Choose a timeframe to see summary coverage.
Drops
-
-
@[punk6529bot] **Encrypted DM setup stalls after MetaMask sign-in on macOS (`0.1.0-rc.2`)** Sign in to Desktop with browser MetaMask, then open **Encrypted messages → Sign to enable both → Use a browser wallet**. Approve **Sign and return to 6529 Desktop**. Desktop returns to the same card with “Your wallet didn't connect.” Quitting and reopening Desktop, then retrying, worked. The browser prompt signs a login challenge. The signing connector can miss the profile’s eligibility update because Desktop saves it asynchronously without notifying the connector. Separately, the permission flow treats the Desktop picker as closed and drops the pending request after one second, even while sign-in is underway. **Proposed fix** - Have the Desktop signing connector subscribe to browser-wallet eligibility changes so it attaches after sign-in. - Keep setup pending through the browser return. Resume the permission signature when the signer for the original profile is ready. End the attempt on cancellation, expiry, or profile change. - Test a fresh MetaMask sign-in and a delayed browser return in a packaged Mac build. Encrypted DMs should activate after approving the permission signature in the same app session.
-
I have the same issue with encrypted DMs and post signing, but for me, even after restarting the desktop client it still doesnt work. I use the browser wallet option, the popup shows up and I sign it then the app says "Your wallet didn't connect. Unlock it and try again." cc @[punk6529bot]
-
-
For the Classic release: the hardening PR is merged to main in 6529-core - https://github.com/6529-Collections/6529-core/pull/307 What it changes: wallet requests from the app to a browser wallet now come only from the app, and the browser page shows what will be signed or sent (message text, typed-data fields, or a transaction's network, recipient, value and function) before Sign. It uses the existing scheme settings, so it works with whatever scheme Classic picks To test: sign a drop or vote, enable signed/encrypted messages, and try a mint via the Chrome, Firefox and Brave connectors. The details should show and the result return to the app; Cancel or a wallet rejection should show as declined; a wallet on the wrong network should get "Switch network" instead of Sign Not tested yet: macOS, Linux, a packaged build, and real wallets (checked with a test wallet on Windows). Two behaviour changes to be aware of: browser-wallet requests on Sepolia no longer complete, and smart-contract wallet signatures show as failed
-
@[punk6529] @[punk6529bot] I tried running the new 6529 Desktop (0.1.0-rc.2) alongside the original (0.4.0) on my Mac and ran into two clashes. Sort of feels like currently I can't have both on my machine: 1. App name. When I dragged the new app into Applications, macOS asked whether to replace the original or keep both. I chose Keep Both, and macOS automatically named the new copy “6529 Desktop 2.” 2. Deep links. Both apps register core6529://. When I sign in through Desktop 2’s browser connector, the browser sends the result back to the original app and Desktop 2 keeps waiting. Can we give the new app a distinct name and its own URL scheme so both versions can work side by side during the transition? OR not sure what the plan is but maybe update the 'old' Desktop app to some other name and URL scheme and keep '6529 Desktop' and 'core6529' for the new app?
-
yes this is a good idea make the existing Electron one "6529 Desktop Classic" and "Core Classic" and use the Desktop and Core for the new one @[prxt0] coordinate a release of this today with @[punk6529bot] pls
-
@[punk6529bot] let me handle this
-
Thanks, all yours. What you need from the new app's side, so the two don't collide: - New app keeps: name "6529 Desktop", macOS bundle id io.6529.desktop, link scheme core6529 (Windows: per-user install, registers core6529 under the current user) - So Classic needs its own app name, its own bundle id / Windows app id, and its own link scheme. Tell me the scheme you pick and I will add it wherever 6529.io checks desktop schemes (the browser sign-in page only accepts schemes on its list) and ship that the same day - If an existing Classic install updates itself into the renamed build, it should also give up core6529 on that machine, otherwise links keep going to it One more thing for the same Classic release: a small hardening PR for the browser-connector flow in 6529-core is being prepared now. I will link it here when it is up so it can ride along. After Classic ships I will post the tester note here and update the known-issues page.
-
I’ll use `classiccore6529://` for 6529 Desktop Classic. The new 6529 Desktop keeps `core6529://`. Classic already has its own app ID, so I’ll keep it for in-place upgrades. Classic serves its browser connector from localhost, so I’ll update the sign-in and signing callbacks in 6529-core. I’ll test the upgrade from 0.4.0 with both apps installed to make sure Classic gives up core6529:// and both schemes open the right app. I’ll also update Connect Device on 6529.io to say “6529 Desktop Classic” and open classiccore6529:// for now. Once the new Desktop supports that flow, we can update the UI again. Please share the hardening PR when it’s ready. I’ll review it before deciding whether to include it in the same release.
-
-
-
-
-
@[punk6529bot] link is broken for me
-
Sorry for the slow reply. The page and both downloads work from here right now, so I'd like to find out what differs for you. Could you tell me which link (the page 6529.io/desktop, the guide, or a download button), what you see when it fails (a 404 page, a blank page, an error from your browser), and whether you clicked it inside 6529.io or the 6529 app, or opened it in a browser tab? In the meantime, try opening https://6529.io/desktop in a new browser tab and reloading once. If you clicked it inside 6529.io, an older copy of the site that was already open may not know the new page until it reloads.
-
-
6529 Desktop 0.1.0-rc.2 is up: https://6529.io/desktop Install - Windows (64-bit): download the setup .exe from that page and run it. It is signed by 6529 Collection LLC - Mac (Apple Silicon): download the .dmg, open it, drag 6529 Desktop to Applications and open it. macOS will ask you to confirm the first time - The page lists each file's SHA-256 if you want to check your download - Step by step: https://6529.io/desktop/guide What to try first - Sign in, with a phone wallet (WalletConnect) or the wallet in your browser - Open a wave, read, post, reply - If you signed in with your browser wallet, post in a wave that asks for a signed drop and see whether the signing page in your browser makes sense - Close the app, open it again, and check you are still signed in Known issues: https://6529.io/desktop/known-issues When you report, please include: your system (Windows or Mac and its version), the app version shown in the title bar, what you did, and what happened - a screenshot helps
-
gm - the 6529 Desktop 0.1.0-rc.2 files (Windows and Mac) are signed and the download page is being set up When it is up I will post here: the link, how to install on each system, and what to try first When you try it, the most useful report is: your system (Windows or Mac and its version), the app version shown in the title bar, what you did, and what happened - a screenshot helps
-
https://6529.io/waves/da16201a-f4d0-40cf-b888-9f3a4a86a894?serialNo=1680095
-
Wave for testing the new 6529 Desktop client
Loading more drops...