New APK

---

Originally Posted by jjwa

Any response to my other issues I wrote about in the above posts?

1) Nothing syncing between GMarks and my browser. (Post #5)
2) Newer version: nothing syncing. At all. (Post #8)

Hi jjwa,

Thanks for working with me to resolve this. I've attached another APK for you to try. After installing, go to Application Management-> GMarks -> Clear Data and give it another try.

If that doesn't work, do you have the SDK tools installed? I can't reproduce this problem so I'd have to rely on getting debug information from you via the "adb logcat" tool.

I apologize for the trouble, and appreciate you're helping me make GMarks better!

Thanks again. Let me know how the new APK goes or if you need instructions on how to use logcat.

Originally Posted by tomstrummer

Hi jjwa,

Thanks for working with me to resolve this. I've attached another APK for you to try. After installing, go to Application Management-> GMarks -> Clear Data and give it another try.

If that doesn't work, do you have the SDK tools installed? I can't reproduce this problem so I'd have to rely on getting debug information from you via the "adb logcat" tool.

I apologize for the trouble, and appreciate you're helping me make GMarks better!

Thanks again. Let me know how the new APK goes or if you need instructions on how to use logcat.

The APK did not produce a different result compared to the previous one as far as I could see.

I currently don't have a working USB cable, so I tried out apps for the adb logcat thing. I have used adb before, but I have no experience logcat, so if you need it done with differently settings (I was now logging at the 'Error' filter level btw). I've sent a log to your gmail adress instead of posting it here, because I wasn't sure there was no information in there I would not want to have up in public...

For recording the logs, I repeated the Clear Data steps, started the log apps, logged in on GMarks, let it attempt it's sync, and then told the apps to email their logs.

Let me know if this is sufficient or if you need me to do it differently or do something else.

P.S. Random curiosity: the log is getting spammed massively with 'WPA supplicant' messages. I know that's related to my WiFi. Any idea why it's going so crazy? Should it? Is it just the security protocal chitchat?

Which passwords should I insert? Can I insert the Application specific one? I'm not comfortable inserting my password just to use the credentials, now that we have specific passwords...

Authentication

---

Originally Posted by alex_herrero

Which passwords should I insert? Can I insert the Application specific one? I'm not comfortable inserting my password just to use the credentials, now that we have specific passwords...

Hi Alex,

Unfortunately you have to use your own, normal password (followed by a verification code if you've enabled two-factor auth.) One-time use passwords unfortunately don't work here - they only work for AuthSub enabled services and the Bookmarks service (as far as I know) doesn't support AuthSub. I tried to use a one-time password myself and the login page rejects it and says as much.

The reason GMarks for Android directs the user to the Google login webpage is exactly because I expect users would (or *should*) be wary of inputting their username and password directly into an Android app. (Lots of apps still seem to do this anyway...) Because you are logging in through the webpage, the GMarks app never sees your username or password.

If it makes you feel any better, if you have two-factor auth enabled, any app that _did_ capture your username and password wouldn't be able to log in without the additional verification code. And the verification codes only work once so that code can't be 'stolen' and used to log into your account from somewhere else.

Sorry! I think this is the best anyone can do until Google releases a real Bookmarks API...

Two-factor auth support

---

Hi folks -- here's a new 0.6.4 build with two-factor auth support.

Entering in the verification code is still a bit of a pain in the ass, but I think it's the best that can be done. Once you enter your username & password in GMarks you get directed to the verification page, at which point you have to switch to the Google Authenticator app.

You can do this quickly if you open the Authenticator app first and then long-press the home button to switch between the two activities. You can also copy the verification code from the Authenticator app by long-pressing on the number. Then you can paste it into the browser textbox in GMarks.

This build also includes the ability to fully re-sync with the server, which will resolve any sync problems and remove stale bookmarks that might have been left on your device if you've deleted bookmarks via the web interface. It's the last item when you go to Menu->Settings. Since this re-downloads *all* of your bookmarks it should be something that is not done often, hence the reason why it's a bit 'hidden away.'

Tom,

thanks for your detailed and excellent answer. I'll try this latest build and come back with results.
[Edited] Seems to be working very well for me. The only comment would be the same as previously stated: when validating the code, you need to leave the application to go to Google authenticator, when you come back, you need to re-enter user and password...

Thanks!

Authenticator/ two-factor support

---

Originally Posted by alex_herrero

thanks for your detailed and excellent answer. I'll try this latest build and come back with results.
[Edited] Seems to be working very well for me. The only comment would be the same as previously stated: when validating the code, you need to leave the application to go to Google authenticator, when you come back, you need to re-enter user and password...

Alex! You'll be happy to hear I realized there's a much more elegant way to make this work -- I can launch the Authenticator activity straight from GMarks (if you have it installed.) So you can copy the code and just hit 'back' to get back to enter it into the verification page.

Try out the attached build. I think it's a big improvement over the prior solution.

Hi,

Is the version on the market not the latest? I've the market version that says 0.6.4, but 2-factor authentication behave the same as before.

0.6.4

---

Originally Posted by BruceCLin

Hi,

Is the version on the market not the latest? I've the market version that says 0.6.4, but 2-factor authentication behave the same as before.

Ooh, that's creepy. I've staged an update but not published it yet. Odd that the Market is now showing the description for 0.6.4 even thought the admin console clearly shows that the last published version is 0.6.3.

You didn't get a Market update, did you?

I plan to publish 0.6.4 soon! I was hoping to get some feedback from the build that I attached in my last post to see if everything looked like it was working correctly first.

If you haven't seen it yet, 0.6.4 is _actually_ released now. I've had some feedback already that two-factor auth is working smoothly now (in addition to my own testing) so you should be good to go! http://goo.gl/AbeDh