-
Notifications
You must be signed in to change notification settings - Fork 140
SendMessageMutation request fails starting 2 hours ago #179
Comments
i have the same bug, i guess poe change something in server. |
Seems like they might have actually lower-cased the first -SendMessageMutation
+sendMessageMutation Protocol Inspection: {
"queryName": "sendMessageMutation",
"variables": {
"chatId": null,
"bot": "claude_3_igloo",
"query": "hi again",
"source": {
"sourceType": "chat_input",
"chatInputMetadata": {
"useVoiceRecord": false
}
},
"clientNonce": "<...>",
"sdid": "<...>",
"attachments": [],
"existingMessageAttachmentsIds": [],
"shouldFetchChat": true,
"messagePointsDisplayPrice": 200
},
"extensions": {
"hash": "b5694554bb2d91d0226fed35139f1d038fdd0fa30148be02546d0e2afa3e72a4"
}
} with the hash differing from: poe-api-wrapper/poe_api_wrapper/queries.py Line 123 in 7fef481
Confirmed a change worked, making a PR now. |
The problem persists even after changing the "S" in SendMessageMutation to lowercase in the three mentioned files. |
change the hash to it fixes the problem |
It doesn't work for me. After doing this fix, I get the same error. |
Try to reinstall the package from the pull request #180 |
This is fixed in the new version. Poe's just changed some of their hashes. |
IDK what happened, I didn't change anything in my script, but all requests just started failing. Funny thing is - it returns status_code: 200 for some reason...
The text was updated successfully, but these errors were encountered: