Open GoogleCodeExporter opened 8 years ago
Thanks for the report -- I have another user whose had this same issue. The
most frustraing thing is, it works on my Xoom emulator!
So, I guess you're not using two-factor auth, right?
In settings, go to "log out" then re-sync which will force you to re-login.
Please try that and see if it helps.
Original comment by tmnich...@gmail.com
on 14 Apr 2011 at 1:11
Same issue on my Asus Eee Pad Transformer:
Model: Transformer TF101
Android: 3.0.1
Kernel: 2.6.36
Bog standard, not rooted or modded - only had it since yesterday ;)
Tried the "log out" and re-sync, but no luck. The login in the browser seem to
work (I think I can see it flash the browser page with my bookmarks), but
GMarks returns with "Login error!".
Original comment by fp.coet...@gmail.com
on 14 May 2011 at 5:35
[deleted comment]
Got the code and debugged it natively against my Transformer. The request for
cookies from the database always returns 0 - a lot of "GOT cookies: 0" in the
log. I have set the time-out to a minute, but the db cursor never contains any
data.
CookieManager.getInstance().getCookie("https://www.google.com"); has some
stuff, but I do not know how to interpret it. Will continue to pick at it -
just started learning this Android lark and got up this morning with a cold, so
progress might be slow.
Original comment by fp.coet...@gmail.com
on 15 May 2011 at 5:16
I am having the same issues with my T-Mobile G-Slate. Continuous "login error"
message. Try logout and then logging back in with no luck. A few times, after
submitting my password, the screen will briefly flash to my Google bookmarks
page, then kick me back to gmarks stating "login error"
Original comment by janet...@gmail.com
on 14 Jul 2011 at 12:15
Same thing happens to me with my Samsung Galaxy Tab 10.1 (Android 3.0.1). I
can't get past the "Login Error" message.
Please make this app tablet ready. GoMarks sucks as it constantly Force Closes.
BTW, GMarks works fine on my NexusOne (Android 2.3.4).
Original comment by cdore...@gmail.com
on 26 Jul 2011 at 12:39
Can someone with root access on their Honeycomb device send me their webview
database file from
/data/data/org.thomnichols.android.gmarks/databases/webview.db?
pls email it to tmnichols@gmail. Don't attach it to this issue since it has
auth information. I'm hoping once I have that, I'll be able to discern why
login doesn't work on Honeycomb tablets.
Thanks for your patience!
Original comment by tmnich...@gmail.com
on 5 Aug 2011 at 1:06
Good news! I'm fairly certain I've found the problem on Honeycomb and released
0.6.7 to the market which should remedy the issue. Please give it a shot and
let me know!
Original comment by tmnich...@gmail.com
on 7 Sep 2011 at 5:02
Issue 57 has been merged into this issue.
Original comment by tmnich...@gmail.com
on 7 Sep 2011 at 5:03
On my Motorola Xoom, the version in the Android Market reflects version
0.6.6. Tried to download, and still receive the Login Error; am still asked
to log in.
Original comment by jvetal...@gmail.com
on 7 Sep 2011 at 11:34
Same here. Via app or web, market still shows 0.6.6. Just to be thorough, I
also checked using my wife's g2, also 0.6.6.
Original comment by aharri...@gmail.com
on 8 Sep 2011 at 1:56
Hmm.. Sorry about that, they changed the admin interface and apparently I
didn't actually publish the update :) Pretty sure I did it right this time;
the Market page says 0.6.7.
Original comment by tmnich...@gmail.com
on 8 Sep 2011 at 10:32
Yes!!! Now works on my Acer Iconia Tab (H3.1)!
Thanks!!
Original comment by starcrui...@gmail.com
on 8 Sep 2011 at 11:16
Installed the new version from the Market, but I am still having the same
issue. When I try to login, the screen flashes the login screen, then all info
except the spatter header and footer disappear. These scrends flash one to the
other very quickly (every second or so) about a dozen times, then send me back
to the gmarks home screen with the message login error.
I have tried uninstalling and reinstalling, clearing the cache, restarting,
etc....
I am running LG/TMo G-Slate, Honeycomb 3.1
Original comment by janet...@gmail.com
on 8 Sep 2011 at 9:46
Hmm, Comment #14 sounds like a different problem. What time did you happen to
install the update? As of this morning (Eastern time) 0.6.6 was still on the
market.
Original comment by tmnich...@gmail.com
on 8 Sep 2011 at 10:10
Issue resolved for me on my Asus Eee Pad Transformer. Thank you!
Original comment by fp.coet...@gmail.com
on 8 Sep 2011 at 11:57
RE: My comment #14: I have installed version 0.6.7 that was uploaded to the
Market this morning. I uninstalled and reinstalled (again) and it appears to
be working now... first sync has started! Woo Hoo!
Original comment by janet...@gmail.com
on 9 Sep 2011 at 12:54
Woot! Working great on my Xoom. Thanks Thom!
Original comment by aharri...@gmail.com
on 9 Sep 2011 at 1:11
Version 0.6.7 now works on my Samsung Galaxy Tab 10.1 (Android 3.0.1). Thanks
for the fix! Goodbye GoMarks!
Original comment by cdore...@gmail.com
on 9 Sep 2011 at 3:53
Brand new transformer, same problem. cycles between login page without
prompting for user/pass to a mostly blank page and back again. two-step auth
enabled, tried both google user/pass and app password.
Original comment by ken.pascoe
on 9 Sep 2011 at 7:15
The 0.6.7 version in the market now works on my moto Xoom. Thanks very much!
Original comment by jvetal...@gmail.com
on 9 Sep 2011 at 1:44
For those of you seeing flickering, this is a new issue, recorded in issue #58:
http://code.google.com/p/gmarks-android/issues/detail?id=58
I'm working on a fix now.
Original comment by tmnich...@gmail.com
on 9 Sep 2011 at 8:30
Anyone experiencing the 'flickering' login problem, I need someone to follow
the instructions at the bottom of issue #58 so I can see which URL is causing
the login to fail. I can't reproduce the problem myself.
Original comment by tmnich...@gmail.com
on 12 Sep 2011 at 12:13
Anyone experiencing the 'flickering login' problem detailed in issue #58, it is
fixed now in GMarks 0.6.8 which is now published in the Android Market.
Original comment by tmnich...@gmail.com
on 14 Sep 2011 at 1:10
Original issue reported on code.google.com by
michaelmcole@gmail.com
on 11 Apr 2011 at 2:01