Yes, the workaround is the same. But the issue is different. The one described by @m.birkholz is fixed by the RobotPositionCallback2 callback.
Yes, the workaround is the same. But the issue is different. The one described by @m.birkholz is fixed by the RobotPositionCallback2 callback.