-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dialogues still not working #6
Comments
I just checked it and it still works for me. "Http status code is none" means that some basic HTTP thing fails, like the stuff that the win7fix tries to solve. Some ideas:
If none of these points help you, maybe you can record a video of you using it and the problem occuring? I don't know what else it could be, based on your description. |
It's possible that the Ubisoft server does not respond within time, maybe because it's trying to do things that it needs to wait for. Debugging this without having the problem yourself is pretty tricky. As a workaround you may be able to delete/close the chat and start a new one. Do you have multiple chats where you can try this out? You can also create a group for this. Even though one chat may fail, the others should continue working after that. Maybe it also has something to do with companies stopping service in Russia. Unlikely, as you mention that the previous requests work. Maybe some requests get blocked/timed out by Russian ISPs. Maybe your internet connection is just spotty. No idea.
|
It is unlikely that the case in the country. I play rainbow 6 with my friends. Everything works fine for them, they are all on Windows 10. And after the last update, I had these problems with Ubisoft Connect. Moreover, thanks to your fix, I can play with them, the main thing is that they send an invitation via chat with the first message =) So the fix still works for me, although if it were stable it would be more convenient. Sometimes I have to break parties and at the same time I have to restart everything. But this is not critical, thank you very much for the fix!
Launcher log:
|
I'm happy that the fix helps you! I want to make it as stable as possible, but you may need to help me. Do the requests always stop working after 18? After some minutes? Are you doing something that could cause it to break, opening a game, opening the overlay or something like that? Please test this: Use the fix as before, but when it stops working, just restart the fix (should cause the "(un)install root certificate popup" when closing, and then again when opening again). See if it does work again please. As I cannot reproduce the error myself, yet the next step will be to include some more output in the win7fix. I will upload a modified version that will log what&when data is sent and what&when is received. Maybe it's really only due to the Ubisoft server responding very slowly, or maybe there is a bug in the win7fix. If the problem is due to the Ubisoft server, I don't think that I can do much about it. I will post it here once I have a new version for you to try out. |
Faced yesterday with a problem that ubisoft connect does not work. I checked the logs and found this entry:
[11020] 2022-03-12 23:14:36 [10180] ERROR ChannelsGet.cpp (101) Get channels failed: 0; Response [11020] 2022-03-12 23:14:36 [10180] ERROR JobHttp.cpp (153) Http status code is none for url https://channel-service.upc.ubi.com/v1/profiles/me/channels?membershipType=ACTIVE&spaceId=c0539e9c-90ab-4af8-a2d6-ef7b3883f430. [11020] 2022-03-12 23:14:36 [10180] ERROR ChannelsGet.cpp (101) Get channels failed: 0; Response:
Using your fix allows me to open the chat, but only the history of the first opened dialogue is loaded in it. To see the history of the next dialog, i have to restart ubisoft connect. i can only send messages to the first opened dialog. In other dialogs, messages are not sent. And in-game overlay is not working. =(
Ubisoft doesn't seem to care at all about this issue, as I've seen reports of such errors dating back to 2017. Maybe you can help me with advice on what I can do?
The text was updated successfully, but these errors were encountered: