Stuck on deploying Chrome Remote Desktop on Windows

[Phane Vagonette]

Hello dear coders,

Yesterday I started a quest following this guide: 

https://chromium.googlesource.com/chromium/src/+/master/docs/chromoting_build_instructions.md

I'm trying to build Chrome Remote Desktop host and the webapp from source, on a Windows 7 x64 machine.

I managed to build everything: service installer, shared lib, executables and the extension.

After loading the extension into the browser and starting it, it opens a tab in the browser: "chrome://chrome-signin/?source=5"

Logging in does not redirect me to the consent prompt, and it just takes me back to the login screen again, like the login never happened. (so I guess something is bad and I get logged out automatically)

The logs produced by the chrome extension:

Chromoting version: 48.0.2534.0 (v2)

console_wrapper.js:115 Native Message port disconnected host_daemon_facade.js:221remoting.ConsoleWrapper.recordAndLog_ @ console_wrapper.js:115

host_controller.js:27 Host version not available.

ui_mode.js:122 App mode: home

console_wrapper.js:115 Native Message port disconnected host_daemon_facade.js:221remoting.ConsoleWrapper.recordAndLog_ @ console_wrapper.js:115

crd_main.js:130 Pairing registry not supported by host.

extensions::lastError:133 Unchecked runtime.lastError while running identity.getAuthToken: OAuth2 request failed: Service responded with error: 'bad client id: {0}'

    at remoting.Identity.getToken (chrome-extension://ljacajndfccfgnfohlgkdphmbnpkjflk/identity.js:77:21)

    at remoting.Application.start (chrome-extension://ljacajndfccfgnfohlgkdphmbnpkjflk/application.js:68:21)

    at Object.remoting.startDesktopRemoting (chrome-extension://ljacajndfccfgnfohlgkdphmbnpkjflk/crd_main.js:182:16)

    at remoting.startDesktopRemotingForTesting (chrome-extension://ljacajndfccfgnfohlgkdphmbnpkjflk/crd_main.js:158:14)

I checked the OAuth2 client id and client id secret.

I set them as environment variables before building.

I also defined them in 'src/google_apis/google_api_keys.cc" as I found hinted in this document: https://docs.google.com/document/d/184niJVxEfBoYqOrL_BLIHR8PNTbvCnGcFy3Rwb7NbPU/edit

Now, I realize there is hard to guess what the problem is, but any hints/opinions will be valuable.

This is my first contact with the chromium trunk and the build tools used by it, so I might have confused things.

Besides this,

What's the 'source' parameter for the page "chrome://chrome-signin" ?

How can I check that the OAuth2 credential is correct and works ?

I tried with both Chrome and Chromium, having the same result.

If I'm using my own OAuth2 credential for the extension, do I have to rebuild Chromium too ? (My guess was no, but better safe than sorry)

All documents I've read so far failed to make me understand why do I need the API key and how to use it. The links I pasted above don't mention creating one, but use one when setting up ~/.gyp/include.gypi.

Is the Chromoting API = Chrome Remote Desktop API ?

Sorry for the long post,

Potato!

Best of wishes

PS: Of course, any other info you might need, I'll be close. Also, if you want to build this on windows yourself and get stuck, I'll be close.

[Antony Sargent]

You might have better luck posting this question on chromi...@chromium.org instead of chromium-...@chromium.org

--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To post to this group, send email to chromium-...@chromium.org.
Visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/04649c41-b75a-4693-9bbd-6f5551e656da%40chromium.org.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.