Thanks for the report and the repro file.

I’ve tried to reproduce this issue using your repo.html on multiple devices and iOS versions (iPhone 11 Pro running iOS 17.7 and iPhone 17 Pro running iOS 26.2), including backgrounding the app and running GPU-heavy workloads while Textastic is in the background. On return to Textastic, the WebGL2 content either continues rendering normally or the HTML viewer is reloaded by iOS, after which the animation runs again. I have not observed a case where the WebGL2 context is lost and never recovers.

I also verified that explicitly forcing a WebGL context loss and restore (using WEBGL_lose_context) works as expected.

So far I’m unable to reproduce the “context lost and never recovers” behavior you’re seeing. This may be specific to a particular device / iOS version combination (for example the iPhone 13 mini on iOS 17.6 mentioned in the report), or a WebKit issue that no longer occurs on newer iOS releases.

If you’re still able to reproduce this reliably on current hardware or iOS versions, additional details (device, iOS version, exact steps) would help investigate further.

Textastic 10.9 adds support for exporting and importing remote connections (SFTP, FTPS, FTP, and WebDAV).

Connections can be exported to a JSON file and imported on another device. This makes it easy to move your complete connection setup between devices, keep backups, or keep multiple devices in sync manually.

Passwords can optionally be included and are encrypted with a passphrase.

While this is not automatic background syncing like some apps provide, it significantly reduces the effort required to keep connection lists consistent across devices and avoids having to recreate connections by hand.

You can find more information including file format documentation and example files in the manual at:

https://www.textasticapp.com/v10/manual/remote_servers/export_import.html

Textastic 10.9 now supports exporting and importing remote connections (SFTP, FTPS, FTP, and WebDAV).

Connections can be exported to a JSON file and imported again on the same or another device. Passwords can optionally be included and are encrypted with a passphrase.

While Textastic does not directly import Transmit’s proprietary export format, the JSON format is documented and designed to be editable by hand. This makes it possible to migrate or recreate existing connection setups with relatively little effort.

This should significantly reduce the work required when moving a large number of connections into Textastic.

It looks like when the search encounters "document.", it's not recognized as a full word.

Thanks for letting me know, I'll try to find out what's going on.

Thanks for letting me know about the issue!

This is fixed in Textastic 10.8.6 which was released today.