Envoy v1.8.5 Not Launching

Brewse · December 5, 2024, 4:45pm

Sometime subsequent to updating to v1.8.5 (on iPhone 16 Pro running iOS 18.2 public beta 22C5142a), I started noticing that Envoy often (seemingly always, now) does not launch correctly.

The symptom is that the app launches, but becomes completely blurred out. It still appears to be the Envoy app (white background, black borders) but nothing is readable (no indication of accounts) and is completely non-responsive.

This often (always?) occurs when there is an error at startup (failure to backup, and/or failure to connect to my node.

The workaround is to terminate the app and re-launch. This works every time, even though I often see the same errors to backup/connect after that re-start (so my connection errors are presumably a separate issue, but possibly contributing factor to blurring/non-responsive behavior).

Has anyone else seen this?

qna · December 5, 2024, 5:06pm

Hey @Brewse,

Are you able to share a screen recording of this happening as well as your Envoy logs please?

In the interest of us trying to replicate the issue, could you also confirm:

Are you using Tor (better privacy)?
What type of node are you connecting to?
Are you using an application lock? If so, which type?

Thanks

Brewse · December 5, 2024, 6:17pm

Thank you for your response.

I have never made a screen recording, so it may take me a little while to respond with that.

I am using Tor to connect to an Umbrel node running Bitcoin Core 27.1.0 and Electrs 0.10.2. This setup does often work as intended.

Envoy is unlocked via Face ID. Envoy is allowed access to Local Network, Camera, Face ID, Background App Refresh, and Cellular Data.

I just launched Envoy and experienced the blurring problem, and noticed two things: 1) the accounts (a mobile wallet, and 2 accounts associated with a Passport) DID appear in the blur (the colored rectangles were there - so I described it incorrectly in my first message, and
2) the blur only lasted one or two seconds this time, followed by Face ID animations, then Envoy was fully functional.

Typically, I do not launch Envoy every day. Today I had used it a bit before my initial message on this forum.

Is it possible that a long time between uses would cause a longer delay before Envoy is ready to go? (and if I were just more patient, the situation would resolve itself without a re-start?)

The connectivity issues with Tor usually resolve themselves (the red shield shape at the top of the screen turns teal colored a few moments after launch).

Based on my most recent experience today, I would not be surprised if the issue is outside Envoy. A delay/hiccup in getting Face ID to run and return authorization.

The contents of my log is below (apologies if there is a way to attach a file, i don’t see a way to do that). I removed the tcp links because I am paranoid - hope they are not important.

