LeanStorage Swift Guide

The LeanStorage Swift SDK can be used to persist and query data in LeanCloud. The code below shows how you can create an object and store it into the cloud:

do {
    // Create an object
    let todo = LCObject(className: "Todo")

    // Set values of fields
    try todo.set("title",   value: "R&D Weekly Meeting")
    try todo.set("content", value: "All team members, Tue 2pm")

    // Save the object to the cloud
    _ = todo.save { result in
        switch result {
        case .success:
            // Execute any logic that should take place after the object is saved
            break
        case .failure(error: let error):
            // Execute any logic that should take place if the save fails
            print(error)
        }
    }
} catch {
    print(error)
}

Installing SDK

See How to Install Swift SDK.

Objects

LCObject

Storing data on LeanCloud is built around LCObject. Each LCObject contains key-value pairs of JSON-compatible data. This data is schema free, which means that you don't need to specify ahead of time what keys exist on each LCObject. Simply set whatever key-value pairs you want, and our backend will store it.

For example, the LCObject storing a simple todo item may contain the following data:

title:      "Email Linda to Confirm Appointment",
isComplete: false,
priority:   2,
tags:       ["work", "sales"]

Data Types

LCObject supports a wide range of data types to be used for each field, including common ones like String, Number, Boolean, Object, Array, Date, and null. You can nest objects in JSON format to store more structured data within a single Object or Array field.

Special data types supported by LCObject include Pointer and File, which are used to store a reference to another LCObject and binary data respectively.

LCObject also supports GeoPoint, a special data type you can use to store location-based data. See GeoPoints for more details.

Some examples:

let number       : LCNumber       = 42
let bool         : LCBool         = true
let string       : LCString       = "foo"
let dictionary   : LCDictionary   = LCDictionary(["name": string, "count": number])
let array        : LCArray        = LCArray([number, bool, string])
let data         : LCData         = LCData()
let date         : LCDate         = LCDate()
let null         : LCNull         = LCNull()
let geoPoint     : LCGeoPoint     = LCGeoPoint(latitude: 45, longitude: -45)
let acl          : LCACL          = LCACL()
let object       : LCObject       = LCObject()
let relation     : LCRelation     = object.relationForKey("elements")
let user         : LCUser         = LCUser()
let file         : LCFile         = LCFile()
let installation : LCInstallation = LCInstallation()

We do not recommend storing large pieces of binary data like images or documents with LCObject using LCData. The size of each LCObject should not exceed 128 kilobytes. We recommend using LCFile for storing images, documents, and other types of files. To do so, create LCFile objects and assign them to fields of LCObject. See Files for details.

To learn about how you can protect the data stored on LeanCloud, see Data and Security.

Creating Objects

The code below creates a new instance of LCObject with class Todo:

let todo = LCObject(className: "Todo")

The constructor takes class name as a parameter so that the cloud knows the class you are using to create the object. A class in LeanCloud is comparable to a table in a relational database. A class name starts with a letter and can only contain numbers, letters, and underscores.

Saving Objects

The following code saves a new object with class Todo to the cloud:

do {
    // Create an object
    let todo = LCObject(className: "Todo")

    // Set values of fields
    try todo.set("title", value: "Sign up for Marathon")
    try todo.set("priority", value: 2)

    // Save the object to the cloud
    _ = todo.save { result in
        switch result {
        case .success:
            // Execute any logic that should take place after the object is saved
            break
        case .failure(error: let error):
            // Execute any logic that should take place if the save fails
            print(error)
        }
    }
} catch {
    print(error)
}

To make sure the object is successfully saved, take a look at Dashboard > LeanStorage > Data > Todo in your app. You should see a new entry of data with something like this when you click on its objectId:

{
  "title":     "Sign up for Marathon",
  "priority":  2,
  "ACL": {
    "*": {
      "read":  true,
      "write": true
    }
  },
  "objectId":  "582570f38ac247004f39c24b",
  "createdAt": "2017-11-11T07:19:15.549Z",
  "updatedAt": "2017-11-11T07:19:15.549Z"
}

There are several built-in fields that are provided by default which you don't need to specify in your code:

Built-in Field	Type	Description
objectId	LCString	A unique identifier for each saved object.
ACL	LCACL	Access Control List, a special object defining the read and write permissions of other people.
createdAt	LCDate	The time the object was created.
updatedAt	LCDate	The time the object was last modified.

Each of these fields is filled in by the cloud automatically and doesn't exist on the local LCObject until a save operation has been completed.

Field names, or keys, can only contain letters, numbers, and underscores. A custom key can neither start with double underscores __, nor be identical to any system reserved words or built-in field names (ACL, className, createdAt, objectId, and updatedAt) regardless of letter cases.

Values can be strings, numbers, booleans, or even arrays and dictionaries — anything that can be JSON-encoded. See Data Types for more information.

We recommend that you adopt CamelCase naming convention to NameYourClassesLikeThis and nameYourKeysLikeThis, which keeps your code more readable.

Retrieving Objects

If LCObject is already in the cloud, you can retrieve it using its objectId with the following code:

let query = LCQuery(className: "Todo")
let _ = query.get("582570f38ac247004f39c24b") { (result) in
    switch result {
    case .success(object: let todo):
        // todo is the instance of the Todo object with objectId 582570f38ac247004f39c24b
        let title     = todo.get("title")
        let priority  = todo.get("priority")

        // Acquire special properties
        let objectId  = todo.objectId
        let updatedAt = todo.updatedAt
        let createdAt = todo.createdAt
    case .failure(error: let error):
        print(error)
    }
}

After retrieving an object, you can use the get method to acquire the data stored in its fields. Be aware that objectId, updatedAt, and createdAt are 3 special properties that cannot be retrieved using the get method or modified with the set method. Each of these fields is filled in by the cloud only, so they don't exist on LCObject until a save operation has been completed.

If you try to access a field or property that doesn't exist, the SDK will not raise an error. Instead, it will return nil.

Refreshing Objects

If you need to refresh a local object with the latest version of it in the cloud, call the fetch method on it:

