Matt Jakeman

Agreed, it's a poor user experience having many of the top results being uninstallable. Unfortunately, this isn't trivial to do on the app-side as our search results come directly from...

This seems like it may actually be supported: https://extensions.gnome.org/#shell_version=42 I wonder if we can use this.

We can access this information through the json API. For example, to search for extensions compatible with 3.36 only: ``` https://extensions.gnome.org/extension-query/?search=terminal&shell_version=3.36 ``` Let's aim to support this in 0.4, with...

Odd... We definitely don't need libadwaita 1.1 Taking a look at the [flathub manifest](https://github.com/flathub/com.mattjakeman.ExtensionManager/blob/7a1d66620c0df27b193580fb0d002cde7346f6b9/com.mattjakeman.ExtensionManager.json#L105), we're using a git snapshot of v1.0.1 for that build. Can you try removing that `can-navigate-back`...

Is this still an issue as of Extension Manager 0.3.1?

This shouldn't be a problem now that we're targeting libadwaita 1.2

Could you provide: - Which operating system you are on? (e.g. Fedora, Ubuntu) - Which version of the application? (v0.3.1) - Where you got it from? (Flatpak, Ubuntu repos, etc)

Let's keep this issue focused on the SSL Handshake failure issue. If extensions have randomly stopped working after an update, you want #224 instead.

Minor update v0.2.2 has been released. - **Release Notes:** https://github.com/mjakeman/extension-manager/releases/tag/v0.2.2 - **Flathub Update:** https://github.com/flathub/com.mattjakeman.ExtensionManager/pull/3

Minor update v0.2.3 has been released. - **Release Notes:** https://github.com/mjakeman/extension-manager/releases/tag/v0.2.3 - **Flathub Update:** https://github.com/flathub/com.mattjakeman.ExtensionManager/pull/4