Closed SENTINELITE closed 2 years ago
What version (well commit) are you using? I recall some issues with manifest generation at some point, but I thought I'd fixed them all as of the current main
branch. If you build the example project does the manifest generate correctly?
@emorydunn It does indeed build correctly. I had copied the example to my /usr/local/bin/
, which is why I was able to use the command packageName generate-manifest --output /Users/userName/manifest.json
, & get it to generate, but I had forgotten that I had done that & never updated the executable.
Turns out, using: .build/release/packageName generate-manifest --output /Location
works just fine. I guess it was just my ignorance.
Glad to hear it's working, and if I had a nickel for every time I ran the wrong version of something from the command line I could probably retire.
Running
packageName generate-manifest --output /Users/userName/manifest.json
doesn't generate the correct output. It appears it's generating mostly hard-coded values? Actions also aren't generated, causing the plugin to not function. I've compared the intended output (from the example script & wiki file), with other Stream Deck plugins, & ended up diff-checking & creating my ownmanifest.json
file. I ended up getting the example project working with this fix.