let todo = LCObject(className: "Todo", objectId: "582570f38ac247004f39c24b")
_ = todo.fetch { result in
    switch result {
    case .success:
        // todo is refreshed
        break
    case .failure(error: let error):
        print(error)
    }
}

Updating Objects

To update an existing object, assign the new data to each field and call the save method. For example:

let todo = LCObject(className: "Todo", objectId: "582570f38ac247004f39c24b")
todo.set("content", value: "Weekly meeting has been rescheduled to Wed 3pm for this week.")
todo.save()

LeanCloud automatically figures out which data has changed and only the fields with changes will be sent to the cloud. The fields you didn't update will remain intact.

Updating Counters

Take Twitter as an example, we need to keep track of how many Likes and Retweets a tweet has gained so far. Since a Like or Retweet action can be triggered simultaneously by multiple clients, saving objects with updated values directly can lead to inaccurate results. To make sure that the total number is stored correctly, LeanCloud allows you to atomically increase (or decrease) the value of a number field:

try post.increase("likes", by: 1)

You can specify the amount of increment (or decrement) by providing an additional argument. If the argument is not provided, 1 is used by default.

Updating Arrays

There are several operations that can be used to atomically update an array associated with a given key:

• append(String, element: LCType)
  appends the given object to the end of an array.
• append(String, element: LCType, unique: Bool)
  appends the given object to the end of an array. A bool can be specified for unique to ensure that the object only appears once within the array.
• append(String, elements: [LCType])
  appends the given array of objects to the end of an array.
• append(String, elements: [LCType], unique: Bool)
  appends the given array of objects to the end of an array. A bool can be specified for unique to ensure that each object only appears once within the array.
• remove(String, element: LCType)
  removes all instances of the given object from an array.
• remove(String, elements: [LCType])
  removes all instances of the given array of objects from an array.

For example, Todo has a field named alarms for keeping track of times at which a user wants to be alerted. The following code adds the times to the alarms field:

func dateWithString(_ string: String) -> LCDate {
    let dateFormatter = DateFormatter()

    dateFormatter.dateFormat = "yyyy-MM-dd HH:mm:ss"
    dateFormatter.locale = Locale(identifier: "en_US_POSIX")

    let date = LCDate(dateFormatter.date(from: string)!)

    return date
}

func testSetArray() {
    do {
        let todo = LCObject(className: "Todo")

        let reminder1 = dateWithString("2018-04-30 07:10:00")
        let reminder2 = dateWithString("2018-04-30 07:20:00")

        try todo.set("reminders", value: [reminder1, reminder2])

        let result = todo.save()
        assert(result.isSuccess)

        let reminder3 = dateWithString("2018-04-30 07:30:00")

        try todo.append("reminders", element: reminder3, unique: true)

        _ = todo.save { result in
            switch result {
            case .success:
                break
            case .failure(error: let error):
                print(error)
            }
        }
    } catch {
        print(error)
    }
}

Deleting Objects

The following code deletes a Todo object from the cloud:

let todo = LCObject(className: "Todo", objectId: "582570f38ac247004f39c24b")
_ = todo.delete { result in
    switch result {
    case .success:
        break
    case .failure(error: let error):
        print(error)
    }
}

Batch Processing

You can create, save, delete, or fetch multiple objects within a single request:

// Create an array for storing LCObjects
let objects: [LCObject] = []

// Batch create and update
_ = LCObject.save(objects, completion: { (result) in
    switch result {
    case .success:
        break
    case .failure(error: let error):
        print(error)
    }
})

// Batch delete
_ = LCObject.delete(objects, completion: { (result) in
    switch result {
    case .success:
        break
    case .failure(error: let error):
        print(error)
    }
})

// Batch fetch
_ = LCObject.fetch(objects, completion: { (result) in
    switch result {
    case .success:
        break
    case .failure(error: let error):
        print(error)
    }
})

The following code sets isComplete of all Todo objects to be true:

let query = LCQuery(className: "Todo")
_ = query.find { (result) in
    switch result {
    case .success(objects: let todos):
        // Get a collection of todos to work on
        for todo in todos {
            do {
                // Update value
                try todo.set("isComplete", value: true)
            } catch {
                print(error)
            }
        }
        // Save all at once
        let _ = LCObject.save(todos, completion: { (result) in
            switch result {
            case .success:
                break
            case .failure(error: let error):
                print(error)
            }
        })
    case .failure(error: let error):
        print(error)
    }
}

Although each function call sends multiple operations in one single network request, saving operations and fetching operations are billed as separate API calls for each object in the collection, while deleting operations are billed as a single API call.

Data Models

Objects may have relationships with other objects. For example, in a blogging application, a Post object may have relationships with many Comment objects. LeanCloud supports three kinds of relationships, including one-to-one, one-to-many, and many-to-many.

One-to-One and One-to-Many Relationships

One-to-one and one-to-many relationships are modeled by saving LCObject as a value in the other object. For example, each Comment in a blogging app might correspond to one Post.

The following code creates a new Post with a single Comment:

do {
    // Create a post
    let post = LCObject(className: "Post")
    try post.set("title", value: "I am starving!")
    try post.set("content", value: "Hmmm, where should I go for lunch?")

    // Create a comment
    let comment = LCObject(className: "Comment")
    try comment.set("content", value: "KFC is the best!")

    // Add the post as a property of the comment
    try comment.set("parent", value: post)

    // This will save both post and comment
    assert(comment.save().isSuccess)
} catch {
    print(error)
}

Internally, the backend will store the referred-to object with the Pointer type in just one place in order to maintain consistency. You can also link objects using their objectIds like this:

let post = LCObject(className: "Post", objectId: "57328ca079bc44005c2472d0")
try comment.set("post", value: post)

See Relational Queries for instructions on how to query relational data.

Many-to-Many Relationships

The easiest way to model many-to-many relationships is to use arrays. In most cases, using arrays helps you reduce the number of queries you need to make and leads to a better performance. However, if additional properties need to be attached to the relationships between two classes, using join tables would be a better choice. Keep in mind that the additional properties are used to describe the relationships between classes rather than any single class.

We recommend you to use join tables if the total amount of objects of any class exceeds 100.

