Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to login() after checkin() #29

Open
ghost opened this issue Aug 13, 2013 · 13 comments
Open

Unable to login() after checkin() #29

ghost opened this issue Aug 13, 2013 · 13 comments

Comments

@ghost
Copy link

ghost commented Aug 13, 2013

In TestGooglePlayCrawler.java, login() will be failed by using the android-id generated after run checkin().
Listcommand also failed.

@HenryHoggard
Copy link

Duplicate of #28 , currently working on a fix.

@ghost
Copy link
Author

ghost commented Aug 13, 2013

I wonder why googleplay client still works, if the request is disabled.@HenryHoggard.

@filamoon
Copy link

@HenryHoggard Please kindly keep us posted :)

@Akdeniz
Copy link
Owner

Akdeniz commented Aug 13, 2013

I don't know why but google started to require a parameter named "client_sig" on authentication, which is kind of a identity for login service system apk. By the way its value does not matter, as far as tested. Weird!

Anyway, last commit should work.

@ghost
Copy link
Author

ghost commented Aug 14, 2013

@Akdeniz How you test it out? On your android device?

@Akdeniz
Copy link
Owner

Akdeniz commented Aug 14, 2013

@uptown1919 No, I prefer to use emulator.

@spacegom
Copy link

@Akdeniz Thanks alot!!!!!

@CodeheadUK
Copy link

@Akdeniz
Wow, quick fix! Great work, thank you.
Care to share how you pulled the API apart? I was poking around yesterday trying to work out where the problem was, but didn't get very far.

@HenryHoggard
Copy link

@CodeheadUK The way I did it was if you use a proxy to view the requests you will see that you get 404 or error 500 unless you add client_sig to the requests. I discovered it was client_sig by comparing the checkin request to the search request because checkin still worked and search didn't. After trial and error I found that client_sig was the difference between the two requests.

@CodeheadUK
Copy link

@HenryHoggard, Thanks for the info.
I saw the 404 and convinced myself that URL_LOGIN was wrong or had changed. I figured that I could snag the traffic from an emulator for more info, but got put off by the https encryption.

@filamoon
Copy link

@CodeheadUK Here is what I did with https on my device:

I'm using the Charles proxy tool that comes with a SSL certificate. Install the certificate to the phone. Then in wifi settings, enable advanced options and set the proxy IP and port accordingly. Enable SSL proxy in Charles, then you will be able to decrypt the https payload.

@CodeheadUK
Copy link

Top tips, Thanks @filamoon.

@qwertydzen
Copy link

@Akdeniz thank you for the fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants