Databases
StackOverflow2013
Postsdbo
POPUT operation response not being saved in Core Data Store
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPUT operation response not being saved in Core Data Store
    primarykey
    data
    text
    <p>I'm trying to authenticate a user with github using RestKit and saving the response back to Core data to hang on to the oauth token. The response is coming back with a 200 or 201 which is good, but nothing is saved back to the context. I assume that there is something small that I am missing, but I can't figure it out. Here's what's going on:</p> <p>This happens in viewDidLoad</p> <pre><code>RKObjectManager *objectManager = [RKObjectManager sharedManager]; RKManagedObjectStore *managedObjectStore = [RKManagedObjectStore defaultStore]; RKEntityMapping *entityMapping = [RKEntityMapping mappingForEntityForName:@"SLAuthentication" inManagedObjectStore:managedObjectStore]; NSString *clientID = [(SLAppDelegate *)[[UIApplication sharedApplication] delegate] clientID]; [entityMapping addAttributeMappingsFromDictionary:@{@"id" : @"tokenID", @"url" : @"url", @"token" : @"oauthToken", @"note" : @"note"}]; entityMapping.identificationAttributes = @[@"tokenID"]; RKResponseDescriptor *responseDescriptor = [RKResponseDescriptor responseDescriptorWithMapping:entityMapping method:RKRequestMethodPUT pathPattern:[NSString stringWithFormat:@"/authorizations/clients/%@", clientID] keyPath:nil statusCodes:RKStatusCodeIndexSetForClass(RKStatusCodeClassSuccessful)]; [objectManager addResponseDescriptor:responseDescriptor]; </code></pre> <p>Here's where the request is made</p> <pre><code>NSManagedObjectContext *context = [[[RKObjectManager sharedManager] managedObjectStore] mainQueueManagedObjectContext]; NSString *secret = [(SLAppDelegate *)[[UIApplication sharedApplication] delegate] clientSecret]; NSString *clientID = [(SLAppDelegate *) [[UIApplication sharedApplication] delegate] clientID]; [[RKObjectManager sharedManager].HTTPClient setAuthorizationHeaderWithUsername:userName password:pass]; [[RKObjectManager sharedManager] setRequestSerializationMIMEType:@"application/json"]; [[RKObjectManager sharedManager] putObject:nil path :[NSString stringWithFormat:@"/authorizations/clients/%@", clientID] parameters:@{@"client_secret": secret, @"scopes" : @[@"repo"]} success:nil failure:nil]; //Flush the username and password so that we aren't storing them anymore. [[RKObjectManager sharedManager].HTTPClient clearAuthorizationHeader]; NSFetchRequest *request = [[NSFetchRequest alloc] initWithEntityName:@"SLUser"]; NSError *error = nil; NSArray *users = [context executeFetchRequest:request error:&amp;error]; [[users firstObject] setUserName:userName]; [context save:&amp;error]; </code></pre> <p>But nothing comes back. The description of the API is here: <a href="http://developer.github.com/v3/oauth/#get-or-create-an-authorization-for-a-specific-app" rel="nofollow">http://developer.github.com/v3/oauth/#get-or-create-an-authorization-for-a-specific-app</a></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USbringel
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COAlso it looks like the response is being mapped into the correct object, but the entity isn't being saved at the end. Any thoughts? Ignore The fetch request and save at the end, RestKit should still save correct?
      singulars
      1. POPUT operation response not being saved in Core Data Store
      1. USbringel
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload