g3ortega / chrometophone

Automatically exported from code.google.com/p/chrometophone
0 stars 0 forks source link

Google apps account works in chrome, not on phone #92

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Please answer the questions about build version and network, will save
developers a lot of time !

What steps will reproduce the problem?
1. login in google chrome with google apps account (success)
2. login on nexus one with google apps account (fail)

What is the expected output? What do you see instead?
If I can use my google apps account to login in my browser, I would assume it 
would also work on my phone. Is there a reason it does not? I'm a bit confused.

What version of the android, in Settings -> About phone -> Build number (
ex. FRFxx ) ? If less than FRF50 - see the FAQ.
FRF83

Is the phone using WiFi or mobile network when problem occurs ? If Wifi,
are you behind a firewall that blocks outgoing connections ?
NO

Can you open "Gmail" application ? Do you see new messages without hitting
'refresh' ?
Yes

Can you open "Talk" application ? Do you see incoming chats ?
Yes

Please provide any additional information below.

Original issue reported on code.google.com by InGeNeT...@gmail.com on 24 Jun 2010 at 2:00

GoogleCodeExporter commented 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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
@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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Please, enable Google Apps fr use in Chrome to Phone !

Original comment by paulstri...@gmail.com on 11 Nov 2010 at 8:11

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
@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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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