Skip to content
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

Plugin fails to load in ChromeOS #123

Open
ElCid87 opened this issue Jan 17, 2023 · 1 comment
Open

Plugin fails to load in ChromeOS #123

ElCid87 opened this issue Jan 17, 2023 · 1 comment

Comments

@ElCid87
Copy link

ElCid87 commented Jan 17, 2023

Using Version : 0.6.1 (currently installed: 0.6.1) with Obsidian Current version: 1.4.1 (83) on both Android (Pixel 6 running Android 13) and ChromeOS (Lenovo Chromebook running ChromeOS 110.0.5481.21).

The plugin loads properly on Android but fails to load on ChromeOS.

Most other plugins load properly. But there are several which do not.

AdvancedURI
Kanban
Natural Language Dates
Templates

Here is the list that does load properly
Dataview
Google Tasks
Minimal Theme Settings
Style Settings
Tasks

@ElCid87
Copy link
Author

ElCid87 commented Jan 17, 2023

I can give a bit more history, in case that triggers some thoughts on what's happening. I copied my vault from the Android phone to Google drive (the entire folder went for the ride) and then to my Lenovo Chromebook. Installed Obsidian from the Play Store opened the app and told it to open a folder as a vault. I answered the question that I trusted the author (since it was me that seemed like a safe bet) and noticed warning messages about failed plugins on the upper right of the screen.

A quick check of the community plugins showed 4 of the 9 had installed but we're not enabled. Manually enabling them caused the warning message that the plugin failed to load.

I then tried uninstalling each plugin, install the plugin and then enable the plugin. Same failure. After each step I closed Obsidian and then open it to take the next step.

Thinking the copy from Android to G Drive to ChromeOS may have corrupted something, I created a vault from scratch, enabled community plugins and attempted to install and enable each plugin in the new vault. Same failures.

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

No branches or pull requests

1 participant