In T264474#8454418, @Ragesoss wrote:

I tested this on the example from above, the track listing table from https://en.wikipedia.org/wiki/Renewal_(Billy_Strings_album), but it isn't fixed even after purging the cache, making a null edit, or previewing the table with a non-null edit.

It sounds like this might be a duplicate of T305383?
I noticed that the above task is closed, but the last comment from Anthony is that it's still reproducible.

My only guess so far would be some kind of weird cached version of that article stuck in the app's browser cache. Would you be able to try clearing the app's cache, and trying again? (go to "App Info" -> Storage -> Clear cache)

hmm, that's definitely not the expected behavior, and not reproducible for me. (tapping the image should just take you to a full-screen view of the image.)

Click "Read article" (why is it called that when you click an image, btw?)

In T324308#8438946, @Imran99886 wrote:

In the Wikipedia Android app, no image opens in any article.

@ARamadan-WMF This needs quite a bit more detail. Which wiki is this on? Which article? Which image in the article?

I'm afraid we can't do much about this. When displaying system-level notifications, we have very little control over their layout and design. (The design of these notifications also changes from one version of Android to another, and also varies from one manufacturer to another!)
There's simply a rough guideline from the Android documentation to keep the action text short, so that it doesn't overflow or become ellipsized.

[will be tested indirectly by the Receiving workflow of sharing reading lists]

In T321485#8414722, @ABorbaWMF wrote:

This one was not working for me on 2.7.50423-beta-2022-11-16

I see, in that case this is probably a duplicate of T70299, closed in 2015 (!) and still as technically prohibitive as it was then.

@ARamadan-WMF As far as I can tell, both Android and iOS already support this language (ku and ckb). Can you clarify what needs to be done here?

In T323237#8406452, @Sharvaniharan wrote:

So far I have checked that we are sending events properly on the app side.

I've confirmed that new events are coming in, which contain proper latency information.
Please refer to my comment on the schema talk page for important considerations.

We now show a warning when the user is entering text in the wrong language.