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 7665669
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 31, 20262026-05-31T14:37:56+00:00 2026-05-31T14:37:56+00:00

I have a simple method that just takes two managed object IDs, pulls the

  • 0

I have a simple method that just takes two managed object IDs, pulls the managedObjects for them, makes a relation and then saves them into the managedObjectContext.

When I perform the save on the managedObjectContext, the debugger stops on the save line with an objc_exception_throw referencing the nsmanagedObjectContext save. Although there is no output in the nserror object that is output to give me any details as to why an exception is thrown. It also appears as if this save does work fine, which makes this even more confusing.

Here is the method in question…

- (void)relateLocationToInvite:(NSManagedObjectID *)locationID :(NSManagedObjectID *)inviteID {
NSManagedObject *invite = [self.managedObjectContext objectWithID:inviteID];
NSManagedObject *locationObj = [self.managedObjectContext objectWithID:locationID];
Location *location = (Location *)locationObj;

[invite setValue:location forKey:@"location"];
NSError *error = nil;
if( ![self.managedObjectContext save:&error] ){
    NSLog(@"Error relating a location to an invite %@",error);
}

}

  • 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-31T14:37:58+00:00Added an answer on May 31, 2026 at 2:37 pm

    If the execution of the application continues after the save: method without any problem (i.e. without throwing any uncaught exception and without reporting any error), that means the saving operation’s implementation has caught the exception and decided to silently ignore it.

    Why this happens is unclear: maybe the implementation relies on exceptions to report internal errors (this is not the way Objective-C exceptions should be used but some other languages make more use of exceptions). As long as the exception is caught before it reaches your own code, you should not worry about it.

    If you want to know the reason of the exception, you may break on objc_exception_throw and use the following debugger command:

    po *(id *)($ebp + 8)
    

    This will display the NSException * parameter given to the function in the iOS Simulator (x86 architecture). On the device (arm architecture), the same result can be achieved using (if my memory serves my correctly):

    po $r0
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am simply learing Ajax with jQuery and have a simple page method that
I have a simple mapview that has the following viewdidload method and didupdate to
So I have a very simple class that has a method called getThumbUrl() but
I have a really simple class with two methods; One that will be called
I have a generic Print method that iterates over a list and simply prints
I have a simple Java class that has some methods: public class Utils {
Say I have this simple method: public IEnumerable<uint> GetNumbers() { uint n = 0;
I have a simple setter method for a property and null is not appropriate
I have a simple extension method on the int type so I can do
I was wondering if anyone knew why jQuery doesn't have a simple $().id() method.

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.