Closed GoogleCodeExporter closed 9 years ago
Same problem.
I have a Google Apps for My Domain Account.
This is the primary account that I use on my Nexus One.
Build number is FRF83.
In Chrome, I have successfully installed the chrome-to-phone extension and
associated it with my GAFMD account. Icon appears on toolbar.
On my Nexus One, I've installed the app, but it will not register using my same
account. If I use a standard GMail account, the device registers.
I would expect to be able to register a device using a Google Apps for My
Domain account since this is what I am using on my phone and when browsing on
the desktop.
Gmail, Calendar, Talk on my phone all without any issue.
Original comment by eric%car...@gtempaccount.com
on 25 Jun 2010 at 6:41
I have added chrometophone as a registered app on my domain as well and this
does not have any effect. I would imagine that the codebase needs to be
modified to allow specifying a specific apps for domains domain name both
client side and extension side.
Original comment by tony%cha...@gtempaccount.com
on 5 Jul 2010 at 11:19
I have tried this as well and whilst all works in my browser I cannot get it to
register against my Google Apps Premier account. It works just fine though when
tied to a regular old Google account that I have on my Nexus 1 for Google
checkout purposes. (as this doesn't work with my GAPE account either...)
Sometimes paying for something renders you a second class customer I guess. I
will be glad when the GAPE accounts get fully integrated with other mainstream
google apps.
Original comment by mthurman...@gmail.com
on 7 Jul 2010 at 11:51
I can't either login to the chrome extension!
It says: "Chrome to Phone requires you to login.", when I click and try to
enter with my user@domain account, it doesn't recognize me.
Original comment by gee.m1ckey@gmail.com
on 12 Jul 2010 at 7:56
Dito...Hopefully if this is related to the google apps (GAFYD) vs google
account issue, the 'just around the corner' improvements may resolve this issue?
Original comment by adr...@higstar.com
on 13 Jul 2010 at 7:56
AppEngine doesn't support Google Apps accounts. When it does, so will CTP.
Original comment by burke.da...@gmail.com
on 13 Jul 2010 at 11:29
Same issue here, i am using the htc desire with froyo and there are too many
google apps that you can't work with using a google apps account. Unbelievable.
Original comment by sherlock...@gtempaccount.com
on 5 Aug 2010 at 8:21
@Sherl@2puntnul.nl
...It's AppEngines fault, not the application developers though!
Original comment by chilling...@gmail.com
on 5 Aug 2010 at 9:18
Google App Engine has an URL [1] on its page [2] to sign in to Google App
Engine with one's Google Apps account. Technically speaking, I would conclude
that Google App Engine supports Google Apps accounts. How can this issue move
forward then? Does everybody have to install chrometophone on its own Google
Apps account then? Please advise.
[1] https://appengine.google.com/a/<YOURDOMAIN.COM>/
[2] https://appengine.google.com/
Original comment by secage...@gmail.com
on 8 Sep 2010 at 7:00
[deleted comment]
Please, enable Google Apps fr use in Chrome to Phone !
Original comment by paulstri...@gmail.com
on 11 Nov 2010 at 8:11
Please enable Google Apps accounts for Chrome to Phone. It is sad that the
customers who actually pay for their Google Account are the last to receive new
features. We're deincentivized (if you'll allow me to make up a word) from
upgrading to a Google Apps account.
Original comment by lhagenb...@homgroup.com
on 24 May 2011 at 6:20
@p...@paulstriker.nl and lhagenb...@homgroup.com: Google Apps accounts are
essentially legacy accounts at this point. All Google Apps accounts should be
converted to Google accounts, so all Google (GAFYD and Google accounts) are on
the same platform. If you are your domain's administrator, if you log in to
your domain's control panel (https://www.google.com/a/cpanel/<yourdomain.com>),
you should see a message regarding the conversion process. It should go very
smoothly if there are no conflicts, and only takes a few minutes.
There is really no reason not to convert your Google Apps account at this
point, and when you do, you'll finally receive all of the new features right
when everyone else does.
Original comment by ji...@jimbotech.com
on 24 May 2011 at 7:15
Thank you for this update. I just checked and I'm good to go now, with my
ex-Google-Apps-now-converted-to-Google-Account account.
Original comment by lhagenb...@homgroup.com
on 24 May 2011 at 7:49
Chrome to phone did not work with Google Apps accounts in the past. In the
last few days, Google added support for Google Apps accounts to several
services (including Chrome to Phone).
Try it now. It should work.
Thanks Google. This is a very useful feature. Besides, it removes the need
for having multiple accounts unnecessarily.
Original comment by char...@cal.sigmaxim.net
on 8 Nov 2011 at 11:56
I got a message saying Chrome to Phone does not support google apps. I have
the 2.2 version installed. It works on my desktop to my phone (HTC EVO 4G) but
I'm unable to get signed in on my laptop to even send links to my phone. I
keep getting a message for Authorization Redirect Page, which doesn't do
anything at all. Just a blank page and the wheel spinning. HELP please!!
Original comment by 12joyr...@gmail.com
on 12 Nov 2011 at 1:29
Original issue reported on code.google.com by
InGeNeT...@gmail.com
on 24 Jun 2010 at 2:00