Gemini chat history error “Sorry couldn’t connect to server. Please try again.”
Gemini chat history is not loading from 2 months (for this account as well as another account)
I am getting “Sorry couldn’t connect to the server. Please try again.” Error from last 2 months I can’t load gems or any chats at all (50+ retries 0 success rate), all workflows effected, second account only has 3-5 threads or chats, with only 10 prompts each very light account not used often still same “server error” I have submitted over 40 reports using “report a problem button” no fix or acknowledgment.
I am Google one Permium subscriber, I reached out to google one tier 2 support they said “AI products are being realised and we don’t have access to Gemini engineering teams”, they suggested these troubleshooting steps (same as some platinum product experts in Google support forms suggested) below which I tried them all and still getting the same error
Also please be advised I have tried desktop, mobile web version Gemini.google.com and getting “can’t load chats error” I have tried multiple weeks almost everyday, 1 hour gaps, and still getting the same error, I have tried using two iPhones and the app it’s the same issue across all—app, desktop and mobile site all are effected for me/my two accounts.
What I have already tried
*1. Verify Network Connectivity and Stability:
-
Strong and stable connection via Wi-Fi or mobile data. (30 mpbs downlink and 15 up).
-
Switch between Wi-Fi and mobile data to see if the issue is with a specific network. (Tested didn’t work).
-
No VPNs active no ISP block (access location India, Gemini is official available in India).
-
Check for Widespread Service Outages: (No outage, no official Google social media channels for announcements about service disruptions.)
*2. Perform the “Off and On Again” Protocol:
-
Force-close and restart the Gemini app. (Tried didn’t work)
- Device restart. (Tried didn’t work)
*3. Clear the App Cache and Data:
N/A iOS device, I deleted the app and reinstalled twice, same error
- Check for App Updates:
* Go to the Google Play Store and check for available updates for both the Gemini app and the core Google app.
* Install any pending updates immediately. (Latest app versions both Google app and Gemini, same errors on Gemini.google.com desktop and mobile)
- Reinstall the Gemini App:
* If clearing the cache and data is unsuccessful, uninstall the Gemini app from the Google Play Store, restart your phone, and then reinstall it. (Done, still same errors across web, app and site both desktop and mobile)
III. Advanced Troubleshooting and Settings
This section covers issues related to system settings and account configurations.
- Adjust System Settings:
* Check your device's battery optimization settings. Ensure that the Gemini and Google apps are not "Restricted" and have unrestricted or optimised battery usage. (Checked and verified not restricted)
* Verify that Data Saver mode is not limiting background data usage for the Gemini and Google apps. (Data saver or low power modes are off)
- Verify Account Access and Settings:
* If you are using a work or school account, your administrator may have disabled access to Gemini or its features. Contact your administrator or try using a personal Google account (e.g., an @gmail.com account) to rule out account-specific issues. (N/A, Two personal accounts, workflow effected inaccessible)
* Access the **Gemini Apps Activity** settings to confirm that data retention is enabled. If this setting is turned off, conversations are not saved to your history and will not load. (Enabled, all data intact in activity/gemini page)
* Ensure that Gemini is set as your device's default assistant. Go to Settings > Apps > Default apps > Digital assistant app and confirm that "Gemini" or "Google" is selected. (Done too, same)
IV. Confirmed Workarounds
If you are unable to fix the app, these workarounds provide a way to access your chat history.
- Use the Web Interface:
* Access the chatbot directly through a web browser on your phone or computer by visiting `gemini.google.com`. (Didn’t work, “can’t load chats error)
- Access the Activity Log:
* Your past conversations are stored in your Google Account's activity history. You can view them directly at `myactivity.google.com/product/gemini`. The data will appear as fragmented entries of your prompts and responses. (Using this method, all data is intact and secure)
- Backup Your Chats:
* As a preventative measure, regularly use the "Export to Docs" feature or manually copy and paste important conversations into a separate file. (No batch export option I have select every single response manually)
Some system logs screenshots attached, all tablets, data, code are unavailable (outside the Gemini Apps activity page) work effected
Note: Error screenshot is around a month a few weeks old, (this is happening since two months)
Same “couldn’t load chats” error from mobile site (gemini.google.com)
For mobile app, Device: iPhone, iOS 18.5 (22F76)
Recent iPhone logs: 2025-09-07 16:30:29.045 Current app version is not outdated.
2025-09-07 16:30:29.047 User not onboarded. Fetching eligibility from server.
2025-09-07 16:30:29.047 %@
2025-09-07 16:30:29.051 [GEMEligibilityFetcherImpl] Hitting UserStatus Request for server side eligibility
2025-09-07 16:30:30.131 Server experiment IDs have changed. Updating Phenotype.
2025-09-07 16:30:30.139 [GEMEligibilityFetcherImpl] Received UserStatus Response: %@
2025-09-07 16:30:30.139 [GEMEligibilityFetcherImpl] received eligibilityOk from server.
2025-09-07 16:30:30.146 Updating storage with the eligibility response from server. Eligible: %@, Subject to minor restrictions: %@, Subject to edu account restrictions: %@, Eligibility failure reason: %@, Eligibility rejection reason: %@, Onboarding status: %@ Safe parameters: index0->YES index3->0 index2->NO index5->0 index1->NO index4->0
2025-09-07 16:30:30.146 User has opted in to email marketing: %@ Safe parameters: index0->YES
2025-09-07 16:30:30.147 Navigating to zero state.
2025-09-07 16:30:30.194 Failed to unarchive array: %@ Safe parameters: index0->Error Domain=NSCocoaErrorDomain Code=4864 “*** -[NSKeyedUnarchiver _initForReadingFromData:error:throwLegacyExceptions:]: data is NULL” UserInfo={NSDebugDescription=*** -[NSKeyedUnarchiver _initForReadingFromData:error:throwLegacyExceptions:]: data is NULL}
2025-09-07 16:30:30.293 using fallback logic for feature gate: %d
2025-09-07 16:30:30.293 No bard mode config found for mode id: %@
2025-09-07 16:30:30.294 using fallback logic for feature gate: %d
2025-09-07 16:30:30.295 using fallback logic for feature gate: %d
2025-09-07 16:30:30.295 No bard mode config found for mode id: %@
2025-09-07 16:30:30.296 No bard mode config found for mode id: %@
2025-09-07 16:30:30.296 No bard mode config found for mode id: %@
2025-09-07 16:30:30.296 using fallback logic for feature gate: %d
2025-09-07 16:30:30.296 using fallback logic for feature gate: %d
2025-09-07 16:30:30.296 No bard mode config found for mode id: %@
2025-09-07 16:30:30.297 No bard mode config found for mode id: %@
2025-09-07 16:30:30.297 No bard mode config found for mode id: %@
2025-09-07 16:30:30.300 using fallback logic for feature gate: %d
2025-09-07 16:30:30.300 using fallback logic for feature gate: %d
2025-09-07 16:30:30.300 No bard mode config found for mode id: %@
2025-09-07 16:30:30.303 Fetch starter queries from server during StarterQueryProvider construction
2025-09-07 16:30:30.330 Conversation Mode tooltip enabled
2025-09-07 16:30:30.391 %@
2025-09-07 16:30:30.409 No bard mode config found for mode id: %@
2025-09-07 16:30:30.410 No bard mode config found for mode id: %@
2025-09-07 16:30:30.410 using fallback logic for feature gate: %d
2025-09-07 16:30:30.411 No bard mode config found for mode id: %@
2025-09-07 16:30:30.411 No bard mode config found for mode id: %@
2025-09-07 16:30:30.411 using fallback logic for feature gate: %d
2025-09-07 16:30:30.411 using fallback logic for feature gate: %d
2025-09-07 16:30:30.411 No bard mode config found for mode id: %@
2025-09-07 16:30:30.412 No bard mode config found for mode id: %@
2025-09-07 16:30:30.412 No bard mode config found for mode id: %@
2025-09-07 16:30:30.412 using fallback logic for feature gate: %d
2025-09-07 16:30:30.412 using fallback logic for feature gate: %d
2025-09-07 16:30:30.413 No bard mode config found for mode id: %@
2025-09-07 16:30:30.414 No bard mode config found for mode id: %@
2025-09-07 16:30:30.415 No bard mode config found for mode id: %@
2025-09-07 16:30:30.415 No bard mode config found for mode id: %@
2025-09-07 16:30:30.450 %@
2025-09-07 16:30:30.738 Server experiment IDs have changed. Updating Phenotype.
2025-09-07 16:30:30.830 Server experiment IDs have changed. Updating Phenotype.
2025-09-07 16:30:30.831 using fallback logic for feature gate: %d
2025-09-07 16:30:30.832 No bard mode config found for mode id: %@
2025-09-07 16:30:30.832 No bard mode config found for mode id: %@
2025-09-07 16:30:30.833 using fallback logic for feature gate: %d
2025-09-07 16:30:30.833 using fallback logic for feature gate: %d
2025-09-07 16:30:30.833 No bard mode config found for mode id: %@
2025-09-07 16:30:30.833 No bard mode config found for mode id: %@
2025-09-07 16:30:30.833 No bard mode config found for mode id: %@
2025-09-07 16:30:30.834 using fallback logic for feature gate: %d
2025-09-07 16:30:30.834 using fallback logic for feature gate: %d
2025-09-07 16:30:30.834 No bard mode config found for mode id: %@
2025-09-07 16:30:30.834 No bard mode config found for mode id: %@