Closed DartBot closed 9 years ago
Added Area-Dartium, Triaged labels.
I did some searching and found a relevant page: http://www.chromium.org/developers/how-tos/api-keys
It'd be great to fix this, as the warning that's displayed when Dartium starts up is a bit disconcerting to users. It also means that several chrome app APIs are not available because these keys are missing.
cc @ricowind. cc @mkustermann.
This comment was originally written by douglas.da...@gmail.com
Possibly related. I attempt to sign into Dartium but receive the error: "Oops sync has stopped working."
Chromium Version 31.0.1650.0 (224845) from Dart VM version: 0.8.10.3_r29803 (Mon Nov 4 07:02:37 2013) on "macos_x64"
Mac OS X Version 10.9
Re: http://www.chromium.org/developers/how-tos/api-keys, we should not be distributing chromium builds with the API keys pre-built in. Note, you can acquire your own API keys and define via env variable as suggested on the page. This does work in Dartium.
Removed this from the M8 milestone. Added this to the Later milestone.
This comment was originally written by douglas....@gmail.com
Thank you for referring me to http://www.chromium.org/developers/how-tos/api-keys. I followed its instructions setting my GOOGLE_API_KEY, GOOGLE_DEFAULT_CLIENT_ID and GOOGLE_DEFAULT_CLIENT_SECRET, respectively through my ~/.bashprofile verifying that echo $GOOGLE... outputs the expected. Yet, when I open Chromium it still provides the same warning message and I cannot sign in to Chrome to develop my Chrome-Dart apps that utilize APIs. I also filed SOO http://stackoverflow.com/questions/20022281/setting-up-google-api-keys-dartium-mac-osx. Thank you for your help.
This comment was originally written by stephan.be...@gmail.com
I have the same issue with Dartium v31. Folowed the How-To step-by-step yet it still displays the warning.
This comment was originally written by rmwels...@pediatrichomeservice.com
This issue is occurring for me also, is there an update on a possible resolution?
This comment was originally written by chenlei.bain...@gmail.com
This issue is also occurring for me! I already set my environment variables .
This comment was originally written by markhl...@gmail.com
I'm glad (well not really glad) to see others are the problem also. I've tried this a bunch of different ways, but don't have the time to do a chromium build.
The how-to is helpful, but I can't get Chromium to work for the "hello world".
This comment was originally written by vlo...@gmail.com
I followed http://www.chromium.org/developers/how-tos/api-keys 2 weeks ago with dartium 33.0.1750.48 (251129)...
And afaik, everything run fine now... I no longer have the "api key missing" warning, i can connect the dartium browser to my google account, and use google api in my dartium-chrome-apps (oAuth, Drive)...
Removed this from the Later milestone. Added Oldschool-Milestone-Later label.
This comment was originally written by jarro...@gmail.com
I'd like to see this issue fixed because it stopping me to develop my Chrome app in Dart which use chrome.identity API. But I'm must be signed in to Chromium to use this API. Any updates on this?
jarrodek: Doesn't it work if you follow the guide here: http://www.chromium.org/developers/how-tos/api-keys As Vijay says, we can't use these keys for shipping chromium based builds.
I am closing this bug since we will not be shipping such builds
Added NotPlanned label.
This issue was originally filed by lawrence...@gmail.com
What steps will reproduce the problem?
What is the expected output? What do you see instead?
I wonder what effect the "warning" message will have.
What version of the product are you using? On what operating system?