search

juzeon / SydneyQt

A cross-platform desktop client for the jailbroken New Bing AI Copilot (Sydney ver.) built with Go and Wails (previously based on Python and Qt).
The Unlicense
862 stars 78 forks source link

UPDATE more error messages [BUG] bing explicit error: value: InternalError; message: Error calling extension "DeepLeo + Sydney" (deep-leo) #258

Open nefaereti opened 3 months ago

nefaereti commented 3 months ago

Checks

Hi, I tried to use Sydney QT as usual and got the following error message: bing explicit error: value: InternalError; message: Error calling extension "DeepLeo + Sydney" (deep-leo)

UPDATE: tried on new laptop and got the following errors as well:

infinite CAPTCHA detected; please resolve it manually on Bing's website or mobile client

failed to WebSocket dial: expected handshake response status code 101 but got 502

Also tried with second Pro account...still same issue

It only happens when "Classic Creative" is toggled on (I was able to get the assistant to reply without Classic Creative, but, of course, it wasn't Sydney.) Tried updating cookies, restarting the PC, etc. Nothing's worked so far. I hope this isn't a bad sign.

To Reproduce

Steps to reproduce the behavior:

  1. Go to SydneyQT with Classic Creative toggle on.
  2. Try to send a message.
  3. See error message pop up.

Expected behavior

Up until today, I have been able to converse as normal. Classic Creative always got me to Sydney. Now I can't send a message at all with Classic Creative toggled on.

Desktop (please complete the following information):

juzeon commented 3 months ago

Classic Creative needs Copilot Pro, do you have a subscription?

nefaereti commented 3 months ago

I do...and if it helps, I'm the US. I'm sorry I didn't include that info.

nefaereti commented 3 months ago

Update: Still happening, but occasionally it just stops sending without the error pop up. I hit send, I get the "scroll up" symbol that appears when you hit send, then it just disappears, message unsent. I try sending again...then get the error. I hope this isn't an issue with the endpoint no longer working. It's the only reason I still pay for Pro.

Hiro2195 commented 2 months ago

Same problem. It seems they removed the ability to use the old model. On the copilot chat bot page, there is no longer a switch between the old and new versions of creative mode.