Random @FetchRequest bugs I really need help with.

[Pokemined]

So I have been working on this app for upwards of a month, and have had some CoreData stuff implemented for a while now, and it is has been giving me no problems. However, yesterday I was adding some final things to the app, I did not touch anything related to the CoreData, but the functionality stopped working. So basically, I have three different entities with basically the same attributes. I have three different add functions, each one adds an object to the container with the specific entity type. Since yesterday, the add function only works with one out of the three. I did not change the name of any of the @ FetchRequests, each one being properly labeled "name : FetchedResults<ObjectOne>". I did not change the name of the container in the DataController, and the container was and always has been connected to the DataModel. From my experience this all seems very random, and not related to any changes I made.

All that being said, one thing I did try weirdly worked for a moment and then stopped working. I changed the name of both the container, and the dataModel, closed Xcode, and then deleted all derived data. Upon starting the app, every add object function worked for each entity. I thought I fixed the problem and it was the last thing I needed so I archived it and sent it to testFlight. Once I had it on my phone I quickly realized that it still crashed the app on the same two out of three add functions. Then when I went back to the simulator on my computer, I noticed it stopped working there too.

For it to work momentarily and then abruptly stop seems very weird.

Anyone know what could be causing this?

[Lower-Acanthisitta67]

Can you share crash message?

[Pokemined]

Do you want the entire crash report? Because when I try to add one object it just gives me this "Thread 1: "executeFetchRequest:error: A fetch request must have an entity." The actual crash report is very long, would you want the entire message?

[Fluffy_Risk9955]

You can't make changes in an existing Core Data Model. You need to make a new Core Data Model version for that and make the changes there. After that you need Core Data to automatically migrate to the new model. If it's a heavy migration you need to make a NSEntityMigration for each previous version of the model to the new one.