Plugin Fails to start after syncing a new Computer/Client

[paxnovem]

Before Submitting: Double-check that you are running the latest version of the plugin. The bug might have already been fixed 😄

Describe the bug

On a new computer that is a fresh install of Obsidian. I start the obsidian sync. The calendar plugin fails to start with console error of

Plugin failure: calendar Error: ENOENT: no such file or directory, open 'C:\Users\Brian\Documents\notes\vaults\knowledgebase\.obsidian\plugins\calendar\main.js'

This originally occurred on a fresh install of v1.1.9 with installer 1.1.9. It was working on another machine with 1.1.9, but an old 0.15.x installer until I updated the installer resulting in both showing the same behavior.

Workaround

On one obsidian instance, I uninstalled and reinstalled the plugin and reset the desired setting. On other instances I then attempted to enable the plugin which worked and had the proper settings synced.

Steps to reproduce

1. Fresh install Obsidian 1.1.9
2. Enable sync from an existing vault
3. Enable syncing setting and extensions
4. Check extensions and see that Calendar has disabled itself
5. Try to enable
6. Get a plugin failed to start dialog

Expected behavior

I expect that the plugin can start after syncing to a new instance like other plugins

Screenshots

N/A

Environment (please specify)

OS

Windows 10 [Windows/macOS/Linux]

Obsidian Version (e.g. v0.10.6)

Obsidian 1.1.9 Installer version 1.1.9 (Settings → About → Current Version)

Theme (if applicable):

Standard light theme If the bug is visual, please provide the name of the Community Theme you're using.

[StevenMcD]

I encountered the same issue today.

When looking at my .obsidian/plugins folder, I found a calendar folder that only contained a manifest file. Because of that, I couldn't even uninstall the plugin on my second machine until I created an empty "main.js" file in the folder.

From there I uninstalled the plugin and reinstalled it.