Error Scheluding and Posting, Infinite ETA

[EmiTo-7]

Hello, i have an issue posting with the program, used to work before but back then it just broke up, i got a new pc, installed it here and its still broken

What is happening is that once you schelude or "post it" it would say "will post at XX:XX:XX" ETERNALLY, it would refuse to post at the indicated date If you schelude, it would just do the same, pass from schelude to posting and put the ETA to the current date but without posting at all I have waited to see if it has a delay and will post later on but after a day without doing anything i gave up

[mvdicarlo]

Could you provide the logs folder (zipped)? You can find it at %appdata%/postybirb-plus

It sounds like a strange file saving issue potentially but hard to say without the logs. And do you use OneDrive for your documents folder?

[EmiTo-7]

app-2024-07-15.log log-audit.json here they are!

and no, my files are saved in a normal folder in my ssd i let the program running for a few hours with that error "running" so hopefully you find something, thank you for replying!

[mvdicarlo]

I need to remind myself on how the app queues everything since it has been a few years since I reviewed that code.

But in the logs at a glance the only thing that I am noticing as strange is an error here that happens during posting. So it might be that something like the resize functionality is having issue with a file.

I might be able to try to reproduce it if you send me the file you are getting stuck with and the list of websites you are trying to post to as I am unsure if it is an issue with the file itself or a website interaction. It has been a few years but it wouldn't be the first time some weirdness with files happened.

{"message":"[FileManagerService] Could not find MIME for Buffer Error: Could not find MIME for Buffer \n at Jimp.parseBitmap$ (C:\Users\vasqu\AppData\Local\Programs\postybirb-plus\resources\app.asar\node_modules\@jimp\core\dist\utils\image-bitmap.js:224:48)\n at tryCatch (C:\Users\vasqu\AppData\Local\Programs\postybirb-plus\resources\app.asar\node_modules\regenerator-runtime\runtime.js:63:40)\n at Generator.invoke [as _invoke] (C:\Users\vasqu\AppData\Local\Programs\postybirb-plus\resources\app.asar\node_modules\regenerator-runtime\runtime.js:293:22)\n at Generator.next (C:\Users\vasqu\AppData\Local\Programs\postybirb-plus\resources\app.asar\node_modules\regenerator-runtime\runtime.js:118:21)\n at tryCatch (C:\Users\vasqu\AppData\Local\Programs\postybirb-plus\resources\app.asar\node_modules\regenerator-runtime\runtime.js:63:40)\n at invoke (C:\Users\vasqu\AppData\Local\Programs\postybirb-plus\resources\app.asar\node_modules\regenerator-runtime\runtime.js:154:20)\n at C:\Users\vasqu\AppData\Local\Programs\postybirb-plus\resources\app.asar\node_modules\regenerator-runtime\runtime.js:164:13","level":"error","timestamp":"2024-07-15T18:17:16.761Z"}

[mvdicarlo]

Apologies, I should have offered an alternative to posting it here. I hope you don't mind I deleted your comment for the sake of not potentially running into issues with github content policies. It would be better if you emailed them to me or reached out on discord. I don't mind files like that personally, more of just a precaution.

[EmiTo-7]

Eep, didn't consider that, my bad too Sure, discord is fine, my code is emito_rawr

[mvdicarlo]

I believe this was resolved.