I keep getting messages saying "An error occurs when registering the lospec.com URL handler" and “lua:122:curlerror - could not close connection” when trying to get a palette. Is there anything I can do to fix it?
Hey there! I’ll look into it! curl is the command used to make the URL request to Lospec’s API, so it’s possible something changed on their end. I’ll make sure it’s still working on my Mac, too.
Okay, I’ve tested the extension on both Windows 11 and Mac OS Sequoia using the latest stable version of Aseprite, which at the moment is 1.3.10.1. It’s possible that since v1.3.11 is still in beta (not sure if you’re on -beta1 or -beta2) that not all of the API features have been implemented/are working correctly. For the time being I’d recommend rolling back to the stable version of Aseprite.
I’m afraid the short answer is no, or at the very least “I doubt it”.
The longer answer is: I don’t know what parts of Libresprite’s API are compatible with Aseprite’s API, if any. This extension also relies on Aseprite’s CLI to handle Lospec’s “Open In App” links, so that feature would almost certainly not work in Libresprite.
No problem, it's very useful and I've already used it quite a few times even though I just downloaded it today. And the ability to just get random or daily palettes as well is going to be very helpful for me and I can see myself using it very often
Error: /home/$USER/.config/aseprite/extensions/losepec-palette-importer/./lospec-palette-importer.lua:191: unexpected end of input
on the Steam version on Linux (Manjaro). I launched the programme from the command line directly from /home/$USER/.local/share/Steam/steamapps/common/Aseprite so I could see logs and potentially debug it a little more but when launching it this way instead of through Steam the script ran fine.
Might be helpful as a workaround to anyone who needs it or the developer for figuring out what the problem is.
Thanks for the report. Based on the information from you and @PhoenixTamer, it seems like there’s something up with a file path somewhere when using the Steam version of Aseprite. This should give me a place to start looking.
That said, I don’t currently have a Linux machine (virtual or otherwise) set up for testing, so I can’t 100% guarantee Linux support with this extension, but I’ll do my best!
I just got another reply from user @PhoenixTamer who’s been running into the same issue on Windows and they found out that Avast was preventing the script from executing properly (likely because it relys on curl under the hood, but that’s a guess). I’m not sure if that’s what you’re up against, but it’s possible that your AV is being overzealous.
I was going to try and debug it a bit more today but today it has decided to work fine when launched through Steam too, so I have no idea what was happening.
Weird, but okay! Keep me posted if you run into anything else, and feel free to submit an issue to the GitHub repo if you hit any other snags. Thanks for keeping me in the loop.
The extension is developed on Aseprite 1.3.5 and is working on Mac OS Sonoma and Windows 11. I don’t have a Windows 10 machine to test on, but if you’re seeing an error message please post it here.
Hey, I'm running into an error and don't really know why. Just installed and did everything as the page says. This happens after I click ok on the initial import window that pops up.
Thank you, that helps! If it’s every name you try then I can assume it’s not just one palette with a weird JSON issue. I just hav a couple more questions if you don’t mind.
Are you using the Steam version of Aseprite or the standalone version?
Have you tried removing and reinstalling the extension? If you do, I’d recommend a fresh download just in case something got corrupted last time!
This seems like a path-related issue with the Steam version of Aseprite. Mind if I ask where your Aseprite executable is located? @Merrow’s Cowl is running into the same issue on Linux, so this is helping me narrow it down further.
Hmm…it could be that the extension is running into an issue writing to /tmp, which it needs to do in order to collect the output from curl. I’ll try to get a Linux test done this week to see if I can figure out what’s going on. Sorry you’re running into trouble!
← Return to Aseprite extension
Comments
Log in with itch.io to leave a comment.
I keep getting messages saying "An error occurs when registering the lospec.com URL handler" and “lua:122:curlerror - could not close connection” when trying to get a palette. Is there anything I can do to fix it?
I use window 10 and version 1.3.11 of aseprite
Hey there! I’ll look into it!
curlis the command used to make the URL request to Lospec’s API, so it’s possible something changed on their end. I’ll make sure it’s still working on my Mac, too.Okay, I’ve tested the extension on both Windows 11 and Mac OS Sequoia using the latest stable version of Aseprite, which at the moment is 1.3.10.1. It’s possible that since v1.3.11 is still in beta (not sure if you’re on -beta1 or -beta2) that not all of the API features have been implemented/are working correctly. For the time being I’d recommend rolling back to the stable version of Aseprite.
Awesome work! Thanks!
Thank you for your support!
Please tell me this works for libresprite
I’m afraid the short answer is no, or at the very least “I doubt it”.
The longer answer is: I don’t know what parts of Libresprite’s API are compatible with Aseprite’s API, if any. This extension also relies on Aseprite’s CLI to handle Lospec’s “Open In App” links, so that feature would almost certainly not work in Libresprite.
Never mind, I just got Aseprite lol. Getting the extension now
Thanks for your support!
No problem, it's very useful and I've already used it quite a few times even though I just downloaded it today. And the ability to just get random or daily palettes as well is going to be very helpful for me and I can see myself using it very often
I was getting the error
Error: /home/$USER/.config/aseprite/extensions/losepec-palette-importer/./lospec-palette-importer.lua:191: unexpected end of inputon the Steam version on Linux (Manjaro). I launched the programme from the command line directly from
/home/$USER/.local/share/Steam/steamapps/common/Asepriteso I could see logs and potentially debug it a little more but when launching it this way instead of through Steam the script ran fine.Might be helpful as a workaround to anyone who needs it or the developer for figuring out what the problem is.
Thanks for the report. Based on the information from you and @PhoenixTamer, it seems like there’s something up with a file path somewhere when using the Steam version of Aseprite. This should give me a place to start looking.
That said, I don’t currently have a Linux machine (virtual or otherwise) set up for testing, so I can’t 100% guarantee Linux support with this extension, but I’ll do my best!
Hey again,
I just got another reply from user @PhoenixTamer who’s been running into the same issue on Windows and they found out that Avast was preventing the script from executing properly (likely because it relys on curl under the hood, but that’s a guess). I’m not sure if that’s what you’re up against, but it’s possible that your AV is being overzealous.
I was going to try and debug it a bit more today but today it has decided to work fine when launched through Steam too, so I have no idea what was happening.
Weird, but okay! Keep me posted if you run into anything else, and feel free to submit an issue to the GitHub repo if you hit any other snags. Thanks for keeping me in the loop.
question, how can i change the directory where the palettes should be saved? i have aseprite in drive D:
There’s a button for that on the Palette Preview window. Set the path you want and the extension will remember it.
thank
Funciona no windows 10, e no aseprite 1.3.5?
The extension is developed on Aseprite 1.3.5 and is working on Mac OS Sonoma and Windows 11. I don’t have a Windows 10 machine to test on, but if you’re seeing an error message please post it here.
Hey PhoenixTamer! Can you give me some more info when you get a second?
That’ll help me narrow down the issue. Thanks for the report!
Hi sudo, yeah I can
I can take a screen cap of the order of things if needed also?
Thank you, that helps! If it’s every name you try then I can assume it’s not just one palette with a weird JSON issue. I just hav a couple more questions if you don’t mind.
I'm using the steam version.
Fresh install results in the same issue even with fresh download as of writing.
Thanks for looking into this!
This seems like a path-related issue with the Steam version of Aseprite. Mind if I ask where your Aseprite executable is located? @Merrow’s Cowl is running into the same issue on Linux, so this is helping me narrow it down further.
Hmm…it could be that the extension is running into an issue writing to /tmp, which it needs to do in order to collect the output from curl. I’ll try to get a Linux test done this week to see if I can figure out what’s going on. Sorry you’re running into trouble!
Thanks for the quick response mate! If it helps I am using Ubuntu 22.04 LTS and PopOs, good luck with the tests!
Epic
Thanks! Much appreciated
Thumbs up