iPadOS 13.4.1

šŸ›Bugs
#1

Steps to reproduce

Starting from scratch, what are the steps to make the bug happen? The fewer the steps, the better.

Open and start typing

Expected result

What do you expect to see after carrying out the steps above?

Responsive typing

Actual result

Instead of the expected result, what happened?

Super laggy typing.

Environment

Which operating system are you using?
Which browser are you using?
If youā€™re using a desktop or mobile app, whatā€™s the version number of Dynalist?
Are you using any third-party scripts for Dynalist, e.g. PowerPack?

iPadOS 13.4.1 (the one with mouse support - yay)

Additional information

Anything else you think would help our investigation, like a screenshot or a log file? You can drag and drop screenshots to this box. For large amount of text, try putting them into something like Pastebin.

Additional comments

#2

Did this just start happening after you made an upgrade from an older version of iPadOS?

#3

Yes. I can confirm that I see the same behavior on my iPhone as well when upgraded to iOS 13.4.1

#4

Got it, weā€™ll upgrade our devices soon to investigate the issue, thanks for the report!

1 Like
#5

Iā€™ve updated our test iPhone to 13.4 17E255 (I canā€™t seem to find 13.4.1 as it says I have the latest update). Havenā€™t seen any issues with the app performance wise compared to before. Our iPad is updating currently, but only to 13.4 as well.

Iā€™m guessing 13.4.1 is a beta? I will test again once a new iOS version is released.

#6

I just tried again (and Iā€™m running on 13.4.1 on my iPad Pro). I see the same performance problem with my primary document. When I create a new document though, I donā€™t see the problem. My primary document is pretty big - 243KB compressed. Perhaps related to the length of the doc? Have you tried it against a large doc?

#7

Thatā€™s certainly a large enough size I would recommend avoiding on mobile, but if you say it worked fine on previous versions of iOS then thatā€™s still quite suspicious. Iā€™m upgrading our test device again to see if we can repro.

#8

Updated and still not seeing an issue so far. Were you able to test if the issue goes away when you split the document up into smaller pieces? Hopefully that can give us some clue as to what to look for.