List of uploaded photographs not refreshing when uploaded via desktop/laptop

[Suyashdwivedi]

Summary

The Commons Mobile Application fails to refresh the list of uploaded photographs when new images are uploaded via desktop or laptop.

Steps to reproduce

1. Upload a new photograph using a desktop or laptop.
2. Open the Commons Mobile Application on my Android device.
3. Navigate to the list of uploaded photographs.
4. Observe that the newly uploaded photograph is not visible in the list.
5. Log out of the app and re-login.
6. Navigate to the list of uploaded photographs again.
7. Observe that the newly uploaded photograph is now visible in the list.

Expected behaviour

The list of uploaded photographs should refresh automatically to reflect new uploads from any device, including desktop and laptop.

Actual behaviour

Device: Android mobile

Device name

Oppo F11

Android version

Android 9.0

Commons app version

5.1.0

Device logs

No response

Screen-shots

No response

Would you like to work on the issue?

None

[nicolas-raoul]

Would you mind trying when building the latest main branch?

[parneet-guraya]

Actually you don't need to logout, just clear the app from memory and open it again, it will trigger the refresh and show you, but we recently added pull to refresh too. I'm not entirely sure what strategy to use to automatically refresh. Maybe trigger it every n time & also every time you visit the screen. But we can have it for sure.

document_6302998381010621591.mp4

Also pull to refresh works.

document_6302998381010621590.mp4

[Sujal-Gupta-SG]

@nicolas-raoul
I think we can call the refresh function or method after adding new post everytime ,maybe this situation get satisfied , we donn't need to clear the cache or clear the app from the memory, it will automatically get triggered when the new post get added .
@nicolas-raoul If you say i want to work on this issue

[Suyashdwivedi]

I think that can help :) *Best Regards,* *Suyash Dwivedi *(He/Him/His) *Vice-Chair**:* Wikimedia Affiliations Committee <https://meta.wikimedia.org/wiki/Affiliations_Committee> (AffCom) *Chair:* Commons Photographers User Group <https://commons.wikimedia.org/wiki/Commons:Commons_Photographers_User_Group> (CPUG) *Skype*: suyash.india (UTC+05:30) *Telegram:* dwivedi_suyash <https://t.me/dwivedi_suyash> *"Imagine a world in which every single person on the planet is given free access to the sum of all human knowledge. That's what we're doing." - **Jimmy Wales*

…

On Thu, Jan 2, 2025 at 8:30 PM Sujal ***@***.***> wrote: @nicolas-raoul <https://github.com/nicolas-raoul> I think we can call the refresh function or method after adding new post everytime ,maybe this situation get satisfied , we donn't need to clear the cache or clear the app from the memory, it will automatically get triggered when the new post get added . @nicolas-raoul <https://github.com/nicolas-raoul> If you say i want to work on this issue — Reply to this email directly, view it on GitHub <#6084 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AISAVBDX2PZKMKAYN2NBUYT2IVH77AVCNFSM6AAAAABUHULBROVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRXHEYDKMZSGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Sujal-Gupta-SG]

i want to work on this issue ,can you assign this issue to me ,so that i can make the changes as soon as possible

[nicolas-raoul]

I don't think the Commons website can "push" to our app a signal that a new file has been uploaded.
We can "poll" from time to time, and load the new files if there are any, ideally without refreshing the ones that are shown already.

For this issue, the most important is to keep network usage and Commons server resources usage very low.

[nicolas-raoul]

How about this:

• When opening the app, in the background (without any UI impact such as loading spinwheel) we check whether the server's last image is the app's last image.
• If not, refresh.
• New "refresh" button having the same effect as swipe down.

[neeldoshii]

When opening the app, in the background (without any UI impact such as loading spinwheel) we check whether the server's last image is the app's last image.
If not, refresh.

Whenever an app is reopened, I believe new contribution are loaded since it fetches the data and new data is updated.

As per this comment #6084 (comment) the newly data is loaded successfully after loading the app again.

wdyt?

[nicolas-raoul]

Whenever an app is reopened, I believe new contribution are loaded

Would you mind actually trying?

1. Stop the app.
2. Upload a picture via the website.
3. Open the app.

[nicolas-raoul]

Note: I meant trying on the main branch.

[Sujal-Gupta-SG]

Note: I meant trying on the main branch.

How about this:

• When opening the app, in the background (without any UI impact such as loading spinwheel) we check whether the server's last image is the app's last image.
• If not, refresh.
• New "refresh" button having the same effect as swipe down.

So what should I do now:
should I make some changes to my pull request according to your idea or should I wait for new idea

[Sujal-Gupta-SG]

Note: I meant trying on the main branch.

How about this:

• When opening the app, in the background (without any UI impact such as loading spinwheel) we check whether the server's last image is the app's last image.
• If not, refresh.
• New "refresh" button having the same effect as swipe down.

So what should I do now: should I make some changes to my pull request according to your idea or should I wait for new idea

Hey @nicolas-raoul
Give a reply ,So that I can resolve this issue as soon as possible

[nicolas-raoul]

Sorry for the delay, I would suggest a new pull request.

[Suyashdwivedi]

Another issue "error fetching notifications" on clicking bell icon Regards, Er. Suyash Dwivedi (pronouns - he/his/him) (U:Suyash.dwivedi) Member: Wikimedia Affiliations Committee ***@***.*** IST (Indian Standard Time) UTC+5:30 --Sent from my mobile device

…

On Sun, Jan 19, 2025, 20:27 Nicolas Raoul ***@***.***> wrote: Sorry for the delay, I would suggest a new pull request. — Reply to this email directly, view it on GitHub <#6084 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AISAVBD7CQ4JDMIIBYWHHPL2LO4NBAVCNFSM6AAAAABUHULBROVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBQHA4TINRXHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>