App should open and display the Cat article
App opens and displays the original article in step 1
App version: 7.5.6 (3787)
OS versions: 17.5.1
Device model: iPhone 12 mini
Device language: EN
+6 more reports from iOS support
Examples
Every time I open the app after a period of inactivity or force closing it, it’s opening on the article for Reefer Madness. I’ve forced closed the app, gone back to the home page, and restarted my phone, but it still occurs. I believe this only started happening since updating to iOS 17.6.1 yesterday, as I believe I had viewed that article shortly before or shortly after that update.
Version: WikipediaApp/7.5.6.3814 (iOS 17.6.1; Phone)
Whenever I close out of the app and open it back up, it takes me back to the last article I read. I don’t know if this is a feature or a bug, but probably the latter. Could you please look into this issue? Thank you.
If the app is not running at all (I don't know quite when that happens on iOS, but certainly when it has been actively nuked), then following a link from (say) a search which should open the app opens it ... but at the page it was showing before it was killed. This is unuseful, and previously did mot happen.
@Tsevener This issue is not occurring for me on 7.5.7 (3876). I am seeing it on 7.5.8 (3879)
Working well for me as well on 7.5.7 (3876). This was also affecting Widgets opening (just saw a more recent support email), and it is also appearing fixed for Widgets.
A comment from one of our users:
I figured out that if I’ve been on the App, previously, I need to click on Explore to go back to the beginning.
Then I click on the respective link in my browser, either Safari or Google, and it works for me.
Therefore I’ve found a way around it.
Thanks for resolving this so quickly. Fixed in public 7.5.7
I find it surprising something like this got past automated or manual testing, so hopefully there's a new test to check for it?
It's a pretty understandable testing miss, because the condition to trigger it involves using the app, leaving it in a specific state, then not using the app for a bit, then returning to the app in a specific way.
Admittedly, QA people are exactly the sort who might think "but what if I force-quit the app in-between every action I might want to take with it?", but probably more as an occasional random deep trawl for bugs rather than as standard practice. 😂
@Flicky1984 & @DLynch Yes, we will add a test to cover these specific steps in our existing deep-linking tests.