Textastic only adds a row above the standard iOS keyboard. To make this available in all apps, I would need to provide the full keyboard. It's not possible to just add a row like I can in my own app. This means I would need to re-implement the standard iOS keyboard, which I don't think is feasible.

Textastic already starts a background task when you switch to another app which should keep the connection alive for about 30 seconds on iOS 13 (on previous iOS versions, the OS granted longer background execution times).

Other apps solve this by using background location tracking - this API is primarily meant for navigation apps, so they can provide turn-by-turn instructions in the background. But, apps like Prompt and Working Copy ("mis-")use it as a "connection keeper" feature that gives you a history of locations where you connected to remote servers with the side effect of keeping your connections alive.

On iPad you can also put two apps side by side or in a slide over window to keep Textastic running.

Mosh is licensed under the GPL, which means I would need to make Textastic's source code publicly available which I don't want to do at the moment.

Can you please share the file with me so I can try to reproduce the issue on my device?

Textastic 9.3 adds a new “Line Height” setting that you can use to adjust the spacing between lines (defaults to 110%).

Textastic 9.3 adds the new setting “Indent Based on Syntax”: Automatically indent code when typing, based on its syntax.

For example, increases the indentation when pressing Return after an opening curly brace (“{”) in C or an opening tag in HTML and decreases indentation after a closing curly brace (“}”) or a closing tag.

Textastic 9.3 adds the new keyboard shortcuts “Toggle Comment” (Cmd-/) and “Toggle Block Comment” (Cmd-Option-/).

Textastic 9.3 has the new setting “Close Brackets and Quotes”: Automatically inserts a matching closing character when typing an opening bracket or quote. 

This works for the following character pairs: "", '', (), [], {}.

Thanks you for your report. This is already fixed in the development version and I plan to release it soon. I'm sorry for the inconvenience.

Thanks for letting me know, I'll fix this in the next update.