Does this version also update the Ouch version with the audit fix?

I believe they just fixed this: https://github.com/quorrajs/Ouch/issues/16

I will try that, thanks!

OMFG!!! I have a solution!!!

1. I add a check for versionstring on the server, and return it to the app.
2. I look for it in localtstorage (IndexedDB) and if I don’t find it, I add it. If I do find it, I compare versions and if there is a newer one on the server, I throw up a dialog.
3. Dismissing this dialog (my ok button is labeled “update”) runs window.location.reload(true) and then stores the new versionstring in localstorage

RESULT: My app is updated!! I have been searching for a way to do this for weeks and weeks, so glad it finally works on iOS. Hope this helps someone else.

UGH nevermind…I had accidentally added ‘Dialog’ to COMPONENTS list instead of PLUGINS list!

I don’t know why I am getting this error (and no dialog showing), any suggestions?

1. I have verified that I added the component 'Dialog" to the list in quasar.conf.js
2. I am using this code to call it:

this.$q.dialog({
                title: 'Confirm',
                message: 'There is a new version available. Your version will be updated.',
                ok: 'Update'
              }).then(() => {
                window.location.reload(true)
                this.$setItem('myapp_version', this.curVersion)
              }).catch(() => {
                alert('Houston...')
              })

Is there something wrong or missing? Why would I get that error? I am using latest Quasar ( CLI v0.17.15 and Framework v0.17.12)

I notice modals have properties “minimized” and “maximized”, but how can I apply one to mobile views and another to desktop (or other size) views?

It is really a shame. And a search around the web has very little information of this type (ie clear descriptions of what is and is not supported), and no word from Apple on when or if they will ever support the missing pieces. My guess is they will not unless there is a huge outcry, for exactly the reasons you mention (ie they won’t make money from it).

@mesqueeb Oh I see what you mean. Yes in fact, I am taken back to the homepage, but because everything is cached, all info on that homepage and other pages (and of course what I am storing in IndexedDB) is still the same, ie no new version or page changes are downloaded, despite being directed to the main page on every PWA launch/load. So other than a navigational inconvenience, it still won’t check for new version of PWA.

@mesqueeb I am curious what you mean about “keeps refreshing the app every time you open”, because this definitely does NOT happen in my PWA on iOS (unless I have something else wrong with it like an invalid cert or mismatched domain). In my testing, I had actually mistakenly thought refreshing was fixed because it seemed to be getting the latest version but then realized my test domain was invalid and thus was never operating as a PWA anyway. Once i tested back on the valid domain it went back to caching all the time. As I said above, the only way I have found to get my PWA to refresh is to paradoxically clear the SAFARI cache. (which obvi makes ZERO sense to a user or anyone else).