Jonas Vautherin

> In the file you posted I see a NO in the build options. Does that need to change to YES? Is there a way to add a target framework...

What param are you setting? What autopilot (I assume PX4?), and what version of it?

MAVSDK-Swift is on mavsdk-server 1.4.2: https://github.com/mavlink/MAVSDK-Swift/blob/main/Package.swift#L50. Let me try to update that to 1.4.4 tomorrow :+1:

Could you try with the newly-published [MAVSDK-Swift v1.1.1](https://github.com/mavlink/MAVSDK-Swift/releases/tag/1.1.1)?

Any chance you could try to debug what's happening in C++? Two ways: 1. Build MAVSDK-C++ and try it there from your laptop (I guess it's a problem related to...

Seems like you are trying to build an example from `main` with a MAVSDK from `1.4.x`. How did you install MAVSDK? You should build it from `main` :+1:

The description says: > Send a key-value pair as integer. The use of this message is discouraged for normal packets, but a quite efficient way for testing new messages and...

It does, if you pass it a URL like (that would be on Linux) `serial:///dev/ttyACM0`. Now I don't think that you can have serial access from iOS, can you? :thinking:

Yes you're right, a `MissionItem` is defined [here](https://github.com/mavlink/MAVSDK-Proto/blob/main/protos/mission/mission.proto#L164-L185). Maybe a transition could be added as a `VtolAction`, similarly to the `CameraAction` [here](https://github.com/mavlink/MAVSDK-Proto/blob/main/protos/mission/mission.proto#L172)? @julianoes what do you think?

> Question is, how to modify MissionItem to make it compatible with MAVSDK C++ The API is defined in the proto file [here](https://github.com/mavlink/MAVSDK-Proto/blob/main/protos/mission/mission.proto#L164-L185), then the C++ headers are auto-generated from...