-
Notifications
You must be signed in to change notification settings - Fork 258
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Loses API Key? #20
Comments
Hi Dusky, before I can solve your issue I'll need some statistics and basic information. Are you connected to the internet ( yes/no ) If you are using a browser, what is the version and name If you are using the browser or desktop, please open the developer console and paste any error logs. If you are on mobile, I will need to know that. I am waiting for your reply. |
if you use a different browser, and import your data from the previous one,
does the issue still persist?
…On Wed, Mar 22, 2023 at 8:35 PM Dusky ***@***.***> wrote:
Yes.
Firefox 110 (64-bit)
Desktop
[image: image]
<https://user-images.githubusercontent.com/651254/227031566-be817260-1b6a-4d6d-8e3c-33b57be2cb8d.png>
—
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APESZJTX2ICNFYVIAUU6OGLW5NPCHANCNFSM6AAAAAAWEJMNYE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I'll try updating, but i was able to recreate it on Chrome 111.0.5563.65. will reply if it happens after updating. |
try clearing your data or using a different key
…On Wed, Mar 22, 2023 at 9:27 PM Dusky ***@***.***> wrote:
I've updated and now it seems to surface in a different way. It gives the
flashing "thinky lines" for a long time and then eventually produces
nothing.
[image: image]
<https://user-images.githubusercontent.com/651254/227042379-c531160b-1840-422f-8516-bf0a82e762b9.png>
—
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APESZJUTLJJC4FBMFD6F45LW5NVDZANCNFSM6AAAAAAWEJMNYE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
After a few prompts, the app claims to no longer have an API key, and the setting to input one no longer accepts input and is disfigured.
This persists after clearing cache, restarting the app and reinstalling.
Strangely enough, this is only true for the one broken chat. I can start new chats as normal.
The text was updated successfully, but these errors were encountered: