# 1.24.1 -> 1.25.0

## Trip Service changes

* `geometry` is removed from `Trip.Expansion`. Please use `points` instead.
* `vehicles` expansion is renamed to `vehicle` . Check [here](/releases/1.25.0/ios.md#summary) for more info on newly added expansions.

```swift
tripService.fetch(expansions: [.points, .vehicle]) { _ in }
```

* `TripService.fetch` and `TripService.fetchAll` accepts one more parameter as `roles` to filter roles while fetching trips

```swift
tripService.fetch(expansions: [.points, .vehicle], roles: [.driver]) { _ in }
```

## Adding Vehicle ID to trip files

<pre class="language-swift"><code class="lang-swift"><strong>let device = IMSDevice(deviceId: "mock-id", deviceName: "mock-device")
</strong><strong>IMSDeviceManager.associateDevice(device, toVehichleId: "50")
</strong></code></pre>

### AppMisuse API Change&#x73;**:**

* Manual calls to `enableAppMisuse()` and `disableAppMisuse()` are no longer needed. Now SDKConfig manages the AppMisuse feature automatically based on the server configuration

### BGTask Scheduler Registration for AppMisuse:

* To enable AppMisuse and other SDK background functionalities, the host app must register the following identifier in its Info.plist under BGTaskSchedulerPermittedIdentifiers:

**BGTask Identifier:**

```swift
<key>BGTaskSchedulerPermittedIdentifiers</key>
<array>
    <string>com.ims.IMSBGTaskScheduler</string>
</array>
```

* The host app must call the below API and register the task from `application(_:didFinishLaunchingWithOptions:)` app life cycle.

```swift
IMSBGTaskManager.shared.registerTask()
```

* For more info, visit [Link](https://developer.apple.com/documentation/uikit/using-background-tasks-to-update-your-app)


---

# 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/older-releases/1.24.1-greater-than-1.25.0.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.