logancyang
Obsidian mobile crashes when Copilot is enabled
- [x] Disable all other plugins besides Copilot (required)
- [x] Screenshot of note + Copilot chat pane + dev console added (required)
Copilot version: 2.9.4
Describe how to reproduce Enable copilot and add a bunch of models then try to load on mobile. Crashes. Mobile device: Pixel 9 Pro on Android 16 Latest version of Obsidian and Copilot Error seemed to start with OpenAI o3 but persists with Gemini and other models, so I'm not sure what actually causes the problem.
Expected behavior I should be able to use Obsidian on my phone just like I do on desktop. I should be able to sync community plugins without having my phone crash.
Screenshots
Screenshot is from desktop since I can't even open the app on mobile with Copilot enabled, and couldn't show the console anyway.
Additional context I can sometimes catch a glimpse of this specific mobile toast message before it crashes: "Error creating model o3|openai"
Disabling copilot fixes the issue. Enabling it causes crash on startup (requiring me to clear cache and storage and jump through some hoops to get it to open without Copilot)
Even with all other plugins disabled, Copilot crashes Obsidian on mobile instantly upon startup, making Obsidian completely unusable.
Thanks for reporting. I wonder if anybody else sees the same thing. It could be certain limitations on a particular mobile env or simply a RAM limitation. Since there's no console log it's impossible to tell what's going on on mobile. Being an Obsidian plugin on mobile rather than a standalone mobile app is quite limiting, that's why we stated on our landing page that mobile is experimental and feature parity isn't guaranteed.
In the meantime if you can somehow get meaningful messages from vConsole on mobile that would be super helpful!
I'll give that a shot. I'm not sure if it's specific to the pixel 9 pro phone, but I doubt it's specific to me, because this is the second time I've been in this situation with Obsidian Copilot. The first time I wasn't sure what was going on, but this time I had a chance to narrow it down to being clearly caused by this plugin.
I've been trying to capture vConsole logs for you but the app crashes as soon as I enable the plugin, so I'm not able to see or capture anything.
Considering that I'm using Google's latest flagship phone, I don't think it's hardware limitations. I might try installing Obsidian to test this out on some old phones or tablets laying around to help narrow down whether it's specific to this phone or Android in general, in which case presumably it's something about my configuration of the plugin because I would assume you'd be flooded with reports if it was every mobile user.
This also means I'm unable activate "Active community plugin list" in my Sync settings without triggering the scenario where I can only open Obsidian after clearing all data and then jumping through some hoops to get it loading with Restricted mode turned off. It's become quite a time sink and frustration for me. Hopefully it's not a wider issue!
FYI I did try this on several different Android devices from phones to tablets, Samsung, Pixel, Lenovo, etc...
It does not work on any Android device.
If this is not a widespread issue, perhaps there is some debugging we can do with my configuration?
FYI I did try this on several different Android devices from phones to tablets, Samsung, Pixel, Lenovo, etc...
It does not work on any Android device.
If this is not a widespread issue, perhaps there is some debugging we can do with my configuration?
Did you disable the index loading in 'Settings -> QA'?