Queries

We've already seen how you can retrieve a single object from the cloud with LCObject, but it doesn't seem to be powerful enough when you need to retrieve multiple objects that match certain conditions at once. In such situation, LCQuery would be a more efficient tool you can use.

Basic Queries

The general steps of performing a basic query include:

1. Creating LCQuery.
2. Putting conditions on it.
3. Retrieving an array of objects matching the conditions.

The code below retrieves all Student objects whose lastName is Smith:

let query = LCQuery(className: "Student")
query.whereKey("lastName", .equalTo("Smith"))
_ = query.find { result in
    switch result {
    case .success(objects: let students):
        // students is an array of Student objects satisfying conditions
        break
    case .failure(error: let error):
        print(error)
    }
}

Query Constraints

There are several ways to put constraints on the objects found by LCObject.

The code below filters out objects with Jack as firstName:

query.whereKey("firstName", .notEqualTo("Jack"))

For sortable types like numbers and strings, you can use comparisons in queries:

// Restricts to age < 18
query.whereKey("age", .lessThan(18));

// Restricts to age <= 18
query.whereKey("age", .lessThanOrEqualTo(18));

// Restricts to age > 18
query.whereKey("age", .greaterThan(18));

// Restricts to age >= 18
query.whereKey("age", .greaterThanOrEqualTo(18));

You can apply multiple constraints to a single query, and objects will only be in the results if they match all of the constraints. In other words, it's like concatenating constraints with AND:

query.whereKey("firstName", .equalTo("Jack"))
query.whereKey("age", .greaterThan(18))

You can limit the number of results by setting limit (defaults to 100):

// Limit to at most 10 results
query.limit = 10

If you need exactly one result, you may use getFirst for convenience:

let query = LCQuery(className: "Todo")
query.whereKey("priority", .equalTo(2))
_ = query.getFirst { result in
    switch result {
    case .success(object: let todo):
        print(todo)
    case .failure(error: let error):
        print(error)
    }
}

You can skip certain number of results by setting skip:

// Skip the first 20 results
query.skip = 20

You can implement pagination in your app by using skip together with limit:

let query = LCQuery(className: "Todo")
query.whereKey("priority", .equalTo(2))
query.limit = 10
query.skip = 20

For sortable types, you can control the order in which results are returned:

// Sorts the results in ascending order by the createdAt property
query.whereKey("createdAt", .ascending)

// Sorts the results in descending order by the createdAt property
query.whereKey("createdAt", .descending)

You can even attach multiple sorting rules to a single query:

query.whereKey("priority", .ascending)
query.whereKey("createdAt", .descending)

To retrieve objects that have or do not have particular fields:

// Finds objects that have the "images" field
query.whereKey("images", .existed)

// Finds objects that don't have the "images" field
query.whereKey("images", .notExisted)

You can restrict the fields returned by providing a list of keys with .selected. The code below retrieves todos with only the title and content fields (and also special built-in fields such as objectId, createdAt, and updatedAt):

let query = LCQuery(className: "Todo")
query.whereKey("title", .selected)
query.whereKey("content", .selected)
_ = query.getFirst { result in
    switch result {
    case .success(object: let todo):
        let title = todo.get("title") // √
        let content = todo.get("content") // √
        let notes = todo.get("notes") // nil
    case .failure(error: let error):
        print(error)
    }
}

The unselected fields can be fetched later with fetch. See Refreshing Objects.

Queries on String Values

Use .prefixedBy to restrict to string values that start with a particular string. Similar to a LIKE operator in SQL, it is indexed so it is efficient for large datasets:

let query = LCQuery(className: "Todo")
// SQL equivalent: title LIKE 'lunch%'
query.whereKey("title", .prefixedBy("lunch"))

Use .matchedSubstring to restrict to string values that contain a particular string:

let query = LCQuery(className: "Todo")
// SQL equivalent: title LIKE '%lunch%'
query.whereKey("title", .matchedSubstring("lunch"))

Unlike .prefixedBy, .matchedSubstring can't take advantage of indexes, which is not encouraged to be used for large datasets.

If you are looking for string values that do not contain a particular string, use .matchedPattern with regular expressions:

let query = LCQuery(className: "Todo")
// "title" without "ticket" (case-insensitive)
query.whereKey("title", .matchedPattern("^((?!ticket).)*$", option: nil))

However, performing queries with regular expressions as constraints can be very expensive, especially for classes with over 100,000 records. The reason behind is that queries like this can't take advantage of indexes and will lead to exhaustive scanning of the whole dataset to find the matching objects. We recommend that you take a look at our In-App Searching feature, a full-text search solution we provide to improve your app's searching ability and user experience.

Queries on Array Values

The code below looks for all the objects with work as an element of its array field tags:

query.whereKey("tags", .equalTo("work"))

You can also look for objects whose array field tags contains work, sales, and appointment:

query.whereKey("tags", .containedAllIn(["work", "sales", "appointment"]))

To retrieve objects whose field matches any one of the values in a given list, you can use .containedIn instead of performing multiple queries. The code below constructs a query that retrieves todo items with priority to be 1 or 2:

// Single query
let priorityOneOrTwo = LCQuery(className: "Todo")
priorityOneOrTwo.whereKey("priority", .containedIn([1, 2]))
// Mission completed :)

// ---------------
//       vs.
// ---------------

// Multiple queries
let priorityOne = LCQuery(className: "Todo")
priorityOne.whereKey("priority", .equalTo(1))

let priorityTwo = LCQuery(className: "Todo")
priorityTwo.whereKey("priority", .equalTo(2))

let priorityOneOrTwo = priorityOne.or(priorityTwo)
// Kind of verbose :(

Conversely, you can use .notContainedIn if you want to retrieve objects that do not match any of the values in a list.

Relational Queries

There are several ways to perform queries for relational data. To retrieve objects whose given field matches a particular LCObject, you can use .equalTo just like how you use it for other data types. For example, if each Comment has a Post object in its post field, you can fetch all the comments for a particular Post with the following code:

