Why haven’t we see an update for iPad in 2 years?
Possibly because one isn’t needed?
Software doesn’t need to be like cars, a yearly ‘update’ and enlargement whether needed or not.
6 Likes
I was having issues with the style bar on my app, where if I wanted to highlight a text, the whole bar would crash. It’s not happening right now, so I’m thankful for that. Also, since two years ago, the iPad’s OS has updated considerably. You didn’t have to answer my post, RuffPub.
We are currently working on an update for the iOS version. It’s going to take a fair bit of effort because some of the core methods used to make the software will no longer be supported, and will have to be overhauled. The way in which split views are handled, for example, have changed quite a lot over the years.
As for the crash you experienced, if you can find a way to reproduce that, write it up as a bug report. I don’t think we have anything on file about that. The Formatting panel can disappear on the phone if you don’t have third-party keyboard support enabled, but this isn’t an issue on the iPad (it’s not a crash either, more just the panel vanishes the moment it appears). The main issue we’ve seen reported there is the Find and Replace tool not working well with external keyboards.
5 Likes
Didn’t have to, but chose to.
I’d assumed that at some stage there would be an update, but my point remains.
Too often we see yearly software updates that contribute little but bloat, et some expect it, just like the yearly car ‘bloat’ update.
1 Like
Thank you for that information.
1 Like
AmberV, your answer raised a question for me. In iPadOS26 they have finally implemented multiple instances of an app (if the app supports it). Is that one of the things that is going to supported in the update? Either in each instance handling a different project or different chapters in the same scene?
To my knowledge that capability has been around for a long time, they just changed the UI for it. Beneath that, nothing has changed about the fundamental problem with Scrivener supporting this: it has no architecture for opening the same project more than once, and given how iOS works in a somewhat “stateless” fashion, it would be very difficult to know if a project is already open. The latter, if it could be done reliably, is how we could implement this safely: if the project is open in another instance, then you simply couldn’t open it again, it would stop you (that’s how the desktop version works). Thus without that, we’d have to make that possible, and that would require a probably ground-up rewrite of an awful lot of stuff.
As for working with more than one thing at a time within a single project though, that has always been a feature.
2 Likes
I suspected that would be the case. Thank you.
1 Like
but in the meantime we continue to use iOS Scriv without any fear of losing data after the update…, isn’t it?
I don’t understand how this question arises from the previous one, and do not know how to answer it. So, just generally speaking, I would never use any software at all without fear of losing data. That is not a safe way to live one’s life, if the work they create in software is important to it. Always make backups, and then another backup, and then another backup you store some place else, and update them frequently.
3 Likes
I apologize, I refer to this sentence of yours… anyway beg your pardon…
No worries, I just didn’t understand the question, and it is best to ask for clarification if so.
What I mean by that is that the program will stop launching (or at the least, crashing when trying to use it) if you upgrade to the new OS without installing the upgrade to Scrivener that the quoted post speaks about. So to answer the question, there wouldn’t be an opportunity to lose data since it won’t run. 
1 Like
This seems like an appropriate place to mention our tips for keeping iOS Scrivener projects backed up: Guide to Keeping iOS Projects Backed Up / iOS / Knowledge Base - Literature and Latte Support
4 Likes