Skip to content

Set Obsidian plugin to desktop-only to suppress mobile loading errors#6

Open
nathancashion wants to merge 1 commit into
DiscourseGraphs:mainfrom
nathancashion:fix/disable-mobile-loading
Open

Set Obsidian plugin to desktop-only to suppress mobile loading errors#6
nathancashion wants to merge 1 commit into
DiscourseGraphs:mainfrom
nathancashion:fix/disable-mobile-loading

Conversation

@nathancashion

Copy link
Copy Markdown

Summary

  • Sets isDesktopOnly: true in the Obsidian plugin manifest to prevent the plugin from loading on mobile devices
  • The plugin currently relies on desktop-specific APIs (CodeMirror 6 editor extensions, tldraw canvas views, DOM event handlers for drag-and-drop) that cause errors when Obsidian attempts to load it on mobile
  • This is intended as a stopgap — iPad support is plausible in the future since most of the plugin's core functionality (CM6 extensions, vault access, Supabase sync) can work on tablet, but a dedicated mobile compatibility effort would be needed for touch interactions and canvas features

Test plan

  • Verify plugin loads normally on desktop Obsidian
  • Verify plugin no longer appears / causes errors on Obsidian mobile

🤖 Generated with Claude Code

The plugin relies on desktop-specific APIs (CodeMirror 6 extensions,
tldraw canvas views, DOM event handlers for drag-and-drop) that cause
errors when Obsidian attempts to load it on mobile devices. Setting
isDesktopOnly to true prevents the plugin from loading on mobile,
suppressing these errors until a dedicated mobile compatibility effort
can be undertaken.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@trangdoan982

trangdoan982 commented Jun 5, 2026

Copy link
Copy Markdown
Member

@nathancashion Thanks for this fix! isDesktopOnly: true is definitely the right call. One thing to flag: discourse-graph-obsidian is a publish mirror. When we cut a release, publish.ts pushes the source files from our monorepo, which would overwrite this change.

The fix needs to land in apps/obsidian/manifest.json in the main monorepo to persist. Would you be open to opening a PR there, or would it be easier if we apply it on your behalf and credit you?

@nathancashion

nathancashion commented Jun 6, 2026

Copy link
Copy Markdown
Author

@trangdoan982 Yeah, I discovered that this was a mirror while trying to vibecobe a fix on my local repo. I'm a novice with GitHub, so don't fully understand the difference, but I'll try to repost the PR there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants