KT Walrus

Yes they are. And in full disclosure, I have a large amount invested in this company as I see them eventually becoming very large and taking significant share of the cloud storage market away from Amazon S3. Backblaze B2 is significantly cheaper to use especially since AWS charges such high egress fees to deliver content to end users.

Please consider adding a separate Backblaze B2 storage method. The existing S3 method doesn’t completely work. B2 is very cheap at $5/TB and when combined with free Cloudflare CDN, B2 has NO egress fees So, all you pay is $0.005/GB stored Using Cloudflare Workers, you can even make the whole bucket private. Making a separate storage method for B2 will allow you to fix the small issues with using Amazon S3 method so B2 works completely.

Found this thread on the topic. One developer posted a work-around by using event.notification.tag in the notification click handler. https://developer.apple.com/forums/thread/726793

Wait a few weeks and all browsers on iOS will have “Add to Home Screen” in their Share menus. Edge already supports installing PWAs. Apple added an API for this with the latest iOS update.

Maybe you have a bad "Friendly URL" installed (in a third-party add-on?) that tries to match all query strings? This would cause an infinite redirect as the FURL would keep redirecting to itself. If you don't have any third-party add-ons, nevermind... Anyway, just a thought.

Is it possible that this is a bug in the Service Worker in the app and not a bug in iOS? I don’t understand why it sometimes works and most times it doesn’t work.

I’ve been using the PWA full time on my iPhone since updating to iOS 16.4. Seems to me it would be much better UX to have a fixed bottom menu bar like most apps on mobile have. My suggestion is to have these icons in a bottom bar: Forums/Notifications/PMs/Search/Account Maybe Unread also Could change Forums to Home but I don’t like that Home on this website doesn’t go to Forums. Could allow customization of the bottom menu bar in Account Settings.

I didn’t work just now with the notification of your reply. So, I don’t know why the links worked yesterday and not today. I think you will have to submit bug reports for your PWA. I’m not an Apple developer.

It didn’t work this morning. Looks like if you have recently been using the PWA, it works and if you haven’t it doesn’t work. So, an iOS bug. Do you know how to report bugs to Apple?

This appears to be working now. Did you fix anything on your side? Maybe it is working now for me since I was in the PWA a few minutes before tapping on the iOS notification. Not sure what will happen if I don’t use the PWA for a couple days and then tap an iOS notification.

Maybe the solution to the navigation issues I’m having is to treat all topic links as external links. Try an external link in the PWA: https://dev.to/chicio/implement-a-pull-to-refresh-component-for-you-web-application-1pc If links to content were treated like the link above, it would be natural to return to the list of topics. Problem now is you can view a topic from a number of different lists, e.g. forum, search, activity, profile, etc. Having to use the Forum button to navigate back to the referer link only goes to the enclosing forum. Anyway, there is much that could be done to make navigation within the PWA better.

Just noticed the Twitter PWA has the browser controls (back/forward/refresh/share) and still manages to support push notifications. The notifications even turn on a badge on the Twitter PWA home screen icon. Maybe you can do something similar? The Twitter PWA seems to be much more useful than your PWA as far as navigation is concerned. Note the Twitter PWA prompted me to turn on push notifications while I think I had to visit Notification Settings on my own in your PWA.

I’ve tried the Twitter PWA and it has the same problem. So, probably nothing you can do to set the app title. Maybe check the manifest schema that iOS currently supports and if there is no manifest setting for this string, wait until Apple addresses this issue.

FYI. Here is a link to one article I found on implementing swipe down for refresh in PWAs: https://dev.to/chicio/implement-a-pull-to-refresh-component-for-you-web-application-1pcg

That button isn’t the same as a back button. I’ve been trying to use the PWA full time, and the missing back button is a major usability problem. Push notifications don’t work with minimal api. Only fullscreen and standalone. Apple wants to encourage PWAs to work more like native apps than Safari websites. Therefore, back/forward/refresh are actions that the PWA has to address in the PWA UI.

I’m testing the Invision Community PWA on iOS today. I ran into several usability UX issues including no reload/refresh button on the pages here. I think there are at least one page here that is being cached in the PWA. And I have no ability to refresh the cached page. If I visit the same page in Safari, I get the updated page since reload button is always available in Safari. In Safari I can swipe down to reload but not in PWA. Second theme issue is missing back button in PWA. I can swipe right for back in PWA, but swiping right is often hard to get interpreted as “back” in both Safari and the PWA. I think it might be a theme issue since on other sites I use, swiping right works every time. This may have something to do with the page margins or the wrapper. So, placing a back button on every page would be better UX. Note you could only show the back/reload buttons if in PWA or maybe only if full screen.

The link back to the PWA uses “untitled” as the app name when opening the link with an external app. Perhaps the manifest is missing an app title attribute? Here is a screenshot when opening with Chrome from the Invision Community PWA: Here is opening the same link from Safari:

Changing setting to from once a day email to immediate didn’t do anything. When I tap an iOS Invision Community notification, it doesn’t redirect to the new topic. Am I the only one seeing this behavior?

So, you are saying when you tap a notification for a new topic, the PWA opens the topic? Maybe my issue was only for followed forum notifications? Or, maybe since I was in the PWA just minutes before receiving the push notification and the PWA was still running in the background, that it didn’t process a redirect to the new content? It definitely didn’t work as I expected. I’ve only had that 1 push notification so not sure if this issue is just a one time glitch. Just noticed the setting for one email a day was checked so maybe the notification was for a digest email and not an immediate notification? Maybe need to link the iOS notification to the first topic in a digest email notification if digest is for only 1 topic?

So, you are saying when you tap a notification for a new topic, the PWA opens the topic? Maybe my issue was only for followed forum notifications? Or, maybe since I was in the PWA just minutes before receiving the push notification and the PWA was still running in the background, that it didn’t process a redirect to the new content? It definitely didn’t work as I expected. I’ve only had that 1 push notification so not sure if this issue is just a one time glitch.

Updated to iOS 16.4. Enabled push notifications in Invision Community web app. Received a notification about a new topic in a forum I follow. Tapped on the iOS notification on the lock screen on my iPhone. This opened the PWA but didn’t redirect to the new topic like tapping on the notification in the notifications list. The last page I had viewed before was still being shown. Is this a bug?

How long does the PWA keep me signed in? Also, can you support sign in by Face/Touch Id? And, will Badge show on the HomeScreen icon to indicate the number of unread notifications or even just unread PMs?

CKEditor 4 is EOL by the end of 2023, it seems. Invision should be prepared to deprecate CKEditor 4 sometime in 2023. Since CKEditor 5 is very different than CKEditor 4, I think Invision should release a beta of CKEditor 5 in an upcoming release with CKEditor 4 being the default editor. An ACP setting should be available if a site wants to switch to the beta CKEditor 5 early. This forum could switch to CKEditor 5 as soon as possible to help get any integration problems addressed early.

I did upgrade to 4.7.3 and these deprecation errors were not fixed. Unless, you slip in minor fixes to the release, I should be using the latest version. The fixes are trivial.

Didn't get any response so reposting here: