jQuery Forum

Hoping someone would have some insight. Not even sure where to point Google to an code issue and I am sure they are not going to be too interested in pursuing an issue with JQM at this point in its life cycle, especially if I cannot point to the specific code issue.

Feel free to report an issue at Issues · jquery/jquery-mobile, but don’t hold your breath.

If you can make a tiny demo that we can visit in IOS Safari, we can take a look. Please keep it simple without extraneous code/html.

Plunker Is a good place to make JQM demos.

Can you rearrange your pages so that you don't have to use "back", but use an explicit URL instead?

I went to make a sample app to demonstrate this effect and could not get it to perform badly. So I went back and update the production app to the new version number of Google Maps again (only change) and it won't fail either. Again others have tested it and reported they could not get it to fail too.

How is this even possible?  I don't think Google could or would change a piece of code that was not in beta.

I hope you use Git, (or some other version management software) to manage updates to your code. It sounds like perhaps you don't, though. If you had, then you could easily discover what is different. If you "live update" your site or app, then you will not  know if you "fat-fingered" something. (Accidentally changed something other than the Google Maps API version.)

When I ask "did anything change" I mean did ANYTHING change? Not just your code. What about content? What about the user environment? (OS update, different computer, etc. etc. etc.) Did it ever fail for anybody but yourself?

Complicated software is complicated. Causes of problems are often not found in the obvious places. That's why making a simple example or test case often helps find the problem. If you make a simple example, and it does not fail, that means the problem (may) lie somewhere else (or at least the addition of something else causes it to be manifested). You can then continue to partition the problem, perhaps by re-introducing features one by one, or taking the opposite approach of removing code until the problem goes away.

I agree that Google shouldn't/wouldn't change a piece of code that is not in beta - and even in beta they would change the version number. But perhaps it happened. Google probably has a blog about the Maps API, and/or some forum, where you can check.

Did you think to clear the browser cache at any point? Google (and you) should use "cache-busting" when you make changes. But, still, it's always a useful exercise. Of course, you shouldn't have to ask your users to clear the cache. But it is a useful debugging step.

Were you running a beta Safari? I do often, and things break. Then they repair after an update to a new beta.

After this behavior to test the caching theory I also made a tiny UI change too in the app so I could tell that it was not stuck between edits.

I tried doing a dynamic loading of Google Maps API and that actually made matters worse.