Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6593695
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 25, 20262026-05-25T17:42:56+00:00 2026-05-25T17:42:56+00:00

When saving my core data context I have the following error. I have really

  • 0

When saving my core data context I have the following error.
I have really no idea where to start looking at, if you have even a lead…
Thank you.

PS: I checked that all types declared in .h files are the same as in my Data Model.

EDIT : I overwrote intValue in a category of NSDate. Now I see that timeIntervalSinceReferenceDate is called on a NSNumber. I tried to put a breakpoint there but it gives no info (only save: is before my code). I also found out a way to know who is those famous objects : NSDate is an object (called lastCompute) in the same class as the NSNumber (called sleep). Their type match the types declarated in .h and data model. But it does not give me a hint on why CoreData calls intValue on an NSDate. Any lead ? Thanks

-[__NSDate intValue]: unrecognized selector sent to instance 0x6a3cba0
 *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSDate intValue]: unrecognized selector sent to instance 0x6a3cba0'
*** Call stack at first throw:
(
    0   CoreFoundation                      0x01ca35a9 __exceptionPreprocess + 185
    1   libobjc.A.dylib                     0x01df7313 objc_exception_throw + 44
    2   CoreFoundation                      0x01ca50bb -[NSObject(NSObject) doesNotRecognizeSelector:] + 187
    3   CoreFoundation                      0x01c14966 ___forwarding___ + 966
    4   CoreFoundation                      0x01c14522 _CF_forwarding_prep_0 + 50
    5   CoreData                            0x00955b50 -[NSSQLiteConnection execute] + 2320
    6   CoreData                            0x009a7ebd -[NSSQLiteConnection updateRow:] + 365
    7   CoreData                            0x009a6e64 -[NSSQLConnection performAdapterOperations:] + 180
    8   CoreData                            0x009a6b0e -[NSSQLCore _performChangesWithAdapterOps:] + 494
    9   CoreData                            0x009a55ea -[NSSQLCore performChanges] + 410
    10  CoreData                            0x0099f038 -[NSSQLCore saveChanges:] + 216
    11  CoreData                            0x0095d199 -[NSSQLCore executeRequest:withContext:error:] + 409
    12  CoreData                            0x00a0d70b -[NSPersistentStoreCoordinator executeRequest:withContext:error:] + 3691
    13  CoreData                            0x00995948 -[NSManagedObjectContext save:] + 712
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-25T17:42:56+00:00Added an answer on May 25, 2026 at 5:42 pm

    I think I solved the problem.
    I tried to remove the NSDate attribute. A new error came up (explained here). So I checked all my [NSNumber numberWithSomething:] and I found out I was putting numbers created with int in attributes declared as float in data model.
    I fixed all those mistakes, re-added the NSDate and now my app doesn’t crash any more. I hope this was the solution even if it has nothing to do with intValue being called on an NSDate.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

So I'm saving small images to core data which take a really short amount
I'm getting some data from the web service and saving it in the core
I am using core data in my iPhone app. I have created a simple
I'm working on an application backed by Core Data. Right now, I'm saving the
I have a core-data object entity with 2 fields - name (a NSString *)
I have an iPhone/iPad app which uses Core Data. In my DB I have
I am using Core data to enter song details in database. I have 3
This somewhat follows on from the question Saving application data to the ipad/iphone Really
I'm currently facing in problem using Core Data. I have two entities A and
I am facing a really strange problem with Core Data. Let's describe it: Definitions

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.