Thanks, @Umherirrender and @Mainframe98. I will use stashed uploads for this feature.

Thanks, @matej_suchanek. That was indeed the cause of the error.

Madhur Gupta is working as a GSoC student for the Wikimedia Commons app. Please grant him access.

@Gouri_panda Thanks for submitting the proposal. It looks great in general and I don't have any specific comments. It might be helpful if you could elaborate the timeline a bit more and make it weekly instead of biweekly.

@Madhurgupta10 Your proposal looks great. Also, your profile is quite impressive. :)

Welcome everyone and thanks for showing interest in this app.

It would be great if this task could be prioritized as it will remove our dependency on the production cluster for testing uploads. :)

I checked with @josephine_l and @Ashishkumar468 and they are fine with having this as GSoC project this year.

@srishakatux I have pinged my other team members. I will comment here once I hear back from them.

@Smalyshev No it doesn't really matter with which endpoint it is connected. We just need an http query endpoint for test wiki data.

@Gopavasanth You can try posting about the issue on discourse if not already done. Someone might be able to help. :)

It would be great if someone could help here. :)

In the Wikimedia Commons Android app, we query Wikidata to show a list of nearby places needing pictures. When an image is uploaded through one of these places, the P18 property is edited automatically for the corresponding Wikidata item.

It wasn't picked up during the hackathon as T223159: Navigation redesign of the Commons Android app took priority over it. Closing it as declined.

Yes. this session took place as planned. Here's the presentation link for reference.

A similar issue is also happening with Commons Android app where the app is unable to connect to beta cluster (https://commons.wikimedia.beta.wmflabs.org).

Moreover, if you have familiarity with python scripting, it would be nice to mention it in the proposal. As you might be required to help in the development of the APIs required for building leaderboard. Our self hosted APIs exist in this repo: https://github.com/urbanecm/commonsmisc

@NahidFatma Thanks for submitting your proposal. Overall the proposal looks good to me.

@SilkyPriya Thanks for documenting your proposal here. Overall the proposal looks good to me.

Excited to see VideoWiki exclusively use Commons content. :)

Yes, this task has been completed by @Tanvidadu1998 and nothing is pending from her end.

Yes, the task has been completed by @Tanvidadu1998 and nothing is pending. In fact, her changes have already been pushed to the play store. One can check it out by updating to the latest version of the Commons Android app. :)

Instead of the login API (which does not support 2FA) you'd have to use the clientlogin API, and depending on what response you get call it a second time with the 2FA response.
Clientlogin is an open-ended API that basically just replicates what the web login does, so after submitting the username + password it might ask you for something else (the 2FA response, but also e.g. a new password if your current password is too weak). So it's not trivial to implement. The original intent behind it is to provide the information clients need to build a login form, without having to understand what the elements in that form are for. You can try to only implement the steps that you care about, though - you can look at how the Wikipedia app does it.

@Tgr I added the centralAuthToken along with csrf token and the upload succeeded for me.

@Tgr I figured out that the first call GET /w/api.php?type=edit&action=tokens is not returning a token(fails with the user not logged in error) so the subsequent upload call doesn't have the proper auth cookie set. This explains why the upload was failing.

So does it suggest that we are not sending the session cookies with our POST request or is there a possibility that they are just not getting printed? To add more context here's the network interceptor that I added to print these request logs:

Yes, now I am able to push to the repo. Thanks a lot, @mmodell.

@Aklapper I misinterpreted you. Sorry.

labs/tools/Commons-twitter-bot looks to be a different project than what tool-commons-android-app is supposed to be.

Yes, I have already added my ssh keys to phab.

Thanks, @matej_suchanek I figured out my mistake. I was sending the tag inside a single quote mark so the API was throwing an error. It's working for me now. Thanks a lot for your help. :)

@matej_suchanek I was trying to add this tag but I get the following exception:

Thanks a lot @matej_suchanek! This is precious information for us. :)

Thanks @matej_suchanek. I will contact the administrators to create a tag for us.

Thanks for submitting the proposal. It looks good in general. Your past experience with Android and Git, in general, is also impressive.

Good to see that you have updated the formatting, it looks much more readable now. :)

Thanks for putting up the proposal on phabricator for review. It looks to me and its good to see that you have experience working with several apps in the past. If some of those apps are already in the play store (in addition to the GitHub projects, which itself is good enough) it would be great if you add a link to it.

Nice to see that you have submitted a proposal for the project. Your past work looks really interesting :)

The proposal looks great to me :).

The proposal is quite comprehensive and answers almost all questions one would have while evaluating a proposal for the internship program. :)

Thanks @srishakatux. Have updated the description. :)

Its Maskaravivek. Thanks @Legoktm

@Fjalapeno Hey! Do you have any pointers for us?

Thanks @Tgr for your reply. Then I guess @Fjalapeno can confirm if there's any need to continue with this task. WMF's legal team can probably connect with WMF tech people to align themselves on the challenges.