Xcode 6 and mmBusinessObject

[rtamesis]

I'm getting some strange behavior with mmBusinessObject where the saveEntities method does not appear to be working properly. I tested my same code on both Xcode 5 and 6 on separate laptops, and while it saves my changes properly to the SQLite database on Xcode 5, it is not doing so on Xcode 6. I've tried cleaning it and deleting the built app from both the simulator and on my iPad, but it doesn't seem to solve the problem.

[kjmcneish]

Are you coding in Swift or Objective-C? I have updated mmBusinessObject to Swift for iOS 8 and Xcode 6 and can get you an early copy if you're interested.

All the best!
Kevin

[rtamesis]

I'm still using Objective-C. I'll probably start learning Swift once I get the app that I've been working on for the last year and a half finished.

[rtamesis]

On further testing, it looks like any changes aren't being saved until I actually quit my app and restart it again. After a user completes a quiz in my app, his or her grade is supposed to be saved to the database using the saveEntities method; I then reload the table listing the grades for different quizzes taken to display the new grade. This works perfectly when running the app on iOS 7, but in iOS 8 both in the simulator and on an iPad, the new grade is not seen until I actually quit the app and then reopen the app again. I don't know if Apple made an underlying change to Core Data in the way data is saved or not or if this is a bug on their part in iOS 8 itself, but I may have to just simply take this functionality out of the app I'm building if I can't find a workaround to it.

[rtamesis]

Well once again I may have been a wee bit premature in saying that the problem lay with Core Data. I may have solved the problem by forcing the tableview to reload in the viewWillAppear: method of the tableViewController. Sorry for all the trouble.

[kjmcneish]

No problem...glad you were able to figure it out!

Kevin

[idearm]

Kevin,

I have done some digging and decided to build my app using only Swift, but am having some difficulty figuring out how to rewrite the mmBusinessObject in Swift. Any suggestions? You presented a much more logical route in Book 3 and would prefer to stick to it.

[kjmcneish]

Sure...here's the version I'm releasing with the upcoming Swift book.

Note that this class uses generics, so here's what your ABusinessObject class needs to look like:

Code: [Select]

class ABusinessObject<T: NSManagedObject> : mmBusinessObject<T> {
   
    override init() {
        super.init()
        self.dbName = "YourDatabaseName"  // <-- Change this
    }
}
And you need to specify the associated entity for your app-specific business objects:

Code: [Select]

class AppCategory<T: AppCategoryEntity>: ABusinessObject<T> {
   
}
Note that you no longer need to set the entityClassName property in your business object classes. That's because you are already specifying the entity in the generic type <T: AppCategoryEntity>.

All the best!
Kevin

[idearm]

This helps a ton, thanks!!

Looking forward to Book 4 as well!!

[idearm]

Hey Kevin,

Just to make sure I am understanding correctly. Within my Business Controller class there is no need for:

self.entityClassName = "EntityClassName"

Line of code because it has already been declared with the generic type similar to what you suggested? Therefore:

override init() {
     super.init()
}

Is all that I would need (for the time being) within my Business Controller class? Please correct me if I'm wrong.


Thank you so much for all of your help! I CANNOT wait to get my hands on Book 4 (granted I will be buying it through the iBooks Store)!!


Best Regards,