Thanks for reporting, Selena! Seems there may be a second way to encounter a bug with the same behavior.
We are aiming to push out a new build later today, where this work-around will no longer be needed. Given that you have already tried it, I can’t say if it will solve the problem for you. We will not rest until we have solved it for everyone though.
One last question: Are you on wifi or cellular connection? Some wifi networks (companies, schools) configure their firewalls to stop traffic through certain ports. If you are on wifi, there is a possibility that switching to cellurar would remove the block.
Is there any chance the two bugs are separately exclusive to the OS systems… the going to setting fix doesn’t work for me on the newest build either and I have an iPhone, whereas ambrose who found the work around has an Android.
The only work around I found worked for me is using the 1.9.7 build… idk I was just thinking maybe the settings fix may only work for Android.
The error is really that there is no connection established between the device and the server, and there are of course several ways to cause that to happen (no internet, selective firewall, programmatic bugs, etc). The server itself is freely accessible from the internet. The work-around takes care of one programmatic bug where an IP address was not properly initialized. That should not depend on iOS or Android. In fact, Selena is on Android, but the work-around did not solve the connection issue for her. You are on iOS and are also having some problems.
Obviously we have to find any other potential sources of this problem and remove them one after another.