Your comments
I've spent the last hour trying to reproduce the issue:
- 13" M4 iPad Pro running iPadOS 26.1
- Using Stage Manager
- Secure ShellFish connection added as external folder to Textastic
- Textastic window open with two files from the external folder
No matter what I did (changing stages, opening new windows, forcing memory pressure), the two files stayed open for me.
So if you have specific cases that trigger the problem, please let me know. For now I could not reproduce the issue, sorry.
Thanks for the screenshot.
So it happens on an external monitor and when you switch from one stage back to the stage which contains Textastic's windows?
I'll try to reproduce it. If you can tell me specific steps that cause the problem, that would be helpful.
That said, I haven't changed anything regarding window restoration recently and Apple is currently changing a lot regarding multitasking, so this might just be a bug in iPadOS 26.
Without seeing what you are doing exactly, it's hard to tell what might be going on.
Are you sure you are not closing the window accidentally or opening a new, empty window?
For example, if you use the red X button, the window is closed and opened files are not restored when opening Textastic again. In this case, a new window is created when returning to Textastic.
What happens if you show the context menu of Textastic's app icon (right click or tap and hold) and select "Show All Windows"? (You can also use Window > Show All Windows in the iPadOS menu bar).
"Show All Windows" shows all windows that can be restored.
Does it maybe show the window with the files you are looking for?
If the window with the files is indeed gone and you can reproduce the issue, it would be great if you could send me a screen recording video.
I can confirm that the accessibility setting currently doesn't seem to be honored.
Textastic actually uses the standard system text selection and insertion point (UITextInteraction), so any system accessibility settings should be respected.
I'll try to find out what's going on. Thanks for letting me know.
SMB connections in the Files app have been very unreliable for me in the past.
It works fine immediately after connecting to an SMB server, but as soon as it gets disconnected, it won't reconnect reliably. You need to recreate the SMB connection in the Files app and add it to Textastic again to make it work again when it is in this state. This is something out of my control that Apple has to fix.
I wouldn't recommend using SMB shares with the Files app. I have seen the problem you are describing as well as hangs when using the iOS Files app's built-in SMB client (not related to Textastic, reproducible in other apps like iA Writer). Instead, I recommend to use Textastic's built-in SFTP client:
https://www.textasticapp.com/v10/manual/remote_servers/sftp_ftps_ftp.html
If you need live editing, I can recommend the app "Secure ShellFish" which allows you to connect to SFTP servers from the Files app and works great with the external folder feature of Textastic (the app's "Pro Unlock" is required for uploading changes):
https://apps.apple.com/de/app/ssh-client-secure-shellfish/id1336634154
You’re welcome. Just let me know if you have any other questions.
Hello,
when you cancel the subscription and the trial expires after one week, you should be able to get the one-time purchase of Textastic Pro. In Textastic, go to Settings -> Textastic Pro and you should either see the paywall or your current subscription status.
This is fixed in Textastic 10.8.3, which was just released.
Customer support service by UserEcho
The "Prefer Non-Blinking Cursor" accessibility setting will be supported in Textastic 10.8.5.
The problem was a workaround I had implemented for a problem on iOS 17 where the cursor didn't start blinking right after tapping the editor. So I forced the cursor to blink on iOS 17 and later. In my testing I found out that this is not necessary anymore on iOS 18 and 26 and that the workaround did interfere with the new accessibility settings introduced in iOS 18.
Thanks again for reporting this problem!
The update is currently in beta testing and is going to be released within a week.