Not only with the “back” button in a browser, but also with a “link:back” action in the app.
If you would like to investigate, please find a clonable app here (I’ve posted the link above as well)
It illustrates the problem quite clearly. Try to use “back” button in the app, and see how ID is not changing (for example, when going back from screen 5 to screen 4), and then changes (back from screen 4 to screen 3). Also see how it works with “back” browser button.
“Form resubmission” doesn’t work in this scenario anyway - there is no form :).
The workaround in a mobile app is to “connect” desired actions not to On-Screen-Enter event, but to pressing “back” button event on the next screen.
But this doesn’t solve the problem of browser’s “back” button, as nothing is “connected” to it. And it is very difficult to change users’ habits of pressing this button.