Open yuyuqc opened 1 year ago
一样的问题
Same here
Same here! Was working fine a week ago but now it doesn't seem to work at all! showing "InvalidRequest: 061+8=0x22" for Bing Chat, showing "Cannot read properties of null (reading '1')" for PoeAI, & for both Waylaidwandrer & ChatGPT Azure it showing Failed to fetch!!
Please fix it! DEV!! @josStorer
Have found a solution, I will attempt to fix it tomorrow
By the way, about the Waylaidwandrer API and Azure, have you correctly configured it? "Failed to fetch" usually indicates a network issue, the default settings are not directly usable
By the way, about the Waylaidwandrer API and Azure, have you correctly configured it? "Failed to fetch" usually indicates a network issue, the default settings are not directly usable
I'm aware of it even a/f correctly configuring them shows the same though was working perfectly a week ago!
Is it fixed?
@SeasonPilot I'm working on it. To apply the solution, requests must be sent from the frontend, so the original code requires some refactoring.
问题应该还没解决吧? 刚使用bing还是报相同的错误
Fixed in e71ee74c
There are still some details to be adjusted, you can download the pre-release bundle here (https://github.com/josStorer/chatGPTBox/releases/tag/latest), I think I will submit it to the store review tomorrow.
Fixed in e71ee74
There are still some details to be adjusted, you can download the pre-release bundle here (https://github.com/josStorer/chatGPTBox/releases/tag/latest), I think I will submit it to the store review tomorrow.
pre-release bundle Requests often go unanswered
@SeasonPilot Use Ctrl+B
to call up the chat box, popup box will be fixed later
@SeasonPilot Use
Ctrl+B
to call up the chat box, popup box will be fixed later
Ctrl + B
, not Alt + B
Currently, manually inputted requests have been transferred to the foreground, while directly activated requests still remain in the background. I will fix it later.
Ctrl + B
, notAlt + B
Currently, manually inputted requests have been transferred to the foreground, while directly activated requests still remain in the background. I will fix it later.
Occasional
Haven't been submitted to the store yet! @josStorer
https://github.com/josStorer/chatGPTBox/releases/tag/v2.4.1 @Droyk Have submitted to the store review, i think will be passed in a week
@josStorer Still waiting! Haven't passed yet!
@Droyk Edge and Firefox have approved; Chrome has rejected me. I am in the process of resubmitting
@Droyk Edge and Firefox have approved; Chrome has rejected me. I am in the process of resubmitting
Still waiting! Haven't passed yet!
@josStorer Bumping!
Recently, Bing had another update, causing the previous fix to become ineffective. I'm attempting to fix it again
Still seeing this problem in 2.4.2. Removed extension, deleted extension data and reinstalled. Same problem in a private window (e.g., no other extensions) too.
@Droyk @wd5gnr Chrome Web Store has approved. I've tested and it works
bing verification is somewhat unique, so it is not available in a private window
@josStorer This is Firefox (should have mentioned that -- sorry) and reports 2.4.2 as verison number. but still same problem when using anything that starts with Bing (Web,...). I also disabled the extentions and loaded as a temp extension from the firefox.zip file in tagged for release... no go.
Error:
InvalidRequest: 061+8=0x22
HELP anybody! chat gpt web not answer - just typed me waiting... bing InvalidRequest: 061+8=0x22
i use mozilla
Chatgpt web recently added additional verification Regarding bing, it is currently temporarily unavailable on Firefox Currently, the free available mode for Firefox is Claude.ai
从8.30突然显示这个,无法使用,恳请解答