Search for people, chatroom doesn’t work

[l-i-n-k]

Hi, it looks like I do only find people and chatrooms that I have in my recent contacts (left-hand column)
I’m unable to start a chat with someone from within Franz. I have to start the conversation in the browser (or mobile). Once the person or chat is active I can use Franz.

This is quite severe and I experience similar things in Google Mail from within Franz.

[ghost]

I have the same problem, the search user on Franz for some reason will only find users that you've already sent messages to. To open a new chat with a new user it works only on the browser.

Can we fix it?

[rflbianco]

I have bumped the same problem. A quick debug shows that the requests to chat.google.com API for autocomplete are getting a 401 (Not authorized) response.

{
  "error": {
    "code": 401,
    "message": "Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.",
    "status": "UNAUTHENTICATED"
  }
}

I have also compared autocomplete request's headers from Hangouts Chat running on Franz (401) and Chrome/Chromium (200). The only difference I have found are 2 missing entries in Franz:

• the origin: https://chat.google.com header
• the ANID=AHWqTUnZY0l5bBjS5H91GbYwY0h[hidden] cookie

Everything else seems to be the same. I'm going to debug a little bit more and try to found out why it is not "authenticated".

[rflbianco]

I have just tested and the missing header origin: https://chat.google.com is the cause of the error.

I've exported the failed request (error 401) as a cURL command, executed and it failed as expected. I added the header -H 'origin: https://chat.google.com' and got a successful response.

Now I may need some help from the guys from Franz to figure out why this header is not passed while using chats.google.com from inside the application.

[mycanaletto]

+1

[philmcmahon]

I've consistently been having this problem for a few weeks. Happy to try help if someone can point in the right direction...

[scheriam]

Somehow it seems that the Electron Client forgets about this important header for CORS - in the last weeks it worked once, but after that short period of hope, everything was like before - CORS header (Origin) not sent, Google denies list of people.

[xFeXx]

Any updates on this? Other Messengers seem to work (Rambox, Hamsket, All-in-one-messenger e.g.)
I fixed the Badges within the recipe, but CORS is still not working