Skip to content

Why android-client stuck on mavsdk = "2.1.0" mavsdk-server = "2.1.6" ? #231

@dima-ko

Description

@dima-ko

Hey.
I see android example stuck on

mavsdk = "2.1.0"
mavsdk-server = "2.1.6"

It looks like the last version is 3.15.0
Why not update to it?

I am asking because I have native crashes on 2.1.0/2.1.6, like this

11:06:21.381  D  Discovered 1 component(s)
11:06:21.800  A  Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 29436 (mavsdk-event-qu), pid 29251 (s.android.stage)
11:06:22.326  D  MAVLink: warning: Preflight: GPS fix too low
11:06:23.411  A  pid: 29251, tid: 29436, name: mavsdk-event-qu  >>> ua.mil.armysos.android.stage <<<
11:06:23.411  A        #00 pc 000000000136383c  /data/app/~~hmv_f1y0KX9MvEzgqm5K8Q==/ua.mil.armysos.android.stage-8IrdQkUqvbDnf4Esyov-4g==/lib/arm64/libmavsdk_server.so (MavsdkServer::stop()+0)
11:06:23.411  A        #06 pc 00000000003ecf8c  /data/app/~~hmv_f1y0KX9MvEzgqm5K8Q==/ua.mil.armysos.android.stage-8IrdQkUqvbDnf4Esyov-4g==/base.apk (io.mavsdk.mavsdkserver.MavsdkServer.stop+0)
11:06:23.411  A        #11 pc 0000000000018b8c  /data/data/ua.mil.armysos.android.stage/code_cache/.overlay/base.apk/classes27.dex (ua.mil.armysos.drones.mavlink.MavServer.stop$lambda$23+0)
11:06:23.411  A        #16 pc 000000000001899c  /data/data/ua.mil.armysos.android.stage/code_cache/.overlay/base.apk/classes27.dex (ua.mil.armysos.drones.mavlink.MavServer.$r8$lambda$vBh1QswgKN0EEa_GWSUKNVXeqjo+0)
11:06:23.411  A        #21 pc 0000000000017df8  /data/data/ua.mil.armysos.android.stage/code_cache/.overlay/base.apk/classes27.dex (ua.mil.armysos.drones.mavlink.MavServer$$ExternalSyntheticLambda21

And hope they are fixed in later versions

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions