[Bug] Public vs. logged in state for previously visited servers is buggy

[psobolewskiPhD]

If I make a new server (via Browser servers) and leave Enable logging in as Public checked, just Connect and Browse, everything that is public is correct and I can access images.

BUT
If I then go to Manage servers and log in, browse becomes a to a bugged state:
I end up showing as logged in but getting the All groups All members view, like public would, but without access to any images. And looking at my user group, basically everything is , I can't even see myself.
(this is contrary to how it works just using the web interface when first connecting as public and then logging in)
This persists even when restarting QuPath: using Manger servers -> connect yields a working Public interface, but clicking log in gives a bugged state where I can't access images.

However
If I start over and make a new server, uncheck allow Enable Public, then I get asked to authenticate and when I browse then I see things mostly correct and can switch between web and ICE (although I'm not sure what that ICE is showing, given our split servers, see #1 (comment) )

Now I get a lot of for members of groups that I cannot see on the actual web interface, which makes navigating the things I can use a bit annoying, but everything seems to be logged in properly.

BUT
If I then reconnect--using Manage servers--it looks like the Public setting here also isn't honored (as noted #4 ), even if I don't click Browse but go right to log in. SO after I authenticate and hit browse I'm directly in the bugged state as above where I cannot access anything.
And again, restarting QuPath doesn't change it.

[Rylern]

Thanks, it should have been addressed in the v0.1.0-rc2 release. Can you see if that version fixes the issue?

[psobolewskiPhD]

Yup, I cannot reproduce the issue, I think it's fixed.