Closed GoogleCodeExporter closed 8 years ago
Thanks for filing a report. Yes, your issue was caused because you never
actually "selected" an account from the account selection menu. Every time the
menu is opened, the stored account is cleared--a necessary hack, for the
current way accounts are handled. This is, clearly, an inadequate way of
handling the issue, and I will leave this ticket open as a reminder that I need
to fix that in a future release.
Your second concern, if I'm reading this right, is that you're confused about
your account, the server, and your privacy.
Your account is simply a Google Account. Any Google Account should work without
a single problem, provided you select it once added (which I need to fix,
you're right). The only information ever, ever accessed from your account
(stored or otherwise) is your account name (your email address).
The server is a custom App Engine website that acts as a database, and serves
as the "cloud" half of the equation. Your phone logs in (securely, with OAuth;
the website never knows your password), and stores your email address and the
link you're sending. Your browser checks every few seconds, and tells the
website to give it the last link associated with your email address. If the
link is different from the last one the browser opened, the browser opens it.
The privacy policy can be found here:
http://code.google.com/p/android2cloud/wiki/Privacy It is subject to change,
but I do so reluctantly and make every effort to contact every single affected
user before the change takes place.
The one major privacy tool I lack right now is the ability to log into the
website and delete every trace of your account, removing you from the system
entirely. I will make a note to have that included in a later release, as well.
Finally, as for the question on documentation, I must admit that it is
extremely sparse right now. That is a short-coming on my part, and one that I
wish to rectify. I'm stretched a little thin (I'm a student doing this in his
spare time) at the moment, but I'm working on simplifying the custom server
install process so that people can easily launch their own server, and not have
to trust me with their data.
If you're interested in doing so, please don't hesitate to use the Google Group.
Thanks for filing an issue.
Original comment by foran.pa...@gmail.com
on 5 Aug 2010 at 12:54
Thank you for your quick and detailed response.
I have tried adding my Google account, but get an android default "Web page not
available" page with OauthCommunicationException.
For the username I entered my full gmail e-mail address in the format of
"username@gmail.com" as per the instructions and the domain http://gmail.com. I
also tried without the http:// as in the example. But get that "page not
available" 404 above.
Thank you for your time and work, I e-mail myself links from my phone several
times a week, and now you've made that process much easier and simpler. Thanks!
Original comment by tse...@gmail.com
on 5 Aug 2010 at 1:05
Attachments:
Sorry for the confusion. When adding an account, you have two fields: Account
and Host. Account is arbitrary; it simply serves as a label, for your own
identification purposes. The application doesn't care whether it's your
username or your mother's favourite flavour popsicle.
The Host field, unless you've set up your own server, should be
http://android2cloud.appspot.com -- http:// included, no trailing /.
The email address you use is entirely determined by whatever email address you
grant access with on the following screen. If you're logged in, it may just ask
you to grant access. In this case, your email will be in the top right hand
corner, and there should be a log out link, if you'd like to use a different
account. If you're not logged in, it will ask you to.
Thanks for your understanding. :)
Original comment by foran.pa...@gmail.com
on 5 Aug 2010 at 1:16
Original comment by foran.pa...@gmail.com
on 5 Aug 2010 at 6:01
@foran.pa...@gmail.com
According to your last post, the Android app should work without any changes in
account settings.
But the "Send" button is inactive.
When I'm trying to add a new account (with "username@gmail.com" and
"http://android2cloud.appspot.com") I'm receiving the same 404 error as tseven
(CAP201008041804.jpg).
So, what I have to do?!
Original comment by n.mi...@gmail.com
on 23 Aug 2010 at 6:08
Have you successfully added an account? Do you get a page asking you to log
into your Google account? Is it after that that you get the 404, or before?
Original comment by foran.pa...@gmail.com
on 24 Aug 2010 at 1:37
No. I didn't add an account.
I can't see any page, different than 404.
After trying to sent any URL to PC, on the first screen the "Send" button is
inactive and the only option is to change account settings.
On the next screen always there is "Add New Account" only.
The next screen is with the Account: "Default" and the Host:
"http://android2cloud.appspot.com". No matter if I leave the "Default" or
change it to "username@gmail.com" (and without changes in Host:
"http://android2cloud.appspot.com") - the next screen is always 404
(CAP201008041804.jpg).
And after any attempt Google Chrome button on the PC opens (of course) blank
page.
By the way, isn't it strange - the app with this functionality to take 1.32 MB
(Application 1.29 MB, Data 40.00 KB - Settings/Applications/Manage
applications) on limited space of Motorola Milestone (with Android 2.1 update
1)?
Original comment by n.mi...@gmail.com
on 24 Aug 2010 at 4:29
I'm sorry. This is really bizarre. Do you know how to access the logcat debug
information?
As for the size, the app unfortunately requires an OAuth library (so I don't
need to handle your password) and a few Apache libraries. These, I would
imagine, constitute a large part of the app. If you're suspicious of its
content, though, I encourage you to build it from source, so you may inspect
each and every inch of it. :)
Original comment by foran.pa...@gmail.com
on 24 Aug 2010 at 5:43
Unfortunately I don't know how to access the logcat debug information.
About the size: I was curious, because there no any graphics, sounds or
something that can increase it's size. I'm not suspicious at all.
Original comment by n.mi...@gmail.com
on 24 Aug 2010 at 5:55
Yeah, it's just a bunch of code. OAuth is a complicated business (clearly-- 99%
of the bug reports I'm getting have to do with OAuth) and it needed a few
libraries to be included. The app CAN be moved to the SD card, but I know you
need froyo for that.
If you don't mind, I'd like to give you a special version of the 0.3.1 beta
that's in testing right now. I'll add a few lines to add some more useful debug
information, and if you're ok with it, you can send the log to me using Bug
Reporter, a free application in the market.
Does that sound like an acceptable plan? I'm really sorry; I'm just stumped.
That exception is raised by the OAuth library when the communication between
the server and your phone breaks down-- that only usually happens when there's
not actually a server where the phone is looking for it.
Original comment by foran.pa...@gmail.com
on 24 Aug 2010 at 6:14
OK. Send the beta. I'll download the Bug Reporter (but which one: Robot Media
or BH_Lin?). And then we'll see.
Original comment by n.mi...@gmail.com
on 24 Aug 2010 at 6:34
I've uploaded it here: http://dl.dropbox.com/u/6777769/android2cloud.apk (sorry
that took so long)
If you could run it and send a bug report from the Robot Media Bug Reporter,
I'd really appreciate it.
Original comment by foran.pa...@gmail.com
on 25 Aug 2010 at 5:57
Report sent.
Original comment by n.mi...@gmail.com
on 25 Aug 2010 at 11:27
Thanks for your report. It cleared some stuff up. The important line is:
08-25 13:57:59.289 I/android2cloud( 6806): OAuth(143) e.getMessage():
Communication with the service provider failed: Service provider responded in
error: 400 (Bad Request)
It looks like, for some reason, you aren't requesting the right URL. Your host
looks good, but your OAuth Request URL wasn't logged.
If you don't mind running this apk:
http://dl.dropbox.com/u/6777769/android2cloud.apk and telling me what error it
gives you, that'd be great. If you want to send another bug report after
running that, that'd be even better.
I'm really sorry. This is totally bizarre-- the OAuth Request URL is hardcoded
into the application, so I'm not sure how it could get botched.
Original comment by foran.pa...@gmail.com
on 25 Aug 2010 at 10:54
I'll uninstall the current beta, then install the new apk, then run the Bug
Reporter and send the report...
...then I'll send you a bill for software QA testing :)
Original comment by n.mi...@gmail.com
on 26 Aug 2010 at 7:26
Thanks. I appreciate the bug report. :) As for the bill, absolutely. I'll
include it with mine for software development whenever I figure out who's
paying the bills. :P
Original comment by foran.pa...@gmail.com
on 26 Aug 2010 at 9:13
This issue has gotten a little off-track, and I haven't received a bug report
from n.minev. As the original issue has been resolved, I'll mark this issue as
closed. n.minev, please do feel free to file a new bug report with your issue.
Original comment by foran.pa...@gmail.com
on 7 Sep 2010 at 6:55
Original issue reported on code.google.com by
tse...@gmail.com
on 5 Aug 2010 at 12:34