search

rrirower / Channel-Feed-Manager

Setup files for the Channel Feed Manager suite of tools for Roku and Amazon.
Other
8 stars 3 forks source link

Bizarre "FATAL" On My End. #225

Open adamesq opened 1 month ago

adamesq commented 1 month ago

Describe the bug As a Mac guy, I've been running CFM on a Windows server vis AWS. I've just switched over to UTM (so cool, BTW!). I re-ingested my current feed, but on launch I get a supposedly FATAL error claiming "Do Not Show json" is invalid. Unlike Mortal Kombat, this fatality doesn't appear to be fatal at all. The app goes on to function properly. I tried reinstalling, but I'm still getting the error.

To Reproduce Steps to reproduce the behavior:

  1. Launch CFM

Expected behavior No FATAL error.

Screenshots

Channel Feed Manager Issue

Version number:

Additional context Thinking there's an easy fix here, but 🤔

rrirower commented 1 month ago

Try complete uninstall and reinstall.

adamesq commented 1 month ago

Uninstalled...reinstalled...the error still pops up right after the GUI, before opening my feed.

rrirower commented 1 month ago

Does the path "C:\Users\Adam\Documents\Channel Feed Manager\Temp" exist on your install?

You are the only one experiencing this error. I think this is isolated to your configuration on UTM.

adamesq commented 1 month ago

Yes, the path is there. Very odd. I don't think it's causing an issue other than the pop-up. Thank you.

adamesq commented 1 month ago

AHHH...The Temp folder is EMPTY. There is no "Do Not Show.json" in there.

rrirower commented 1 month ago

Do you have "write" access to the folder?

adamesq commented 1 month ago
Screenshot 2024-10-07 at 12 12 36 PM
rrirower commented 1 month ago

It appears you have read-only access to the files in the temp folder. The software tries to write a file into that folder. You must have write access for that to work.

adamesq commented 1 month ago

It's letting me write and read. I tried removing the CFM folder and reinstalled again. I launched with a completely clean CFM. However, the error persists. I'll try adding to the feed and see if anything else arises later. I just want to be free of needing AWS. 😂 I'll report back just in case someone else runs into this odd situation.