let post = LCObject(className: "Post", objectId: "57328ca079bc44005c2472d0")
let query = LCQuery(className: "Comment")
query.whereKey("post", .equalTo(post))
_ = query.find { result in
    switch result {
    case .success(objects: let comments):
        // comments contains the comments for the post
        break
    case .failure(error: let error):
        print(error)
    }
}

To retrieve objects whose given field contains LCObject that matches a different query, you can use .matchedQuery. The code below constructs a query that looks for all the comments for posts with images:

let innerQuery = LCQuery(className: "Post")
innerQuery.whereKey("image", .existed)

let query = LCQuery(className: "Comment")
query.whereKey("post", .matchedQuery(innerQuery))

To retrieve objects whose given field does not contain LCObject that matches a different query, use .notMatchedQuery instead.

Sometimes you may need to look for related objects from different classes without extra queries. In such situations, you can use .included on the same query. The following code retrieves the last 10 comments together with the posts related to them:

let query = LCQuery(className: "Comment")

// Retrieve the most recent ones
query.whereKey("createdAt", .descending)

// Only retrieve the last 10
query.limit = 10

// Include the related post together with each comment
query.whereKey("post", .included)

_ = query.find { result in
    switch result {
    case .success(objects: let comments):
        // comments contains the last 10 comments including the post associated with each
        for comment in comments {
            // This does not require a network access
            let post = comment.get("post") as? LCObject
        }
    case .failure(error: let error):
        print(error)
    }
}

You can even indicate multi-level associations using dot notations. If you wanted to include the post for each comment as well as the author of the post, you can do:

query.whereKey("post.author", .included)

Feel free to use .included as many times as you need for the same query to have multiple fields included. Related objects retrieved in this way also works with LCQuery helpers like getFirst and get.

You can also use dot notations with .selected to limit the fields returned from the related objects:

query.whereKey("post.author.firstName", .selected)

Caveats about Relational Queries

The backend of LeanCloud is not built on relational databases, which makes it impossible to join tables while querying. For the relational queries mentioned above, what LeanCloud would do is to first perform an inner query (with 100 as default limit and 1000 as maximum) and then insert the result from this query into the outer query. If the number of records matching the inner query exceeds the limit and the outer query contains other constraints, the amount of the records returned in the end could be zero or less than your expectation since only the records within the limit would be inserted into the outer query.

The following actions can be taken to solve the problem:

• Make sure the number of records in the result of the inner query is no more than 100. If it is between 100 and 1,000, set 1000 as the limit of the inner query.
• Create redundancy for the fields being queried by the inner query on the table for the outer query.
• Repeat the same query with different skip values until all the records are gone through (performance issue could occur if the value of skip gets too big).

Counting Objects

If you just need to count how many objects match a query but do not need to retrieve the actual objects, use count instead of find. For example, to count how many todos have been completed:

let query = LCQuery(className: "Todo")
query.whereKey("isComplete", .equalTo(true))
let count = query.count()

Compound Queries

Compound queries can be used if complex query conditions need to be specified. A compound query is a logical combination (OR or AND) of subqueries.

OR-ed Query Constraints

An object will be returned as long as it fulfills any one of the subqueries. The code below constructs a query that looks for all the todos that either have priorities higher than or equal to 3, or are already completed:

let priorityQuery = LCQuery(className: "Todo")
priorityQuery.whereKey("priority", .greaterThanOrEqualTo(3))

let isCompleteQuery = LCQuery(className: "Todo")
isCompleteQuery.whereKey("isComplete", .equalTo(true))

let query = priorityQuery.or(isCompleteQuery)

AND-ed Query Constraints

The effect of using AND-ed query is the same as adding constraints to LCQuery. The code below constructs a query that looks for all the todos that are created between 2016-11-13 and 2016-12-02:

let dateFromString: (String) -> Date? = { string in
    let dateFormatter = DateFormatter()
    dateFormatter.dateFormat = "yyyy-MM-dd"
    return dateFormatter.date(from: string)
}

let startDateQuery = LCQuery(className: "Todo")
startDateQuery.whereKey("createdAt", .greaterThanOrEqualTo(dateFromString("2016-11-13")))

let endDateQuery = LCQuery(className: "Todo")
endDateQuery.whereKey("createdAt", .lessThan(dateFromString("2016-12-03")))

let query = startDateQuery.and(endDateQuery)

While using an AND-ed query by itself doesn't bring anything new comparing to a basic query, combining AND-ed queries with OR-ed queries together allows you to implement complicated query conditions in your program. The code below constructs a query that looks for all the todos created today that either have no location set or have 3 as priority:

let dateFromString: (String) -> Date? = { string in
    let dateFormatter = DateFormatter()
    dateFormatter.dateFormat = "yyyy-MM-dd"
    return dateFormatter.date(from: string)
}

let createdAtQuery = LCQuery(className: "Todo")
createdAtQuery.whereKey("createdAt", .greaterThanOrEqualTo(dateFromString("2018-04-30")))
createdAtQuery.whereKey("createdAt", .lessThan(dateFromString("2018-05-01")))

let locationQuery = LCQuery(className: "Todo")
locationQuery.whereKey("location", .notExisted)

let priorityQuery = LCQuery(className: "Todo")
priorityQuery.whereKey("priority", .equalTo(3))

let orQuery = locationQuery.or(priorityQuery)
let query = createdAtQuery.and(orQuery)

Optimizing Performance

There are several factors that could lead to potential performance issues when you conduct a query, especially when more than 100,000 records are returned at a time. We are listing some common ones here so you can design your apps accordingly to avoid them:

• Querying with "not equal to" or "not include" (index will not work)
• Querying on strings with a wildcard at the beginning of the pattern (index will not work)
• Using count with conditions (all the entries will be gone through)
• Using skip for a great number of entries (all the entries that need to be skipped will be gone through)
• Sorting without index (querying and sorting cannot share a composite index unless the conditions used on them are both covered by the same one)
• Querying without index (the conditions used on the query cannot share a composite index unless all of them are covered by the same one; additional time will be consumed if excessive data falls under the uncovered conditions)

Files

LCFile allows you to store application files in the cloud that would otherwise be too large or cumbersome to fit into a regular LCObject. The most common use case is storing images, but you can also use it for documents, videos, music, and any other binary data.

