Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Plugins unavailable.
See original GitHub issue**macOS version:**10.15.3 **Kap version:**3.1.0
Steps to reproduce
Current behaviour
Expected behaviour
Workaround
I don’t know why these plugins are unavailable. There’s no more alert. Maybe I missed something?
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Plugin is unavailable after installation/activation - WordPress.org
I'm facing issue with sharethis plugin in wordpress. Sharethis plugin creating issue while navigating to 'General Settings' “Fatal error: Uncaught Error: Call ...
Read more >Error message "Plugin Unavailable" in Grafana Home Assistant
Hello, after configured data source google data sheet, put api key and press test button. The test succeded but an error message at...
Read more >What Happens When Audio Software And Plugins Become ...
As you will see, there are several reasons why plugins and other software might become unavailable. Brand Acquisitions. The first reason we are ......
Read more >I cannot install plugins. Plugin site unavailable ... - HOOBS
If you are not able to install plugins or your plugins fail to connect to the internet after a System update, and your...
Read more >Plugins repository is unavailable - GIS Stack Exchange
I'm using QGIS 2.18.20. On MacOS High Sierra 10.13.5 Only recently I haven't been able to find uninstalled plugins. The settings show the ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
If we hide them, people will also be confused why they see a plugin on GitHub, but it doesn’t show up in Kap. I would just add a note (box) under the app description “Requires Kap 3.2.1” and also reduce the opacity for such plugins. Maybe also sort them last.
I figured that since the client auto updates, and this is mostly due to the introduction of the new plugin system, we could get away with not adding anything to handle it. I agree though, your suggestion sounds like a good way to go about it.