I completely understand your frustration Simon but I think this is what happens in earlyaccess and this is why we are here. I’d consider going back to a production set up if this sort of occurrence tests your patience.
I only say this out of empathy, having had incredibly frustrating network issues of late that have caused me to question using Roon at all (not that it was entirely the softwares fault).
Oh, I understand what being a tester of early release software involves and some of the potential pitfalls and issues.
My comment was based on this, in that the recent user experience/customer journey undertaken following the SSO Logout test, is not yet ready for the general/non earlier-access Roon user, as they have a different expectation level of ‘release software’ and a much much shorter tolerance level of shortcomings & issues.
There will be much weeping and gnashing of teeth, and then they will come with their pitchforks
Don’t bring this back to me - providing Payment solutions to companies in Africa, there has been a case, in Ghana, where one of our customers had payments owed to consumers but there was a technical issue with disbursing the funds to the individuals, there was a physical storming of the customer’s offices looking for their monies owed, the pitchforks were real and actual!
I was envisioning them in the metaphorical sense…with harsh words being as far as it went.
After updating to the latest beta version, the app launched correctly and I was able to log into my account
@Ivan: Curious! I had tried occasionally to see if anything changed with launching in past days, but I got stuck every time at the black screen. As you now released the SSO stuff, I assumed that you don’t need my black screen startup logs anymore, so I went to reset my ARC app now, and launched it to do so - and suddenly it worked! On the first launch it got stuck on the Core choice screen after clicking the button for my (only) Core, but after a force quit and relaunch, everything is back and works. Yay, no re-downloading! Thanks!
Yes, @Suedkiez, thank you for the assistance. I think we figure out the way how to reproduce this locally now. Going to be fixed some time soon.
Thanks!
–
Ivan
Just to clarify, I did not have to reset the app, it worked when I started it to do so
Yup, I got it. That’s the behaviour we’ve been observing so far but not consistetnly…
Thanks!
–
Ivan
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.