I primarily use the PWA when visiting this site using an iPhone 16 Pro Max.

There are several theme usability issues that would be obvious to anyone using the PWA for a couple of days.

Please have your devs spend time on testing out the UX specifically on the iOS PWA before releasing the v5 GA.

Specifically, I am unable to post using the PWA so I’m posting this in Safari. I think I might have taken time to report this one bug already, but almost every time I use the PWA I see issues with the theme that I simply don’t have the time or energy to report.

A good week of thorough testing of the PWA would be very welcome by me as I intend to enable the PWA for my upcoming v5 site and it is important to me that the UX be as good or better than using a browser.

The issues are undoubtedly from Webkit in the PWA being several releases behind Safari and your devs using Safari or Chrome and not the PWA for testing.

I‘m not having any issues to reply with PWA, the editor loads fine for me.

There must be something else going on. What iOS version are you using?

6 minutes ago, Daniel F said:

I‘m not having any issues to reply with PWA, the editor loads fine for me.

There must be something else going on. What iOS version are you using?

18.2.1 (the latest version I think).

Maybe there is a JavaScript exception preventing the keyboard from appearing to input text?

I do have the fastest iPhone and I think this prevents me from seeing edits to posts unless I force a page reload to see the changes.

So, maybe the issue is only on very fast iPhones where there is some sort of asynchronous JS that gets handled out of the usual order sometimes.

I did notice that around 10% of the time I can see edit changes without reloading making me think that some of my PWA UI issues are JavaScript related and maybe hard for you to reproduce?

This is what Claude says to see JavaScript exceptions on my iPhone. I’m not going to take the time to do this, but maybe this would explain what I’m seeing, if this works for debugging a PWA.

Claude 3 response via duck.ai

To see JavaScript exceptions in Safari on your iPhone, you can follow these steps:

1. Enable the Develop Menu in Safari: Go to Settings > Safari > Advanced and turn on the "Develop" menu.

2. Connect your iPhone to your Mac: Use a Lightning cable to connect your iPhone to your Mac.

3. Enable Web Inspector on your iPhone: On your iPhone, go to Settings > Safari > Advanced and turn on "Web Inspector".

4. Open the Web Inspector on your Mac: On your Mac, open Safari and go to the "Develop" menu (which should now be visible). Hover over the name of your connected iPhone, and then select "Show Web Inspector".

5. View JavaScript Exceptions: In the Web Inspector window, you should see a "Console" tab. This is where you can view any JavaScript exceptions that occur while you're using Safari on your iPhone.

When a JavaScript exception occurs, it will be displayed in the Console, along with information about the error, such as the line of code where the exception occurred and the stack trace.

Keep in mind that the Web Inspector feature is primarily intended for web developers, so it may not be the most user-friendly way to view JavaScript exceptions for non-technical users. However, it is the best way to access this information on an iPhone.

I know I said I wasn’t going to do this, but I did and the Web Inspector console shows no exceptions when replying to this topic and the keyboard doesn’t pop up to enter text into the editor.

Here is a screenshot of the console:

I’m trying editing a reply to see if that throws an exception.

Here is my edit.

This edit showed up this time.

It is working every time when the Web Inspector on my Mac is connected.

Maybe this bug really is a timing issue with very fast iPhones.

Disconnecting cable to MacBook Pro for this edit.

Yes. With the cable disconnected I don’t see the edit until I reload the page.

This last one worked while the previous one didn’t.

Edited 2 hours ago2 hr by KT Walrus

Maybe this timing bug is related to the size of the reply. Trying one more time with a short reply.

Here is my edit.

That failed to show.

Here is a longer edit:

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

That failed to show either. Maybe this will show up?

Nope. Didn’t show up either so theory about size of post is wrong. Maybe it really is a timing bug that can be avoided when cable is connected to MacBook Pro web inspector console.

Connected to Mac for this edit.

That showed up kind of confirming it is a timing issue.

Edited 2 hours ago2 hr by KT Walrus

Does this site use web sockets?

I’m seeing some connection errors when switching between the PWA editor and the editor in Safari on same iPhone.

Here is a screenshot:

Doesn’t matter which way I switch. Either to or from Safari from or to the PWA. I suppose web sockets aren’t shared between two processes. Still, I think the JavaScript should try to connect to a new socket if the current socket goes wonky. Maybe I just needed to refresh the page though to get a new connection.

This might be a DDOS vector for overwhelming the Invision Cloud service.

I don’t think this happens with my Laravel app but I am no longer experimenting with Web Sockets in Laravel any longer.

Edited 2 hours ago2 hr by KT Walrus