Theme and plugin updates become unresponsive (console error)

Help
1

Steps to reproduce

  1. Open Obsidian settings.
  2. Update themes, or
  3. Update plugins.
  4. Open the console to check for update-related errors (themes/plugins).

Did you follow the troubleshooting guide? [Y/N]

Y

Expected result

  • Theme and plugin updates should complete without any errors appearing in the console.

Actual result

  • Theme and plugin updates do not respond; checking the console shows errors.
  1. For themes, the themes modal opens, but the list of available themes does not load.
  2. For plugins, the update process only displays the “Checking for updates” notification and then becomes unresponsive.

Environment

SYSTEM INFO:
Obsidian version: 1.12.7
Installer version: 1.12.7
Operating system: Windows 10 Pro 10.0.19045
Login status: not logged in
Language: es
Insider build toggle: off
Live preview: on
Base theme: adapt to system
Community theme: none
Snippets enabled: 0
Restricted mode: off
Plugins installed: 1
Plugins enabled: 1
1: Minimal Theme Settings v8.2.3

RECOMMENDATIONS:
Community plugins: for bugs, please first try updating all your plugins to latest. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community plugins.

Additional information

  • For now, the issue is resolved by restarting or reopening Obsidian.
  1. Theme update error
    app.js:1 Error: Failed to load themes
    at t. (app.js:1:2653090)
    at app.js:1:258511
    at Object.next (app.js:1:258616)
    at a (app.js:1:257334)
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    a @ app.js:1
    Promise.then
    l @ app.js:1
    (anonymous) @ app.js:1
    y @ app.js:1
    t.loadItems @ app.js:1
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    y @ app.js:1
    Uv @ app.js:1
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    y @ app.js:1
    t.onOpen @ app.js:1
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    y @ app.js:1
    t.onOpen @ app.js:1
    e.open @ app.js:1
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    y @ app.js:1
    (anonymous) @ app.js:1
    themes
    themes1082×618 32.9 KB
  1. Plugin update error
    app.js:1 Uncaught (in promise) TypeError: Cannot read properties of null (reading ‘length’)
    at e. (app.js:1:2757444)
    at app.js:1:258511
    at Object.next (app.js:1:258616)
    at a (app.js:1:257334)
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    a @ app.js:1
    Promise.then
    l @ app.js:1
    (anonymous) @ app.js:1
    y @ app.js:1
    e.checkForUpdates @ app.js:1
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    y @ app.js:1
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    y @ app.js:1
    Uv @ app.js:1
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    (anonymous) @ app.js:1
    y @ app.js:1
    (anonymous) @ app.js:1

plugins
plugins1070×604 4.83 KB

2

You have a network problem.

3

Hi, are you referring to connection problems? I don’t think so. I had the browser open and was browsing normally.

4

It’s working for me. So there is a connection problem specifically from your computer and where we keep plugin catalog (GitHub). Maybe you are behind a firewall or something.

5

I just checked it again. I had the browser open and was browsing normally. I opened Obsidian and the problem happened again. As I already mentioned, this issue is temporarily fixed by restarting or reopening Obsidian. Regarding the firewall, I don’t have it applied to Obsidian. I will run some more tests.

6

Browsing normally can still miss the specific endpoint Obsidian needs. I’d test GitHub access from that machine while the problem is happening, especially raw.githubusercontent.com and the community plugin/theme catalog URLs. If those hang only inside Obsidian, also check whether Windows Defender/AV web protection, a proxy, or DNS filtering is treating Obsidian differently from the browser. The restart workaround sounds like a stale failed request/cache state after one of those calls fails.