Using Files in iOS Native Apps

To handle files in native iOS apps, use convenience methods defined in the SFRestAPI (Files) category. These methods parallel the files API for Android native and hybrid apps. They send requests to the same list of REST APIs, but use different underpinnings.

For example, the following code snippet calls the requestForOwnedFilesList:page: method to retrieve a SFRestRequest object. It then sends the request object to the server, specifying its owning object as the delegate that receives the response.

1SFRestRequest *request = [[SFRestAPI sharedInstance] requestForOwnedFilesList:nil page:0];
2[[SFRestAPI sharedInstance] send:request delegate:self];
3...

This example passes nil to the first parameter (userId). This value tells the requestForOwnedFilesList:page: method to use the ID of the context, or logged in, user. Passing 0 to the pageNum parameter tells the method to fetch the first page.

Swift versions of SFRestAPI (Files) methods are not defined explicitly by Mobile SDK. To code these methods in Swift, use the autocomplete suggestions offered by the Xcode compiler. These suggested method and parameter names are determined by Swift compiler heuristics and can differ from their Objective-C equivalents.

Note

REST Responses and Multithreading

The SalesforceNetwork library always dispatches REST responses to the thread where your SFRestDelegate currently runs. This design accommodates your app no matter how your delegate intends to handle the server response. When you receive the response, you can do whatever you like with the returned data. For example, you can cache it, store it in a database, or immediately blast it to UI controls. If you send the response directly to the UI, however, remember that your delegate must dispatch its messages to the main thread.

Mobile SDK Development Guide

Using Files in iOS Native Apps

REST Responses and Multithreading

See Also