Time : 2024-12-05T12:52:11.326621
Category : wallet
Message : Couldn’t sync: Exception: Couldn’t sync to: Network.Mainnet (tcp:// .onion:50001)
Library : None
Exception : None
Stack Trace : None

Time : 2024-12-05T12:52:11.360057
Category : tor
Message : Both Electrum and NGU unreachable through Tor
Library : None
Exception : None
Stack Trace : None

Time : 2024-12-05T12:52:11.360062
Category : wallet
Message : Couldn’t sync: Exception: Couldn’t sync to: Network.Mainnet (tcp:// .onion:50001)
Library : None
Exception : None
Stack Trace : None

Time : 2024-12-05T12:52:11.401338
Category : tor
Message : Both Electrum and NGU unreachable through Tor
Library : None
Exception : None
Stack Trace : None

Time : 2024-12-05T12:52:11.401343
Category : wallet
Message : Couldn’t sync: Exception: Couldn’t sync to: Network.Mainnet (tcp:// .onion:50001)
Library : None
Exception : None
Stack Trace : None

Time : 2024-12-05T12:52:11.489811
Category : tor
Message : Both Electrum and NGU unreachable through Tor
Library : None
Exception : None
Stack Trace : None

Time : 2024-12-05T12:52:11.489815
Category : wallet
Message : Couldn’t sync: Exception: Couldn’t sync to: Network.Mainnet (tcp:// .onion:50001)
Library : None
Exception : None
Stack Trace : None

Time : 2024-12-05T12:52:11.490251
Category : tor
Message : Both Electrum and NGU unreachable through Tor
Library : None
Exception : None
Stack Trace : None

Time : 2024-12-05T12:52:11.490252
Category : wallet
Message : Couldn’t sync: Exception: Couldn’t sync to: Network.Mainnet (tcp:// .onion:50001)
Library : None
Exception : None
Stack Trace : None

Time : 2024-12-05T12:52:11.503113
Category : tor
Message : Both Electrum and NGU unreachable through Tor
Library : None
Exception : None
Stack Trace : None

Time : 2024-12-05T12:52:11.503115
Category : wallet
Message : Couldn’t sync: Exception: Couldn’t sync to: Network.Mainnet (tcp:// .onion:50001)
Library : None
Exception : None
Stack Trace : None

Time : 2024-12-05T12:52:11.515421
Category : tor
Message : Both Electrum and NGU unreachable through Tor
Library : None
Exception : None
Stack Trace : None

Time : 2024-12-05T12:52:11.515423
Category : wallet
Message : Couldn’t sync: Exception: Couldn’t sync to: Network.Mainnet (tcp:// .onion:50001)
Library : None
Exception : None
Stack Trace : None

Time : 2024-12-05T12:52:11.603037
Category : tor
Message : Both Electrum and NGU unreachable through Tor
Library : None
Exception : None
Stack Trace : None

Time : 2024-12-05T12:52:11.603047
Category : connectivity
Message : TimeoutException: Timed out
Library : None
Exception : None
Stack Trace : None

Time : 2024-12-05T12:52:11.605336
Category : tor
Message : Both Electrum and NGU unreachable through Tor
Library : None
Exception : None
Stack Trace : None

Time : 2024-12-05T12:52:11.605338
Category : wallet
Message : Couldn’t sync: Exception: Couldn’t sync to: Network.Mainnet (tcp:// .onion:50001)
Library : None
Exception : None
Stack Trace : None

Time : 2024-12-05T12:52:11.605891
Category : tor
Message : Both Electrum and NGU unreachable through Tor
Library : None
Exception : None
Stack Trace : None

Time : 2024-12-05T12:52:11.605892
Category : wallet
Message : Couldn’t sync: Exception: Couldn’t sync to: Network.Mainnet (tcp:// .onion:50001)
Library : None
Exception : None
Stack Trace : None

Time : 2024-12-05T12:52:21.115702
Category : tor
Message : Both Electrum and NGU unreachable through Tor
Library : None
Exception : None
Stack Trace : None

Time : 2024-12-05T12:52:21.115724
Category : connectivity
Message : TimeoutException: Timed out
Library : None
Exception : None
Stack Trace : None

Time : 2024-12-05T12:52:21.116830
Category : tor
Message : Both Electrum and NGU unreachable through Tor
Library : None
Exception : None
Stack Trace : None

Time : 2024-12-05T12:52:21.116835
Category : wallet
Message : Couldn’t sync: Exception: Couldn’t sync to: Network.Mainnet (tcp:// .onion:50001)
Library : None
Exception : None
Stack Trace : None

Time : 2024-12-05T12:53:06.885425
Category : connectivity
Message : TimeoutException: Timed out
Library : None
Exception : None
Stack Trace : None

Time : 2024-12-05T12:53:32.097138
Category : connectivity
Message : TimeoutException: Timed out
Library : None
Exception : None
Stack Trace : None

qna · December 6, 2024, 5:52am

Thanks again for the detailed info, it really does make troubleshooting this kind of stuff much quicker.

Based on what your recent developments, combined with the contents of your logs (nothing in there to worry about) and the fact you’re running iOS beta software, I’m inclined to agree with your assumption that "I would not be surprised if the issue is outside Envoy. A delay/hiccup in getting Face ID to run and return authorization."

But with that said, I’d still be intrigued to see a screen recording of this phenomenon. Your explanations are pretty detailed, but there’s nothing quite like seeing it with your own eyes. If you’re unsure how to do that, see here.

Brewse · December 15, 2024, 1:54am

Apologies for my long delay in responding.

Thank you for your thoughts and the pointer on how to make a screen recording.

My iPhone is now running iOS 18.2 (22C152), and has not exhibited the frozen blurry screen issue since (though I have recorded the screen during recent launches of Envoy, so if it occurs I may yet capture it.

I do believe the issue was caused by factors outside Envoy, such as failure of FaceID to respond with authentication (or failure to authenticate).

qna · December 15, 2024, 6:28am

Thanks for circling back. Let us know if you have any issues in the future.