• Avatar
    Permanently Deleted User

    Here's a screenshot of the Switfkey keyboard over my home screen. As I said, the back key on the tablet doesn't make it disappear. Nor does turning the screen off and on again. In this case I managed to make it go away by going into Google search and making it disappear there. Please help. Many thanks. A

    1
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Having exactly the same problem! And it is very frustrating!

    Any way we can revert to the previous version?

    1
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Mine too

    Bluetooth Keyboard
    Logitech K810

    1
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    I too am experiencing this very same issue that seems to have been introduced what seems like a year ago but instead of not disappearing SwiftKey Keyboard would report so many errors that the Android OS recommended it be uninstalled. The crashes are gone but the keyboard behaves incorrectly

    1
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    I am experiencing the same thing with a Samsung Galaxy Tab E 8" and a Belkin bluetooth keyboard. Any suggestions? I'd hate to have to use a different keyboard but it looks like I may have to.

    1
    Acciones de comentarios Permalink
  • Avatar
    Permanently deleted user

    Same here with Tablet Samsung Galaxy s3.

    I love swiftkey: sole this bug pls

    1
    Acciones de comentarios Permalink
  • Avatar
    Mark Brooks

    I'm having this problem as well unfortunately - I can no longer swap between English and Cyrillics using my hard keyboard linked to my phone. Showing the keyboard on screen I can see that the virtual keyboard changes between english and cyrillics but unfortunately when typing it defaults to either English or Cyrillics - basically whatever is set as the default for swiftkey

    1
    Acciones de comentarios Permalink
  • Avatar
    Peter Jancar

    Same problem here with android 6.0 with 5.1 there was not any problem with that.

    1
    Acciones de comentarios Permalink

Iniciar sesión para dejar un comentario.