Mac OS Crash Loop after Toggling Proxy Setting

[amosgroth]

Description

Downloaded Green for the very first time, installed and opened it. Before setting everything up, I wanted to make sure communication goes through Tor. Jumped to the settings menu, activated the toggle for "Proxy", the application immediately crashed and is not usable ever since. Every time I want to restart the app, the Mac OS error dialogue shows up instead, telling me to send the crash report. Makes no difference, if I click on "send" or not, the dialogue closes after the click but the application won't start so I am stuck in this loop and cannot use the application at all.

Version

1.1.6

Steps to reproduce

1. Install Green
2. Open Green
3. Go to settings
4. Toggle "Proxy" (Crash)
5. Reopen Green

Expected behaviour

• The proxy toggle should not crash the application.
• The application should reopen properly again after a crash.
• There should be a clear and human understandable error message in case of a problem/crash.

Actual behaviour

• The proxy toggle (activation) crashes the application.
• The application doesn't reopen at all after.
• There is no clear human error message.

Screenshots

Device or machine

macOS Crash Report.log

[amosgroth]

So after waiting for more than one month for a reply here, I suppose Blockstream is not willing or unable to help. Not very professional, to say the least. I'll stick to my BitBox02 and Shiftcrypto. Their device and software runs without problems at all and their support is fast, friendly, reliable and they care about their software...

[domegabri]

Hello @amosgroth, your report has been noted and the issue has been fixed upstream in the library (see Blockstream/gdk@c86946a).

We are in the middle of a larger refactor in the app, to fix a few issues including this one. We should release a new version in a week or so. Sorry for the inconvenience.

If you are still willing to give Green a try, this is how you unstuck the app from this state:

• open the settings.ini file in your data directory (which for macOS is $HOME/Library/Application\ Support/Blockstream/Green/app/
• set use_proxy to false

I hope this can help.

[domegabri]

Hello @amosgroth , this should be fixed in the latest release.

[amosgroth]

Hello @domegabri , It is still not usable for me. Now I can open green and set up Tor without a crash loop as before, but then I set up a local BTC Node as a server and after that the application is not responding anymore, showing the "loading ball" of Mac OS and not responding anymore. I can repeat that over and over again and I have to kill the app by force...

[amosgroth]

Update: Deleting all data & reinstalling doesn't help. Even with standard settings, the app freezes right after start while trying to connect to Blockstream servers...

[domegabri]

Is the node that you are connecting to running in LAN? Do you have other optiona enabled like spv?

[amosgroth]

Yes, it's in the LAN. In the UI I don't see clearly what is happening, if I am connected or not, what the problem is etc. No other option changed, no SPV.

But in the meantime I tested the Linux and the Android App. They don't crash but they don't recognize the device, neither via USB nor BT. I am giving up...

[domegabri]

If you are exposing your server through an hidden service it makes sense to use Tor. But if you are trying to connect in LAN I don't see why you should use Tor. If this is the case I can see why connection is not working. Also keep in mind that the app can connect to an electrum server, not a btc node directly.

[amosgroth]

I repeat:

• The Mac application crashes/freezes as described, no matter what configuration, also with Blockstream server standard settings (Tor activated)
• There is no clear indication for the user to see what's happening, if the application is connected or not or if there is any error
• Also it seems like you need to restart the application for changed server settings to take effect, which is not communicated nor plausible and pretty old school
• Activating Tor and connecting to a LAN server at the same time makes sense to me, the same feature works like a charm with Sparrow (described here: https://sparrowwallet.com/docs/connect-node.html#local-setup)

As said earlier, Linux and Android app don't work neither, though with a different problem (not being able to find and connect to the device).

[borgbyte]

@amosgroth can you check 1.2.0 and let us know how it goes.

[amosgroth]

@amosgroth can you check 1.2.0 and let us know how it goes.

Manjaro Linux: AppImage doesn't open, the application doesn't even start. Nothing happens. Trying to run it from terminal gives me this, nothing more:
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.

[borgbyte]

@amosgroth try #82 (comment)

[amosgroth]

@amosgroth try #82 (comment)

OK, that fix works.

• Still I have to restart the app after changing the server to my personal one. The app doesn't tell me so I have to guess.
• Also to me it's still not clear wether I am connected or not. No tooltip on the "connection" icon, no message from the application. I suppose I am connected when the wheel stops spinning. After a few minutes it seems to lose connection (icon disappears?). Tested aside with Sparrow where I get feedback and stay connected.
• Next problem: No connection of the device possible, neither with USB nor with BLE. Terminal (lsusb) tells me: Bus 003 Device 005: ID 1a86:55d4 QinHeng Electronics USB Single Serial so it is properly connected. The application doesn't show or tell me anything about it.

[amosgroth]

@amosgroth try #82 (comment)

OK, that fix works.

* Still I have to restart the app after changing the server to my personal one. The app doesn't tell me so I have to guess.

* Also to me it's still not clear wether I am connected or not. No tooltip on the "connection" icon, no message from the application. I suppose I am connected when the wheel stops spinning. After a few minutes it seems to lose connection (icon disappears?). Tested aside with Sparrow where I get feedback and stay connected.

* Next problem: No connection of the device possible, neither with USB nor with BLE. Terminal (lsusb) tells me: `Bus 003 Device 005: ID 1a86:55d4 QinHeng Electronics USB Single Serial` so it is properly connected. The application doesn't show or tell me anything about it.

Helped myself with https://help.blockstream.com/hc/en-us/articles/900005443223-Why-is-Blockstream-Jade-not-recognized-by-my-computer-

Meaning I could upgrade the firmware but still the application doesn't connect and I cannot see the balance or anything, it stays like this:

Via BLE I could connect with system tools but the application doesn't recognize the device:

[amosgroth]

@borgbyte

Heading back to Mac OS the application is still unusable. Deleted all old files and application. Installed recent green version. No difference: the application slows down the whole system, showing the spinning wheel ball and needs to be force-quitted. Also my firewall noticed initial communication attempts of green to google servers, which I don't like at all and blocked it...

[borgbyte]

@amosgroth

the application slows down the whole system, showing the spinning wheel ball and needs to be force-quitted.

please try version 1.2.3.

Via BLE I could connect with system tools but the application doesn't recognize the device:

the app does not support BLE yet.

my firewall noticed initial communication attempts of green to google servers,

some stuff is hosted on google buckets, like software update info and blog content.

[amosgroth]

@amosgroth

the application slows down the whole system, showing the spinning wheel ball and needs to be force-quitted.

please try version 1.2.3.

The application in Linux recognizes and shows the device and I could change the firmware. But the device stays "locked" and there is no prompt (neither on the device nor in the application) to actually unlock it with the given password. So nothing has changed with this version....

Via BLE I could connect with system tools but the application doesn't recognize the device:

the app does not support BLE yet.

my firewall noticed initial communication attempts of green to google servers,

some stuff is hosted on google buckets, like software update info and blog content.

As I said, I could imagine that I am not the only one that doesn't like it (the google servers connection).