Beta 15 has corrupted everything #99605
https://thebrain.zendesk.com/agent/tickets/99605
Hello Trevor,
Thank you for the detailed report. I understand why this is concerning, especially given that the issue is now affecting multiple machines and persists even after reverting to version 14.
The key point here is that your Brain is still accessible via the web client and iOS, which strongly suggests that the Brain data itself is intact in the cloud. What appears to be failing is how the desktop clients are loading or recognizing local Brain metadata after the recent beta update.
To move this forward safely, we’ll need to gather diagnostic data and confirm how the behavior differs across environments.
First, please confirm the following:
• When you log in at https://app.thebrain.com, your Brain opens and is fully usable there
• On iOS, the Brain opens normally in the app
• On desktop (both v15 beta and v14), the Brains list shows “no brains found” and does not allow access to account details
Next, we’ll need log files from one affected desktop machine. These can be collected even if the app is not fully usable.
On Windows
- Open File Explorer
- Copy and paste this path into the address bar and press Enter:
%LocalAppData%\TheBrain\Logs
Send us the file named Output.log
On macOS
- Open Finder
- Click Go > Go to Folder
- Paste this path and click Go:
~/.TheBrain/v9/Logs
as before, send us the file named Output.log
If possible, a short screen recording showing the startup behavior (from launch to the error state) would also be very helpful.
In the meantime, to help us isolate whether this is specific to the most recent beta build, please try the following on one machine only:
• Install and test an earlier v15 build:
https://thebrain.com/download-mac-update?v=15.0.503.0
https://thebrain.com/download-windows-update?v=15.0.503.0
• Confirm whether the Brain appears there or if the same “no brains found” behavior occurs
Please do not delete or reset any local Brain folders yet. Once we review the logs, we’ll be able to advise on next steps without risking data loss.
Thanks again for the clear explanation and your patience. Once we have the logs, we’ll take this up with the engineering team promptly.
Best regards,
John