![]() ![]() The actual sign in process hasn't changed since 2021 so we're pretty sure it's not directly related to this update. ![]() (Even if that works it doesn't rule out something blocking the communication between the browser and Cakewalk itself).Īlso, the digital signature of the application has changed since the last version so it's not impossible that if it was whitelisted before that has changed now. I'm curious if simply going to the bandlab website and trying to sign in from there is successful. The 400 HTTP error makes me wonder if something in your network (firewall, router or AV possibly) is blocking the bandlab OAUTH sign in process which requires communication with the application via a localhost port. Please note that the Early Access has now been updated to 29.09.0.062 which addresses some of the issues reported. Check your PM messages and we can try and troubleshoot further one on one. Cakewalk by BandLab: General Cakewalk by BandLab: Q&A Cakewalk by BandLab: Early. Let's take troubleshooting your issue offline. ![]() Here's the Fiddler I'm more interested in the errors displayed in the app rather than the HTTP errors. Yes I did exactly that: used the sign-in from within CbB. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |