• Commentaire officiel
    Avatar
    Alpert

    Hi,

    Thanks for the feedback, I'll take this thread as the main thread.

    At this moment SwiftKey team has confirmed this problem is a known issue. We kindly ask to wait for the fix comes out soon.

    Thank you

    Alpert

    Actions pour les commentaires Permalien
  • Avatar
    Permanently deleted user

    I have oneplus 3 and have the same problem

    2
    Actions pour les commentaires Permalien
  • Avatar
    Permanently deleted user

    Well I was hoping I could work it out myself but turns out it's hopeless on my end :(

    I've tried reinstalling and updating and everything, still can't seem to find a solution to this one.

    0
    Actions pour les commentaires Permalien
  • Avatar
    Permanently Deleted User

    Same problem here (Samsung galaxy s8+). Maybe it's related to Hebrew users. 

    0
    Actions pour les commentaires Permalien
  • Avatar
    Permanently Deleted User

    It seems to be a bug in version 6.7.5.30 onwards. 
    When I uninstalled the Swiftkey app and installed previous version (6.7.4.31), the bug is gone. 

    0
    Actions pour les commentaires Permalien
  • Avatar
    Permanently deleted user

    edit: wrong thread.

    0
    Actions pour les commentaires Permalien
  • Avatar
    Permanently deleted user

    Same issue here using Hebrew with Sony Xperia XZ1 (Android 8). Its seems that the pop up characters are not align correctly when using Hebrew Local.

    Bear in mind that SwiftKey is Sony's default keyboard.

    Tesed SW 6.7.5.31.

    0
    Actions pour les commentaires Permalien
  • Avatar
    Permanently deleted user

    Swift key beta has the same issue. Using hebrew, oneplus 5.

    1
    Actions pour les commentaires Permalien
  • Avatar
    Permanently Deleted User

    Tried the regular and beta current versions, and they both have the same bug.
    Samsung Galaxy s8+,  SwiftKey versions: 6.7.5.31, Beta - 6.7.6.19. Languages: Hebrew, English. Android 7.

     

    One more important thing:
    This bug appears only when the system language is Hebrew (Maybe in Arabic too. Didn't check it). 
    It does not happen when the system language is English (or other languages that are written left to right). 

    0
    Actions pour les commentaires Permalien
  • Avatar
    Permanently deleted user

    Last version (6.7.5.30) has a bug concerning question mark gesture input were swiping to the right would insert a question mark. Now it doesn't work most of the time. You have to keep trying over and over to get it right.

     

    Rolled back to previous version where this problem isn't present (6.7.4.31)

     

    I use Spanish and English (also tried disabling either one, no changes). As I mentioned, the bug started after version 6.7.4.31

     

    I noticed there's a new update: 6.7.6.19, has anyone tried it yet? I'm sick of having to uninstall to roll back

     

    I'm posting here because this could be related to the bug you describe.

    0
    Actions pour les commentaires Permalien
  • Avatar
    Permanently deleted user

    Xiaomi mi5 with lineage 14.1 Hebrew as locale. Same bug with question mark

    1
    Actions pour les commentaires Permalien
  • Avatar
    Alpert

    Thank you everyone.

    @Dexter: can you confirm that only Spanish & English installed, no Hebrew? What's your phone system language? Meanwhile the 6.7.6.19 is a standalone beta, it will installed as second SwiftKey beside the one you've installed. So don't worry about rolling back.

     

    @נתי רובינשטיין: Sorry, we can't take bug reports from 3rd party ROMs. But hopefully by solving the problem on official ROMs can help you as well.

    0
    Actions pour les commentaires Permalien
  • Avatar
    Ryan P

    This is a known issue we are looking into. We will update this thread with more info. 

    0
    Actions pour les commentaires Permalien
  • Avatar
    Permanently deleted user

    @Alpert. Never installed Hebrew. My phone's language is English and I use both english US and Spanish LA. I tried the beta, but unfortunatelly it has the same bug.

    0
    Actions pour les commentaires Permalien
  • Avatar
    Permanently deleted user

    How do i install the old version. With the current version i cannot type a question mark.

    0
    Actions pour les commentaires Permalien
  • Avatar
    Permanently Deleted User

    @Avrohom_Notik: You have to download an apk file of previous version. To uninstall the current version, and then - to install from the apk. Previous APK file can be found 

    0
    Actions pour les commentaires Permalien
  • Avatar
    Permanently deleted user

    I have the same problem - Samsung Galaxy S8, system language english/us, Swiss-German keyboard, it shows accented characters but instead of ä ö ü only some swedish or norwegian, don't know really. So, accented characters are there, but the wrong ones :-( I never installed other languages than Swiss-German, English-US and German. Hope you can fix it, otherwise swiftkey becomes pretty useless. Thanks!

    0
    Actions pour les commentaires Permalien
  • Avatar
    Permanently deleted user

    Waiting for an update when this problem will be fixed.

    In the meanwhile – I've stopped using Swiftkey :-(

     

    0
    Actions pour les commentaires Permalien
  • Avatar
    Ryan P

    Just an FYI, we are testing a fix for this in the beta version of our app. it can be found in the Play Store for free.

    Version 6.7.8..

    I will update this channel again when it goes live to market.

    0
    Actions pour les commentaires Permalien
  • Avatar
    Permanently deleted user

    super, thanks for this information. With 6.7.8. Beta, in the Swiss (German CH) package, accented charactes such as ä ö ü work now. Well done, thanks!

    0
    Actions pour les commentaires Permalien
  • Avatar
    Permanently Deleted User

    Thanks. It seems to be ok also in Hebrew system language. Waiting for the fix to be applied also in the stable version. 

    0
    Actions pour les commentaires Permalien
  • Avatar
    Permanently deleted user

    Thank you, looks like it's been fixed

    0
    Actions pour les commentaires Permalien

Veuillez vous connecter pour laisser un commentaire.