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

Fix invalid JSON schema #4

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

karaggeorge
Copy link

No description provided.

@karaggeorge
Copy link
Author

@kevva ping 😄

This is currently blocking the plugin from being installed

@ProjectInfinity
Copy link

@karaggeorge Is there a way to install this without having it be merged into master? It seems abandoned and it would be very nice to have this plugin working.

@karaggeorge
Copy link
Author

@ProjectInfinity you could fork it locally, and follow the steps here to install it as a dev plugin: https://github.com/wulkano/Kap/blob/master/docs/plugins.md#development

I'll try contacting one more time, otherwise I might publish a clone from a fork in the meantime

@paour
Copy link

paour commented Oct 12, 2020

I'll try contacting one more time, otherwise I might publish a clone from a fork in the meantime

Could you indeed fork it? This would be a really useful plugin, if it could be installed. Not everyone who uses Kap is a developer…

@buuduc
Copy link

buuduc commented May 26, 2024

After 4 years, I see this problem wasn't fixed. So, May be @kevva isn't available to help us. So I cloned and also published it as a new plugin. npm link

Because this is a new plugin, you can't see it, so check the plugin list on the Kap app; This is how you fix this issue.

  1. access this folder in your terminal /Users/{username}/Library/Application Support/Kap/plugins. The username is the name of your user on your machine. For example, my username is macbook, I ran this command in my terminal
    cd '/Users/macbook/Library/Application Support/Kap/plugins'
  2. After that, run this command in that folder
    npm install kap-streamable-v2@latest
  3. create the config file for the new plugin by running this command
    touch kap-streamable-v2.json
  4. Now you restart the Kap app and open the installed plugin tab. You must add your username and password of your Streamable account to run this plugin
image 5. Now you can see this option after recording a video image

@buuduc
Copy link

buuduc commented May 26, 2024

After 4 years, I see this problem wasn't fixed. So, May be @kevva isn't available to help us. So I cloned and also published it as a new plugin. npm link

Because this is a new plugin, you can't see it, so check the plugin list on the Kap app; This is how you fix this issue.

  1. access this folder in your terminal /Users/{username}/Library/Application Support/Kap/plugins. The username is the name of your user on your machine. For example, my username is macbook, I ran this command in my terminal
    cd '/Users/macbook/Library/Application Support/Kap/plugins'
  2. After that, run this command in that folder
    npm install kap-streamable-v2@latest
  3. create the config file for the new plugin by running this command
    touch kap-streamable-v2.json
  4. Now you restart the Kap app and open the installed plugin tab. You must add your username and password of your Streamable account to run this plugin

image 5. Now you can see this option after recording a video image

Or you just need to install the plugin if you see it here:
image

@3raxton
Copy link

3raxton commented Nov 24, 2024

Hey @buuduc, thanks for moving this forward. Strangely enough, when I install your version of the plugin using npm, it breaks my version of Kap. I don't know if you've run into this issue before but I can't seem to get cap to run properly post install. Any insight you can provide me here? Thanks!

@buuduc
Copy link

buuduc commented Nov 27, 2024

Hi @3raxton
I haven't encountered this issue before, but I do have a perspective on it. Kap manages its plugins using npm for package management. When you download a plugin, it retrieves it from the npm registry, performs a few tests, and then runs it in your code. Based on this, I think the issue might be related to whether Node.js is properly installed or available in your shell. It could also be due to a compatibility issue with the Node.js version you're using. I suggest trying to run it with different Node.js versions to see if that resolves the problem.

@3raxton
Copy link

3raxton commented Nov 28, 2024

Hey @buuduc, I got things to work but not sure why. I removed the plugin manually, ran the command npm config get prefix and then reinstalled it and for some reason it started working. This could have something to do with it but I can't be sure.

I did have to restart Kap a few times, eventually working my way into the preferences screen, then adding my account info. I appreciate your support and perspective. Out of curiosity, are logins kept locally?

Finally, an idea: Would you consider making this a plugin that is easier to find on GitHub? That way other Kap users may be able to find the plugin rather than digging through issues and accidentally stumbling upon your version as I did (I'm grateful nonetheless). Thanks again!

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

Successfully merging this pull request may close these issues.

5 participants