ios 18.0 (beta - test at own risk) quine save not stable

[maki aea]

hi chris!

ofc i realise it's because of the beta :)

just to let you know saving (even a new tw 5.3.3 initiated from quine) is unstable when running ios18.0beta on iphone 15 pro

my old 5.3.1 tw saves sometimes and not others

the 5.3.1 tw save still works fine on rclone serve webdav still on a mac (haven't put any macos betas on that mac, but have tested safari technology preview Release 196 (Safari 17.4, WebKit 19619.1.16.3) which works fine with rclone serve webdav to save still)

so it looks like this issue is a ios18.0beta issue (possibly something to do with safari 18 beta (20619.1.15)); hopefully upcoming ios betas might solve this

maybe there is a clue somewhere in the safari 18 beta release notes https://developer.apple.com/documentation/safari-release-notes/safari-18-release-notes

warmest wishes, maki

[maki aea]

discussion on talk.tiddlywiki https://talk.tiddlywiki.org/t/ios18-0-beta-issue-poss-safari-18-tw5-3-4-seems-ok-but-tw-5-3-3-tw-5-3-1-affected/9958

just quickly tried tw5.3.4prerelease and from initial tests it seems to save fine on ios18.0/quine -- hopefully it is stable throughout and users can just update to that for a fix

[maki aea]

unfortunately on further testing 5.3.4 also has saving problems that weren't evident on first few saves.

saving does seem to happen eventually, after many seconds, accessing a different file from the "<" menu also takes many seconds to work

maybe it's not a quine issue at all but rather some files/icloud bug as the save does seem to go through just very slowly

[Quine]

Hi Maki,

Thank you for letting me know. I've not loaded iOS 18 yet,  the early betas really are betas, and the times that I've jumped in early I've ended up chasing my tail, made worse by beta performance. The same is usually true of the development tools, so coding and debugging can be a big frustration so early.I'll watch closely though and start testing as soon as 18 seems stable enough to load - but please do let me me know if/when/as you see changes - good and bad ;-)

Thank you! - Chris.

[Jeremy Ruston]

Hi Chris

Living dangerously, I'm running iOS beta 1 on my iPad, which is set up as a development device on Xcode on my Mac. I can replicate the fault. I'm very inexperienced with Apple developer tools, but is there anything I can do to retrieve useful debug information that I can post here?

Best wishes

Jeremy

--

Jeremy Ruston

On 14 Jun 2024, at 05:18, Quine <quin...@googlegroups.com> wrote:

Hi Maki,

--
You received this message because you are subscribed to the Google Groups "Quine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quine-app+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/quine-app/1f88a09e-659e-47b0-bfd5-53f7843ac182n%40googlegroups.com.

[maki aea]

beta 2 (from 20240624), from limited testing, seems to resolve this issue!

[Quine]

Great - thanks for the update  Maki. Meanwhile I've been resurrecting my Quine 3 project and getting it ready for Swift 6.0. The most recent WWDC was heartening in many ways, most especially because a lot of the core iOS plumbing didn't change much, instead stabilizing after a handful of big jumps over the past few years. I've been hoping for such because it gets exhausting having to refactor my core code year after year. Quine 3 is a major rewrite onto libraries I've been using for a couple of years on other projects, I started it in 2021 so there is work to do, but it at least feels durable as well as current from a coding perspective. We shall see.

Chris.