Creating Files

You can create a file from a string:

if let data = "LeanCloud".data(using: .utf8) {
    let file = LCFile(payload: .data(data: data))
}

You can also create a file from a URL:

if let url = URL(string: "https://leancloud.cn/assets/imgs/press/Logo%20-%20Blue%20Padding.a60eb2fa.png") {
    let file = LCFile(url: url)
}

LeanCloud will auto-detect the type of the file you are uploading based on the file extension, but you can also specify the Content-Type (commonly referred to as MIME type):

if let data = "{\"company\":\"LeanCloud\"}".data(using: .utf8) {
    let file = LCFile(payload: .data(data: data))
    file.mimeType = "application/json"
}

But the most common method for creating files is to upload them from local paths:

if let url = Bundle.main.url(forResource: "avatar", withExtension: "jpg") {
    let file = LCFile(payload: .fileURL(fileURL: url))
}

The file we uploaded here is named avatar.jpg. There are a couple of things to note here:

• Each file uploaded will get its unique objectId, so it is allowed for multiple files to share the same name.
• A correct extension needs to be assigned to each file which the cloud will use to infer the type of a file. For example, if you are storing a PNG image with LCFile, use .png as its extension.
• If the file doesn't have an extension and the content type is not specified, LeanCloud defaults the file's type to be application/octet-stream.

Saving Files

By saving a file, you store it into the cloud and get a permanent URL pointing to it:

_ = file.save { result in
    switch result {
    case .success:
        print("File uploaded. objectId: " + file.objectId)
    case .failure(error: let error):
        // The file either could not be read or could not be saved to LeanCloud
        print(error)
    }
}

You can associate a file with LCObject after it is saved:

let todo = LCObject(className: "Todo")
todo.set("title", value: "Get Cakes")
// attachments is an Array field
todo.append("attachments", element: file)
todo.save()

Upload Progress

You can monitor the progress of uploading and display that to the user:

_ = file.save(progress: { (progress) in
    print(progress)
}) { (result) in
    switch result {
    case .success:
        // Things to do after saving
        break
    case .failure(error: let error):
        print(error)
    }
}

File Metadata

When uploading a file, you can attach additional properties to it with metaData. A file's metaData cannot be updated once the file is stored to the cloud.

// Set metadata
file.metaData["author"] = "LeanCloud"
_ = file.save { result in
    switch result {
    case .success:
        // Get author
        String? author = file.metaData["author"]
        // Get file name
        String? fileName = file.name
        // Get size (not available for files created from base64-encoded strings or URLs)
        UInt64? size = file.metaData["size"]
    case .failure(error: let error):
        print(error)
    }
}

Deleting Files

The code below deletes a file from the cloud:

let file = LCObject(className: "_File", objectId: "552e0a27e4b0643b709e891e")
file.delete()

Enabling HTTPS

If you demand that the files in the cloud should be accessed through HTTPS, check on Enable HTTPS domain in Dashboard > LeanStorage > Settings > Custom domain for files. There is no free quota on using HTTPS for files and you will see the pricing once the function is enabled.

After enabling HTTPS, the URLs of the files previously stored in the _File table will be converted to HTTPS. If you disable the function, the URLs being converted will not change back.

LeanMessage stores files sent through messages with LCFile and the URLs of the files will be included in the messages. After HTTPS is enabled, the URLs of the files sent in the past messages will not be automatically converted like what happens in _File.

Setting up Custom Domain

LeanCloud offers a shared domain for all the apps to access the files stored in the cloud. However, due to the Cyber Security Law of the countries where we offer our services, the shared domain might not be available all the time. We highly recommend that you set up your custom domains for accessing files so that your apps will not be affected when the shared domain becomes unavailable. You can set up custom domains at Dashboard > LeanStorage > Settings > Custom domain for files.

The setup of custom domains is irreversible. You cannot unbind domains, but you can change the domains at any time.

When binding domains, you can choose if you want to enable HTTPS:

• If you don't enable HTTPS, clients can only access files via HTTP.
• If you enable HTTPS, clients can access files via both HTTPS and HTTP.

CDN Support

You can set up your own CDN to improve the speed your users access the files stored on LeanCloud. Take Amazon CloudFront CDN as an example:

1. Read Getting Started with CloudFront.
2. Create an Amazon AWS account, and choose a CloudFront subscription plan that suits your business.
3. LeanCloud has got S3's read permission properly configured, so you can skip Step 2: Upload your content to Amazon S3 and grant object permissions in the guide and proceed with other steps.
4. Take the domain name from the URL of your LCFile and fill it into CloudFront's Origin Domain Name. Leave the other settings with defaults.

GeoPoints

LeanCloud allows you to associate real-world latitude and longitude coordinates with an object by adding LCGeoPoint to the LCObject. By doing so, queries on the proximity of an object to a given point can be performed, allowing you to easily implement functions like looking for users or places nearby.

To associate a point with an object, you need to create the point first. The code below creates LCGeoPoint with 39.9 as latitude and 116.4 as longitude:

let point = LCGeoPoint(latitude: 39.9, longitude: 116.4)

Now you can store the point in an object as a regular field:

try todo.set("location", value: point)

Geo Queries

With a number of existing objects with spatial coordinates, you can find out which of them are closest to a given point, or are contained within a particular area. This can be done by adding another restriction to LCQuery using .locatedNear. The code below returns a list of Todo objects with location closest to a given point:

let query = LCQuery(className: "Todo")
let point = LCGeoPoint(latitude: 39.9, longitude: 116.4)
query.whereKey("location", .locatedNear(point))

// Limit to 10 results
query.limit = 10
_ = query.find { result in
    switch result {
    case .success(objects: let todos):
        // todos is an array of Todo objects satisfying conditions
        break
    case .failure(error: let error):
        print(error)
    }
}

To have the results limited within a certain distance, check out .locatedNear's from and to parameters in our API docs.

You can also query for the set of objects that are contained within a rectangular bounding box with .locatedWithin:

