Open ohcee opened 3 months ago
This might be due to various reasons (for example missing code signing or something wrong in app manifest). I expect that building from sources should work as temporal solution.
I will try sometime later add dmg packaging for convenience (but I don't think it will help with connection issues) for reference, this flutter app seems uses code signing: https://github.com/localsend/localsend/blob/main/scripts/compile_mac_dmg.sh
@ohcee by the way, could you please check if latest veil-qt works on Apple M2
?
Judging by name it is also unsigned: veil-1.4.1.0-macos-unsigned.dmg
@steel97 Ok got it for the light wallet. I think remember this issue now.
I tried the core qt wallet the other today and it did start with M2. My mac mini M1 works with the macosx-binaries.zip
Ive been used to using that version due to the actions button, but my M2 does not work wit the .zip but it does work with the veil-1.4.1.0-macos-unsigned.dmg
I haven't had a chance to make a issue yet.
Describe the bug When trying to open a new wallet using a mac laptop, I keep getting an error about not being able to connect to the node. I'm using the newest version.
Expected behavior To enter the seed phrase and the wallet start.
Screenshots
Laptop:
Additional context Had the same problem with an M1 before. I phone version works flawlessly. Using the zip file. I'm not building it.