I’m using iOS 11.2.6
Scrivener 1.1.5 (1301)
and a Logitech DiNovo Edge for Mac bluetooth keyboard.
This is the first time I have used a bluetooth keyboard with Scrivener iOS, and I’m not going to assume that the problem has anything to do with Scrivener.
The current issue is that when using THIS PARTICULAR bluetooth keyboard I am experiencing issues similar to those above. The onscreen keyboard does not dismiss and accordingly input from the bt keyboard is not accepted into any app, including Scrivener, unless the onscreen keyboard is present. I have not had to do anything more involved than single- or double-tapping in a text entry area of the screen in order to restore the onscreen keyboard and reenable both onscreen and external keyboard entry. I have not had any occasion where onscreen keyboard did dismiss with the Edge keyboard, but I have regularly used a different somewhat newer bluetooth keyboard with my iPad without any unusual behavior. Further, I have just confirmed that other keyboard to work as intended with Scrivener.
From my viewpoint as an iOS developer and longtime beta tester of software and hardware, this appears to be an issue with Bluetooth compliance and compatibility. True and comprehensive compliance with the standard is rarer than we, as consumers, would hope, regardless of the peripheral involved. The keyboard that does work happens to be a fairly high-end mechanical custom made by a now-defunct low volume maker. The reason it is likely to work properly is that the bluetooth transceiver chip in it was a fairly high-spec, high-cost selection at the time. It pairs with 10 devices and allows switching between them at a keystroke. Sadly, this keyboard is about 4 years old and no longer being made, but It does give hope to those out there that are having problems.
Go to a major computer store and take your tablet. The gang that works there will have no problem with letting you pop batteries into the demo units to check how they work. I’m betting that Logitech fans, like myself, may be a bit disappointed. They have ridden their own 2.4ghz “universal receiver” for a long time and thus have not had the same all-in emphasis on using bluetooth and solving the issues.
For what it’s worth, I will leave you with this test. If you see a problem with a peripheral in more than one app on your iOS device, the problem is with the OS or hardware, not the app developers. If there are only problems in one app, the issue is something that the app developer MAY be able to resolve, but they also may not.
Apple doesn’t allow anything like low-level access to external peripherals like keyboards and headsets. Everything is passed back and forth through the OS. The display of the onscreen keyboard can be called or dismissed by the app developer, but I’m not even sure that the OS allows the app to know the origin of a typed letter, so the developer cannot tell if it came from an external or onscreen keyboard. It makes sense from Apple’s point of view. It’s secure. From the viewpoint of a developer, it’s limiting and puts us and our users at the mercy of Apple’s coding ability and master plan.
I hope this has helped and that those of you having problems find a keyboard that works as well as Scrivener does and that you love the feel of. IT IS OUT THERE!