Closed GoogleCodeExporter closed 9 years ago
I too have this same problem with my GAFYD / GApp account.
I have the exact same setup as above too !
Original comment by metse...@ymail.com
on 14 Jul 2010 at 8:41
Same issue here, using CM 6.0.0 RC1 on the Dream, not that I am sure that this
makes any difference to the way that the thing attempts authentication. All
other Google apps work on the device, including the Market, Maps/Navigation,
GMail, and so forth, so it's not a problem with the credentials on my account.
Original comment by mike%tra...@gtempaccount.com
on 14 Jul 2010 at 10:08
Setup instructsions specifically mention Google Apps are not supported:
http://code.google.com/p/chrometophone/wiki/SetupInstructions
Original comment by roger.warwick@hotmail.com
on 15 Jul 2010 at 9:40
True, but that doesn't make this issue invalid. It should support GApps
accounts 'cause they are Google Accounts.
Original comment by r3...@r3pek.org
on 15 Jul 2010 at 3:52
That's understood, roger@gomadrid.com, but that doesn't make it any less of a
defect. Support for GAFYD is something that many applications have support
for, and it's not technically difficult to do—and for that matter, it makes
this whole thing useless for those of us that exclusively use GAFYD for one
reason or another.
I can understand why it wouldn't generally work for any sort of system, but
GAFYD is still run by Google, and should still work.
Original comment by mike%tra...@gtempaccount.com
on 15 Jul 2010 at 3:53
I also agree, surely GAFYD should be compatible across the Google products.
This issue however is still evident when trying to purchase apps from the
Market, you simply can't do it because it doesn't recognise the GAFYD email!!
Original comment by metse...@ymail.com
on 15 Jul 2010 at 4:04
I've improved the error message to state clearly that Google Apps accounts are
not supported. They will be in the future (when core infrastructure supports
them) but don't have a specific time.
Original comment by burke.da...@gmail.com
on 31 Jul 2010 at 8:50
great, this app is useless to me without being able to support gapp accounts
since when i log into google voice on my computer it logs me out of my
chrometophone gmail account
Original comment by mrono.mr...@gmail.com
on 2 Aug 2010 at 8:12
Absolutly must have. Really bad ad for Google Apps :-S
Original comment by ada...@gmail.com
on 2 Aug 2010 at 8:33
Is there any plan for adding support for Google apps accounts?
Original comment by greppade...@googlemail.com
on 3 Aug 2010 at 9:07
I have Google apps and i just installed a gmail account to in the phone and it
worked perfect.
But i still want it to be able to use google apps so i can trash my gmail :)
Otherwise i love this app :)
Original comment by col...@gmail.com
on 3 Aug 2010 at 4:33
Issue 146 has been merged into this issue.
Original comment by aml...@gmail.com
on 4 Aug 2010 at 7:16
Google Voice works if you create a regular google account with the same
user@domain as your GAFYD account user@domain. I'm assuming this must use some
other means of authentication/communication. Google Voice lets you put in a
user/pass rather than using sync accounts. Possible solution? Dunno.
Original comment by matthewm...@gmail.com
on 4 Aug 2010 at 1:49
Issue 149 has been merged into this issue.
Original comment by patrick....@gmail.com
on 4 Aug 2010 at 3:42
I have the same problem! When can we expect an update?
Original comment by andre.vo...@gmail.com
on 13 Aug 2010 at 4:56
The timeline is not within this projects control, it depends on an upgrade to
the AppEngine
Original comment by patrick....@gmail.com
on 13 Aug 2010 at 9:09
This is absolutely critical for me to use this app. Otherwise, this app is
useless to everyone at my company.
Original comment by ben%benl...@gtempaccount.com
on 13 Aug 2010 at 3:40
I have the same problem before, but it works now with my Google apps account.
Pls try again!
Original comment by KevinOKW...@gmail.com
on 15 Aug 2010 at 2:26
@KevinOKWong, are you sure? I've tried again and it definitely does NOT work.
Original comment by metse...@ymail.com
on 15 Aug 2010 at 8:45
I've just tested again, it worked.
One week before, I couldn't even able to connect to Chrometophone server from
my Nexus One when I was using a Google apps account, then I registered a Gmail
account and tried again, it successfully connected. Today, I disconnected
Chrometophone server from my Nexus One, and signed in/connected using the
original Google apps account again at both my PC and Nexus one, it worked.
Strange!
Original comment by KevinOKW...@gmail.com
on 15 Aug 2010 at 11:31
Confirmed. My GAFYD account worked fine.
Original comment by 4braham
on 15 Aug 2010 at 7:41
I have 4 google apps account on my phone.. it only worked with one. my
"GoogleAccount@<mydomain.com>" account... worked on both ends and tested ok. I
have a @gmail.com account I set up just for these functions and this version
force closes every time it tries to access that account. That is the same
account I used on earlier versions... Just for kicks I thought I'd try my other
accounts and B-I-N-G-O the one apps account worked (other 3 did not) WTF?
Original comment by GoogleAc...@Air-Gen.com
on 15 Aug 2010 at 7:43
My Google Apps account doesnt' work :-(
Original comment by bohuslav...@gtempaccount.com
on 15 Aug 2010 at 7:47
It would be nice to try to understand what type of accounts does work. Like
type of account (free/enterprise/education) and extra apps associated with the
domain.
I have 2 accounts and none work (Free/nothing extra)
Original comment by claudia....@gmail.com
on 15 Aug 2010 at 11:28
If it ends in @gmail.com .. it should work... if it ends in anything else... it
wont.
Original comment by kiall%ma...@gtempaccount.com
on 15 Aug 2010 at 11:33
I'm running Google Apps Standard Edition on @abrah.am and it worked just fine
to register on the phone, with the extension and to send a URL to the phone.
Original comment by 4braham
on 15 Aug 2010 at 11:39
Google Apps accounts are NOT supported. This is stated clearly in the installer.
It is a known issue however it is out of the control of this project at the
moment to resolve.
Only Gmail accounts work with Chrome To Phone
Original comment by patrick....@gmail.com
on 16 Aug 2010 at 9:38
OK, for you dense people who "KNOW" google apps accounts don't work. SOME OF
THEM DO!
NOT SUPPORTED and NOT WORKING are also two different things.
"Only Gmail accounts work with Chrome to Phone" is a FALSE statement.
My account that works is in the same domain as other accounts that don't. My
google apps account for that domain is relatively new, after they stopped
allowing the old start page. It is a free account. My primary email address at
that domain does not work, but the account I set up to buy my nexus one
"GoogleAccount@<mydomain>.com" does work. It has that capitalization, and is a
.com.
Original comment by GoogleAc...@Air-Gen.com
on 16 Aug 2010 at 3:07
Interesting detail about the account that works. It is not an actual email
alias. it is forwarded to another email account through the * function. I only
use it to log into google services.
Original comment by GoogleAc...@Air-Gen.com
on 16 Aug 2010 at 3:25
It just clicked why my Google Apps account works. Because it is also a
considered a Google Account.
http://www.google.com/support/accounts/bin/answer.py?hl=en&answer=182174
Original comment by 4braham
on 16 Aug 2010 at 3:55
BINGO. That explains my account. i had to set that account up because trying to
use one of my primary emails would have resulted in a loss of services by
converting it to a "google account".
Original comment by GoogleAc...@Air-Gen.com
on 16 Aug 2010 at 4:49
This is correct - some google apps domains do work. The correct statement is
"Only Gmail accounts are officially supported by chrometophone".
As you can see in the code, the chrome extension and the android app are using
the account to login to the app engine application. App engine doesn't support
google apps accounts (except those converted to the new system for testing).
Maybe we can make a code change and allow registration without account/password
- for example the appengine side could generate a random token which could be
displayed on the android app ( like the hash of the registration token), and
than entered on the chrome extension. There is some potential for abuse ( DOS,
etc ), but it could work until all google apps accounts are converted.
Opinions ?
Original comment by cos...@google.com
on 16 Aug 2010 at 5:21
Issue 203 has been merged into this issue.
Original comment by aml...@gmail.com
on 7 Sep 2010 at 7:46
http://googleenterprise.blogspot.com/2010/09/early-adopters-transition-to-new.ht
ml
I'm marking this as fixed - it requires domains to transition to the new system.
Please re-open the bug if your domain migrated and it still doesn't work.
Original comment by costin
on 9 Sep 2010 at 6:01
It's funny, but my account just just migrated and it still says that Google
Apps are not supported.
Original comment by r3...@r3pek.org
on 9 Sep 2010 at 7:05
Chrome to phone login in browser is possible, phone says it's not possible
to login with Apps...
Op 2010 9 9 21:05 schreef <chrometophone@googlecode.com> het volgende:
connection
Google
Original comment by wwwou...@gmail.com
on 9 Sep 2010 at 7:23
After one day of the account being a "Google Account", i still can't setup
chrome2phone on the phone. Maybe some caching problems? Really don't know, but
something's wrong here.
Original comment by r3...@r3pek.org
on 10 Sep 2010 at 3:41
Details please, hard to debug something with "something is wrong here".
Please note that if you want to use picassa, google voice etc after migrating
your account to the new "Google Account" (from "Hosted Account") - you will
need to remove the hosted account and add it back again, currently the phone
won't detect the change. C2P doesn't have this problem - since it's asking for
HOSTED_OR_GOOGLE when listing accounts.
Original comment by costin
on 11 Sep 2010 at 12:27
All I can say is something is wrong, I don't have any other infor to tell you.
(I'm a dev myself and I know this hurts :P )
The app doesn't produce any log in logcat (only Google Apps accounts not
supported is shown on the aplication).
All I can say to you is that picasa sync was automaticaly enabled after a
reboot, so the phone already knows it is a google account. it's just c2p that
doesn't detect it as such. If I can help in any other way just tell me how that
i'm glad to help.
Original comment by r3...@r3pek.org
on 11 Sep 2010 at 12:47
Issue 226 has been merged into this issue.
Original comment by aml...@gmail.com
on 9 Oct 2010 at 9:24
Issue 247 has been merged into this issue.
Original comment by aml...@gmail.com
on 18 Nov 2010 at 3:47
Original issue reported on code.google.com by
r3...@r3pek.org
on 14 Jul 2010 at 6:24