Kagi TestFlight iOS app critical authentication issue

hithubfr

Executive Summary

The Kagi TestFlight iOS application is currently experiencing critical authentication issues that prevent users from logging into their accounts. This problem renders the beta version completely unusable and requires immediate attention from the development team.

Problem Description

Primary Issue

Authentication Failure: Users cannot sign in to their Kagi accounts through the TestFlight version of the iOS app
Complete Service Disruption: The login functionality is entirely non-functional, making the app inaccessible
Beta Testing Impact: This issue affects all TestFlight beta testers and prevents proper evaluation of new featur

hawdini

Weirdly, for me, I can use the app, but nothing is customised. It’s like Kagi is letting the product be used for free. Either that, or it’s somehow using Privacy Pass to authenticate.

mroche

I am also experiencing this. There was one attempt where despite not showing as logged in my settings page displayed all settings that an account would normally be able to see in the navigation menu. Hopping into the Assistant, it was clear I'm not logged in as none of my custom assistants exist.

That was once out of about a dozen login attempts over the past two days since the update. The rest just cycled back to the Search app and did not actually create a session.

nh9961

I will try to log in with my GitHub account, then I will be hit with an authentication failure as the redirect_url is not associated with the application. Usually I'm guessing I could just force it to continue, but there is no option two on the Kagi browser thing that you log in with. I'm not complaining; it is a beta after all. I just thought I would share my two pence.

MisterTwo

I am experiencing the issue as well.

jdf3

Me too

AlBob

Since the last beta update I’m unable to log into the Kagi Search app on iOS with my Apple Account. Attached error screen image.

I expect that I will be able to log into the app with my Apple Account which I am still able to do on the web.

pieceofhart

Having the same issue - I'm getting the same image/error as @AlBob.

pixel

Hi all,

We're aware of the issue and will release a new version very soon to resolve this!