Viewing 3 replies - 16 through 18 (of 18 total)
  • Hi Sean Donovan
    As mentioned, I’ll change the default, that will happpen the next time I release an update.
    This will probably solve this “critical bug” for you and SemperFideles, but new critical bugs will be created by people still creating descriptions containing spaces and using an iPhone.
    Then I could silently remove any entered space characters before creating the QR code, and people would start complaining about that.

    The right way to solve this issue, is to have it fixed at the root.
    Google created the Google Authenticator App for IOS and Android, Google created the app in way that it behaves differently depending on if you’re using an iPhone or an Android phone.

    Best regards
    Henrik Schack

    Thanks for the lengthy report. I agree -> I should probably google to see if there is a bug reporting interface for the iPhone authenticator app.

    Henrik,

    Appreciate the work. Not a critical bug for me. All I needed to know was to make sure I didn’t put a space in the Site Name and I was good to go. I really appreciate the app.

    My suggestion was aimed at primarily saving you the grief of people constantly telling you about the problem. A couple of things you could do:

    1. Change the default name that is generated during the plugin install. I didn’t change the name because I’m lazy and am like a majority of users who leave the default value. You’ll then eliminate a good number of problems.

    2. Place instructions underneath the site name that explicitly warns the user that if they use a site name with a space in it that it’s not going to work on the iPhone.

    These two steps ought to be fix enough to keep you getting a steady stream of complaints.

Viewing 3 replies - 16 through 18 (of 18 total)
  • The topic ‘[Plugin: Google Authenticator] Scanning barcode doesn't work’ is closed to new replies.