Great, so I merged this into release branch. I also created a separate ashish branch for you. It's recommended that you checkout that branch and push into the same branch(ashish).
Everybody works in their separate branch and I eventually merge all those changes into release branch.
Master branch has the production code that is tagged for release on F-Droid store i.e a new tag creates an update notification to all F-Droid users.
There are some tasks still pending. One of them is to get the url dynamically instead of hard-coded string (http:172....).
PU@Campus is weird, it sometimes redirects and sometimes serves a local page instead that redirects.
It isn't completly successful but works in some situations.
CASE 2: Local server serves page instead of google.com which redirects (UIET, PU@Campus sometimes does this)
We need to figure out a way to distinguish normal google homepage from the one served to us.
Then we need to parse that page data to get the url, which is easy (RegEx).
Then we need to find out what the username and password field's id are in response. This is tough part I guess. Let's reach till the above point and then we'll figure out a solution for this phase too.
Update: I just opened a separate issue #14 for this. Let's figure out ways to do this there.
Great, so I merged this into release branch. I also created a separate ashish branch for you. It's recommended that you checkout that branch and push into the same branch(ashish).
Everybody works in their separate branch and I eventually merge all those changes into release branch. Master branch has the production code that is tagged for release on F-Droid store i.e a new tag creates an update notification to all F-Droid users.
There are some tasks still pending. One of them is to get the url dynamically instead of hard-coded string (http:172....).
CASE 1: Redirections 302
CASE 2: Local server serves page instead of google.com which redirects (UIET, PU@Campus sometimes does this)
Update: I just opened a separate issue #14 for this. Let's figure out ways to do this there.