Keyboard displays incorrectly on iPadOS 16 with Universal Control and Stage Manager

Not sure if this is an iPadOS 16Beta bug or an Obsidian bug, so I’m reporting it here so someone with more knowledge is aware of it.

I’m using an iPad Pro 12.9" with M1 chip, running the first public beta of iOS 16 - because I wanted to try out Stage Manager (the simple windowing system for the iPad).

I’m also using Universal Control - so I’m controlling my iPad using the keyboard and trackpad from my Macbook Pro.

I’ve also tested this using an iPad Mini running iPadOS 15 and Universal Control and everything works fine - so the issue is somewhere in the interaction between Obsidian and iPadOS16/Stage Manager. However, I’ve not noticed this behaviour on any other iPadOS16 apps so far - regardless of Stage Manager.

Basically with iPadOS16 and Universal Control, Obsidian works OK. But if you switch Stage Manager on, Obsidian displays the keyboard area and toolbar - but with no keyboard. It seems to think there is no keyboard attached (which is physically true, but logically untrue).

This happens whether Stage Manager is displaying Obsidian as a floating (resizable) window or as a full-screen window.

Again, switching Stage Manager off makes it work OK - but having Stage Manager on or off doesn’t seem to affect other apps in a similar way, so it seems to be something particular to Obsidian.


Please, send the bug report to Apple.

I will do. But, as I say, it does not seem to be happening in any other apps, so appears to be something Obsidian specific


Same problem with my iPad M1 12.9 and iPadOS 16 public beta and the most recent mobile obsidian, 1.2.3 (57)

1 Like

send the bug report to apple.

Yes, already done.

Same here. Does not matter if stage manager is active or not. I also sent this feedback to Apple.

I saw this too, with iPadOS 16 public beta 2 — but, the work-around of toggling Stage Manager on-and-off in the OS’s Control Center, ending up off, did fix the issue for me (at the expense of Stage Manager, obvs)

It looks like this problem is now fixed with the iPadOS 16.1 public beta!

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.