Images are not being uploaded to creative commons from google drive about gdrive-to-commons

[NdibeRaymond]

possible duplicate of issue #32

[RishikaBhatia17]

Hi @NdibeRaymond ,
I have just gone through the issue #32 .
I have found out that you have not mentioned the actual results clearly and i feel that the issue has been just mentioned vaguely. That's why I have added this issue.
Thanks!

[tonythomas01]

Thank you guys. Can you also paste the result of the network call (from inspector in the browser) to the POST call to upload/. We might find some answers there.

[RishikaBhatia17]

I have followed the local environment setup instructions that were mentioned in the documentation. I have got all the Google Cloud Platform related keys and pasted them in the local settings.
Then, I have started the process to request for an OAuth client using Wikimedia:OAuth by filling the following form: https://meta.wikimedia.org/wiki/Special:OAuthConsumerRegistration/propose
In the 1st try, I have set the MediaWiki OAuth Callback URL as http://127.0.0.1:8000/ (Local host) and I was facing a problem while running the application
In the 2nd try, I have set the MediaWiki OAuth Callback URL as https://tools.wmflabs.org/google-drive-photos-to-commons/upload/? (Choose Photos from Google Drive button page) and I have got both the keys.
Then I have pasted the keys in local_settings.py file and then I have Run the Django standard runserver. Now I'm able to upload the file to Wikimedia commons from google drive successfully as shown below.

Also, I have used the dev keys as given in the https://phabricator.wikimedia.org/P10014
The only keys I have changed are the OAuth client using Wikimedia:OAuth because I felt there was a mistake in the callback URL.
I'm also able to upload images multiple times.
Hence I would request you to generate new OAuth client using Wikimedia:OAuth by setting the MediaWiki OAuth Callback URL as https://tools.wmflabs.org/google-drive-photos-to-commons/upload/? (Choose Photos from Google Drive button page) and paste both the newly generated keys in local settings.py and run the tool and test it.
So, I feel that the solution for the primary bug is found out now and it would be a great help if you can test this method and let me know.