with external keyboard command key acts like still pressed after command-c when using cursor keys

Hmm. I just tried to reproduce this, but for me it behaves as expected. 

Are you sure that you are not just pressing Cursor up when you are already pressing the Cmd key for Cmd-C?

Can you maybe make a deliberate short pause between pressing Shift-Cursor Up and Cmd-C to see if this is indeed an issue with the app?

How is the behavior in other apps - e.g Apple's Notes or another editor app like Runestone?

I'm really not doing anything special with these keyboard shortcuts and Cmd-C and Shift-Cursor up are iOS system shortcuts.

Hi Alexander, thanks for the quick reply. I just tested again : 

- Select whole line with shift + cursor up

- Command + c

- Count to 3 😁

- Cursor up : moves to top of file

- Cursor down : returns to insertion point

I also re-tested directly after that with the magic keyboard attached to confirm that I was able to have the same behaviour

All files are remote (shellfish) if that changes anything, and I also have a magic trackpad connected

I have other iPads to test with too if needed, I tried activating the log too but nothing of interest was written.

Version 10.7 for textastic but I had this issue before, just wasn’t able to replicate.

iPad OS 18.5

Test file is a 700 lines JS file, changes to the configuration done were to make all characters visible & soft tab with 4 spaces.

Happy to help / send video or whatever would be useful.

OK just checked too with an ipad mini with ios 26.2 and textastic 10.7, other bluetooth keyboard cover attached to the mini, textastic welcome text : same issue.

I’m selecting the whole line with shift+cursor and found an interesting thing : it only behaves like this if the cursor up / down move after the copy is the opposite of the cursor move used to select the line :

- select with shift+cursor+up, command-c, cursor down -> move to end of file

- select with shift+cursor+up, command-c, cursor up -> cursor up one line

- select with shift+cursor+down, command-c, cursor up -> move to start of file

- select with shift+cursor+down, command-c, cursor down -> move down one line

Hope that helps,

Thanks! With these instructions I could reproduce it!

Never noticed this before. That's a nasty bug - I'll investigate.

Cmd-C isn't even necessary: just Shift-Cursor Down to select the whole line and then Cursor Up jumps to the start of the file. 

But then pressing down again jumps to the next line as expected.

I hope it's easy to fix.

I've been debugging the problem and this looks like an actual iOS bug.

I can reproduce the same behavior in the Notes app and in Runestone on iPadOS 18.5.

I don't think I can work around this problem because this appears to be a bug in the iOS text system.

Can you also see the problem in the Notes app?

• Open a note in the Notes app
• Place the insertion point at the start of a line
• Use Shift-Arrow Down to select the current line
• Press Arrow Up
• Now the insertion point is at the beginning of the document

I've reported this bug to Apple.

Yes I can reproduce it too with notes, guess that we’ll have to wait for Apple on this one then. Looks like it has been around for quite some time. Thanks