let query = LCQuery(className: "Todo")
let southwest = LCGeoPoint(latitude: 30, longitude: 115)
let northeast = LCGeoPoint(latitude: 40, longitude: 118)
query.whereKey("location", .locatedWithin(southwest: southwest, northeast: northeast))

Caveats about GeoPoints

There are a couple of things to keep in mind:

• Each LCObject may only have one field containing LCGeoPoint object.
• Points should not exceed the extreme ends of the ranges. Latitude should be between -90.0 and 90.0. Longitude should be between -180.0 and 180.0. Attempting to set latitude or longitude out of bounds will cause an error.

Users

At the core of many apps, there is a notion of user accounts that allows users to access their information in a secure manner. We provide a specialized user class called LCUser which automatically handles much of the functionality required for user account management in your app.

LCUser is a subclass of LCObject. Therefore, all the methods that work for LCObject also work for LCUser. The only difference is that LCUser has some additional features specific to user accounts. Each app has a dedicated _User class for storing LCUser.

User Properties

LCUser offers the following fields that LCObject does not have:

• username: The username of the user.
• password: The password of the user.
• email: The email address of the user.
• emailVerfied: Whether the user has verified the email address with LeanCloud or not.
• mobilePhoneNumber: The mobile phone number of the user.
• mobilePhoneVerfied: Whether the user has verified the mobile phone number with LeanCloud or not.

We'll go through each of these in detail as we run through the various use cases for users.

Signing up

When a user first opens your app, you may want them to sign up for an account. The following code shows a typical sign-up process with username and password:

// Create an instance
let user = LCUser()

// Same as user.set("username", value: "Tom")
user.username = LCString("Tom")
user.password = LCString("cat!@#123")

// Optional
user.set("email", value: "tom@leancloud.rocks")
user.set("mobilePhoneNumber", value: "+19490008888")

// Other fields can be set in the same way as LCObject
user.set("gender", value: "secret")

assert(user.signUp().isSuccess)

If the code returns the error 202, it means that a user with the same username already exists in _User table and the client should prompt the user to try a different username. It is also required that each email or mobilePhoneNumber appears only once in the corresponding column, otherwise error 203 or 214 will occur. You may ask a user to sign up with an email address and make the username to be the same as the email. By doing so, the user can directly reset their password with email.

Signing up with Phones

For a mobile app, it's also common to ask users to sign up with their phone numbers instead of usernames and passwords. There are two basic steps in it. First, ask the user to enter a phone number that can receive text messages. When the user clicks on the "Get Verification Code" button, call the following method to have a 6-digit verification code sent to the phone number the user just entered:

_ = LCSMSClient.requestVerificationCode(mobilePhoneNumber: "+19490008888") { (result) in
    switch result {
    case .success:
        break
    case .failure(error: let error):
        print(error)
    }
}

After the verification code is entered by the user, call the following method to finish signing up:

_ = LCSMSClient.verifyMobilePhoneNumber("+19490008888", verificationCode: "123456", completion: { (result) in
    switch result {
    case .success:
        break
    case .failure(error: let error):
        print(error)
    }
})

Phone Number Format

A phone number that LCUser accepts should have a leading plus sign (+) immediately followed by the country code and the phone number without any dashes, spaces, or other non-numeric characters. For instance, +8618200008888 is a valid China number (86 is the country code) and +19490008888 is a valid US or Canada number (1 is the country code).

For a list of countries and regions that LeanCloud can reach out through SMS, please refer to the Pricing section of the SMS guide.

Logging in

The code below logs a user in with username and password:

_ = LCUser.logIn(username: "Tom", password: "cat!@#123") { result in
    switch result {
    case .success(object: let user):
        print(user)
    case .failure(error: let error):
        print(error)
    }
}

Logging in with Emails

The code below logs a user in with email and password:

_ = LCUser.logIn(email: "tom@leancloud.rocks", password: "cat!@#123") { result in
    switch result {
    case .success(object: let user):
        print(user)
    case .failure(error: let error):
        print(error)
    }
}

Logging in with Phones

If you are allowing users to sign up with their phone numbers, you can also let them log in with either a password or a verification code sent via text message. The code below logs a user in with phone number and password:

_ = LCUser.logIn(mobilePhoneNumber: "+19490008888", password: "cat!@#123") { result in
    switch result {
    case .success(object: let user):
        print(user)
    case .failure(error: let error):
        print(error)
    }
}

You may also let a user in with a verification code sent to their phone, which is useful when the user forgets the password and does not want to reset it at the moment. Similar to the steps of signing a user up with phone numbers, ask the user to enter the phone number associated with the account, and call the following method once the user clicks on the "Get Verification Code" button:

_ = LCUser.requestLoginVerificationCode(mobilePhoneNumber: "+19490008888") { result in
    switch result {
    case .success:
        break
    case .failure(error: let error):
        print(error)
    }
}

After the verification code is entered by the user, call the following method to finish logging in:

_ = LCUser.logIn(mobilePhoneNumber: "+19490008888", verificationCode: "123456") { result in
    switch result {
    case .success(object: let user):
        print(user)
    case .failure(error: let error):
        print(error)
    }
}

Sandbox Phone Number

During the development of your application, you may need to test the sign-up or log-in related API intensively with your phone. As there are, however, limits to how quickly messages can be sent into the carrier networks, your testing pace can be greatly affected.

To work around it, you can set up a sandbox phone number in Dashboard > Messaging > SMS > Settings. LeanCloud will issue a fixed verification code to go with that sandbox phone number. Whenever LeanCloud detects such combination of data, the user will be let right in authenticated without any connections to the carrier networks being made.

On a related note, a sandbox phone number also comes in handy for iOS apps that allow users to log in with SMS code. This is because Apple may ask developers to provide a fixed combination of phone number and verification code for them to review the app as a normal user. Failure to do so may result in their app being rejected by App Store.

For more details regarding limitations of sending and receiving SMS messages, see SMS Guide.

Single Device Sign-on

In some scenarios you may want to restrict a user's account to be logged on by no more than one device at a time, that is, when a user logs in to the app on a new device, all the previous sessions on other devices will become invalid. Here's the instruction about how you can implement this feature with LeanCloud:

