3

z64 It is consistent. I can’t use Kagi on my phone atm :-(

  • z64 replied to this.

    shawthing I see. Is this an issue that just started happening recently? Or have you never been able to make searches from this device?

      z64 it used to work fine on this device. I’ve only noticed this issue in the past few days. I’ve been using it on this phone for a few months without trouble.

      • z64 replied to this.

        That works! Guess it’s something to do with the age of this browser. I’m happy just to use the URL you supplied if that’s a reliable work around?

        • z64 replied to this.

          shawthing Gotcha. Yes that's the only thing I can recommend in the meantime - the /html bit is a feature, so that's not going anywhere. The caveats of this experience are

          • Missing some things that needs JS, like autosuggest. But luckily very very few of our features need it
          • If you cannot properly disable JS permanently for kagi.com via a browser setting, then some forms of the navigation around the site will kick you back to JS-mode, i.e. clicking the home "G" on the upper left

          I have an open poll with our other engineers for other ideas to try, and one of us will get back to you if anything comes out of it.

          I asked some other users in the same region + iOS if they were having any issues - none so far.

          Any other questions, or if anything changes, let us know 👍

            shawthing Update: We believe we have fixed it for your device 🎉

            Not sure if we will be doing a hotfix for this, but we should have a rollout on monday with a bunch of other stuff - so should be fixed for you by then at the latest.

              Amazing! Thanks so much. The less pressure to upgrade my phone the better 😊

                10 days later
                a year later

                Hey team, this has started to happen again recently. Anything that can be done this time?

                • Vlad replied to this.

                  shawthing please open a new bug report, with steps to reproduce and a video.

                    No one is typing