# 1.29.0 -> 1.29.1

### Breaking Changes

#### **Update User Service Calls**

The return type has changed from `Void` to `Activation`.

```swift
// OLD (1.29.0)
activationService.activate(activationId: id, activationCode: code, emailAddress: email) { result in
    switch result {
    case .success:
        print("Activated successfully")
    case .failure(let error):
        print("Error: \(error)")
    }
}

// NEW (1.29.1)
activationService.activate(activationId: id, activationCode: code, emailAddress: email) { result in
    switch result {
    case .success(let activation):
        // Capture userProfileId for future use
        let profileId = activation.userProfileId
        print("Activated userId: \(activation.userId)")
    case .failure(let error):
        print("Error: \(error)")
    }
}
```

#### **Update Legal Documents Service Calls**

Both platforms now require `userProfileId` for all Legal Documents operations. This ID is typically obtained from the `Activation` response or `user` response.

```swift
// OLD (1.29.0)
legalDocsService.getLegalDocuments { result in ... }

// NEW (1.29.1)
legalDocsService.getLegalDocuments(userProfileId: userProfileId) { result in ... }
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://sdk.ims.tech/migration-notes/ios/1.29.0-greater-than-1.29.1.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.