1. Create a new class that keeps track of each user's credentials and their device information.
2. Each time when a user logs in on a device, update the device information of this user to be the current device.
3. When the app running on another device is opened, check if the device matches the one stored in the cloud. If it does not, log the user out.

User Account Lockout

If the wrong password or verification code is entered for an account for more than 6 times within 15 minutes, the account will be disabled temporarily and the error { "code": 1, "error": "You have exceeded the maximum number of login attempts, please try again later, or consider resetting your password." } will be returned.

The account will be automatically recovered 15 minutes after the last attempt and the process cannot be expedited through SDK or REST API. While the account is disabled, the user cannot be logged in even though the correct credentials are provided. The restriction applies to both client-side SDKs and LeanEngine.

Verifying Emails

You can request that your users have their email addresses verified before they can log in or access certain functions in your app. This makes it harder for spam users to abuse your app. By default, each user has an emailVerified field which becomes false when the user first signs up or has their email address changed. In your app's Dashboard > LeanStorage > Settings, you can enable Send verification emails when users register or change email addresses from clients so that when a user signs up or changes their email address, an email containing a verification link will be sent out automatically. You can find the option to prevent users with unverified email addresses from logging in on the same page.

If a user forgets to click on the link and needs to have their account verified later, the following code can be used to send a new email:

_ = LCUser.requestVerificationMail(email: "tom@leancloud.rocks") { result in
    switch result {
    case .success:
        break
    case .failure(error: let error):
        print(error)
    }
}

The emailVerified will become true after the link is clicked on. This field can never be true when the email field is empty.

Verifying Phone Numbers

Similar to Verifying Emails, you can also request that your users have their phone numbers verified before they can log in or access certain functions in your app. By default, each user has a mobilePhoneVerified field which becomes false when the user first signs up or has their phone number changed. In your app's Dashboard > LeanStorage > Settings, you can enable Send verification SMS when users register or change phone numbers from clients so that when a user signs up or changes their phone number, a text message containing a verification code will be sent out automatically. You can find the option to prevent users with unverified phone numbers from logging in on the same page.

You can also initiate a verification request at anytime with the following code:

_ = LCUser.requestVerificationCode(mobilePhoneNumber: "+19490008888") { result in
    switch result {
    case .success:
        break
    case .failure(error: let error):
        print(error)
    }
}

After the verification code is entered by the user, call the following method and the user's mobilePhoneVerified will become true:

_ = LCUser.verifyMobilePhoneNumber(mobilePhoneNumber: "+19490008888", verificationCode: "123456") { result in
    switch result {
    case .success:
        // mobilePhoneVerified is set to true
        break
    case .failure(error: let error):
        // Verification code is incorrect
        print(error)
    }
}

Current User

After a user is logged in, LeanCloud SDK automatically stores the session information of this user in the client so that the user does not need to log in each time they open the client. The following code checks if there is a user logged in:

let currentUser = LCApplication.default.currentUser

The session information of a user will remain in the client until the user is logged out:

LCUser.logOut()

// currentUser becomes nil
let currentUser = LCApplication.default.currentUser

Setting The Current User

A session token will be returned to the client after a user is logged in. It will be cached by our SDK and will be used for authenticating requests made by the same LCUser in the future. The session token will be included in the header of each HTTP request made from the client, which helps the cloud identify the LCUser sending the request.

Below are the situations when you may need to log a user in with session token:

• A session token is already cached on the client which can be used to automatically log the user in (you can use LCApplication.default.currentUser?.sessionToken to get the session token of the current user).
• A WebView within the app needs to know the current user.
• The user is logged in on the server side using your own authentication routines and the server is able to provide the session token to the client.

The code below logs a user in with session token (the session token will be validated before proceeding):

_ = LCUser.logIn(sessionToken: "anmlwi96s381m6ca7o7266pzf") { (result) in
    switch result {
    case .success(object: let user):
        // Logged in successfully
        print(user)
    case .failure(error: let error):
        // Session token is invalid
        print(error)
    }
}

The code below checks if a session token is valid:

Resetting Passwords

It's quite common for the users of an app to forget their passwords. LeanCloud provides a number of ways for them to reset their passwords.

Here is the flow of resetting password with email:

1. The user enters the email address used for the account.
2. LeanCloud sends an email to the address including a link for resetting password.
3. After the user clicks on the link, a new page will pop up, asking for a new password.
4. The password will be reset after the user enters a new password.

To start with, ask the user to enter the email used for the account, and call the function below:

_ = LCUser.requestPasswordReset(email: "tom@leancloud.rocks") { (result) in
    switch result {
    case .success:
        break
    case .failure(error: let error):
        print(error)
    }
}

The code above will check if there is a user in the _User table that has the email to be the same as the one provided, and will send them a password reset email if so. As mentioned previously, you can make the username of each user to be the same as their email, or collect the email separately and store it in the email field.

Alternatively, you can ask for the mobile phone number instead of the email to reset their password:

1. The user enters the mobile phone number used for the account.
2. LeanCloud sends a short message to the number including a verification code.
3. The user types in the verification code and a new password.

The code below sends a verification code to a number:

_ = LCUser.requestPasswordReset(mobilePhoneNumber: "+19490008888") { (result) in
    switch result {
    case .success:
        break
    case .failure(error: let error):
        print(error)
    }
}

The code above will check if there is a user in the _User table that has the mobilePhoneNumber to be the same as the one provided, and will send them a verification code if so.

The code below resets the password of a user after they enter the verification code and a new password:

_ = LCUser.resetPassword(mobilePhoneNumber: "+19490008888", verificationCode: "123456", newPassword: "cat!@#123") { result in
    switch result {
    case .success:
        // Password is updated
        break
    case .failure(error: let error):
        // Verification code is incorrect
        print(error)
    }
}

Queries on Users

To query for users, you can simple create a new LCQuery for _User:

let userQuery = LCQuery(className: "_User")

For security reasons, the _User table of each new app has its find permission disabled by default. Each user can only access their own data in _User table and cannot access that of others. If you need to allow each user to view other users' data, we recommend that you create a new table to store such data and enable the find permission of this table. You may also encapsulate queries on users within LeanEngine and avoid opening up find permissions of _User tables.

See Security of User Objects for other restrictions applied to the _User table, and Data and Security for more information regarding class-level permission settings.

Associations

Associations involving LCUser works in the same way as basic LCObject. The code below saves a new book for an author and retrieves all the books written by that author:

let book = LCObject(className: "Book")
let author = LCApplication.default.currentUser
book.set("title", value: "My Fifth Book")
book.set("author", value: author)
_ = book.save { result in
    switch result {
    case .success:
        // Find all the books by the same author
        let query = LCQuery(className: "Book")
        query.whereKey("author", .equalTo(author))
        _ = query.find { result in
            switch result {
            case .success(objects: let books):
                // books is an array of Book objects by the same author
                break
            case .failure(error: let error):
                print(error)
            }
        }
    case .failure(error: let error):
        print(error)
    }
}

Security of User Objects

The LCUser class is secured by default. You are not able to invoke any save- or delete-related methods unless the LCUser was obtained using an authenticated method like logIn or signUp. This ensures that each user can only update their own data.

The reason behind is that most data stored in LCUser can be very personal and sensitive, such as mobile phone number, social network account ID, etc. Even the app's owner should avoid tampering with these data for the sake of user's privacy.

The code below illustrates this security policy:

_ = LCUser.logIn(username: "Tom", password: "cat!@#123") { result in
    switch result {
    case .success(object: let user):
        // Attempt to change username
        try! user.set("username", "Jerry")
        // Password is hashed and an empty string will be returned
        let password = user.get("password")
        // This will work since the user is authenticated
        user.save()

        // Get the user with a non-authenticated method
        let query = LCQuery(className: "_User")
        _ = query.get(user.objectId) { result in
            switch result {
                case .success(object: let unauthenticatedUser):
                    try! unauthenticatedUser.set("username", "Toodle")
                    _ = unauthenticatedUser.save { result in
                        switch result {
                            .success:
                                // This will not succeed since the user is unauthenticated
                            .failure:
                                // Failure is expected
                        }
                    }
                case .failure(error: let error):
                    print(error)
            }
        }
    case .failure(error: let error):
        print(error)
    }
}

The LCUser obtained from LCApplication.default.currentUser will always be authenticated.

To check if LCUser is authenticated, you can invoke the method. You do not need to check if LCUser is authenticated if it is obtained via an authenticated method.

As a reminder, the user's password can be set when signing up but cannot be modified and saved to the cloud afterwards unless the user requests it to be reset. It will not be cached on the client and will show as null when being retrieved from the cloud after the user is logged in.

Security of Other Objects

For each given object, you can specify which users are allowed to read it and which are allowed to modify it. To support this type of security, each object has an access control list, implemented by the LCACL class. More details can be found in ACL Guide.

Linking Users

LeanCloud allows you to link your users with services like GitHub, Twitter, and Facebook (commonly known as social networking services, or SNS), allowing your users to sign up or log into your application using their existing identities. For example, to sign up or log in with a user's GitHub account, your code will look like this:

let authData: [String: Any] = [
    // Required
    "uid":           "UID",
    "access_token":  "ACCESS_TOKEN",
    "expires_in":    7200,

    // Optional
    "refresh_token": "REFRESH_TOKEN",
    "scope":         "SCOPE"
]
let user = LCUser()
user.logIn(authData: authData, platform: .custom("github")) { (result) in
    switch result {
    case .success:
        assert(user.objectId != nil)
    case .failure(error: let error):
        print(error)
    }
}

LeanCloud then verifies that the provided authData is valid and checks if a user is already associated with it. If so, it returns the status code 200 OK along with the details (including a sessionToken for the user).

If the authData is not linked to any account, you will instead receive the status code 201 Created, indicating that a new user has been created. The body of the response contains objectId, createdAt, sessionToken, and an automatically-generated unique username. For example:

{
  "username":     "k9mjnl7zq9mjbc7expspsxlls",
  "objectId":     "5b029266fb4ffe005d6c7c2e",
  "createdAt":    "2018-05-21T09:33:26.406Z",
  "updatedAt":    "2018-05-21T09:33:26.575Z",
  "sessionToken": "…",
  // authData won't be returned in most cases
  // See explanations below
  "authData": {
    // …
  }
  // …
}

The authData field won't be returned to the client unless it is owned by the current user.

To ensure that each LCUser is linked to each service account only once, a unique index needs to be created for the authData.<SERVICE_NAME>.uid key in the _User class.

Authentication Data

authData is a JSON object with the names of services as keys and the details as values. You are responsible for completing the authentication flow (usually through OAuth 1.0 or 2.0) to obtain the details from the service provider which is required for linking.

A user who has GitHub linked may have the following object as authData:

{
  "github": {
    "uid":           "…",
    "access_token":  "…",
    "expires_in":    7200,
    "refresh_token": "…",
    "scope":         "…"
  }
}

LeanCloud automatically validates the access tokens for certain services to prevent data forge attack. When the validation fails, LeanCloud will respond with invalid authData error and the linking will not be established. For services that are not recognized by LeanCloud, you are responsible for validating access tokens by yourself. You can turn off the Validate access tokens when logging in with third-party accounts option in your app's Dashboard > LeanStorage > Settings if you prefer not to have LeanCloud validate access tokens for you.

Unlinking

You can unlink a service by setting the authData for the service to null. The code below unlinks a user's GitHub account:

Roles

As your app grows in scope and user-base, you may find yourself needing more coarse-grained control over access to pieces of your data than user-linked ACLs can provide. To address this requirement, LeanCloud supports a form of role-based access control. Check the detailed ACL Guide to learn how to set it up for your objects.

In-App Searching

In-App Searching offers a better way to search through the information contained within your apps. It's built with search engine capabilities that you can easily tap into your app. Effective and useful searching functionality in your app is crucial for helping users find what they need. For more details, see In-App Searching Guide.

In-App Socializing

In-app socializing offers features like following, timeline, status update, interaction, messaging, etc. For more details, see In-App Socializing Guide.