-
Notifications
You must be signed in to change notification settings - Fork 581
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DJIMissionManager.pauseMissionExecution hangs... #43
Comments
Hi @jgrantr, thanks for your feedbacks, we will investigate this issue and get back to you once we make progress. |
Hi @jgrantr, we have just launched the new Android SDK 3.4.1, please try it and check if the issue still exist. Thanks! |
I am also experiencing this in SDK 3.4.0 with the Inspire 1. |
Hi @jtuchek, please try the latest Android SDK 3.4.1 and check if the issue still exists. |
Hey DJI, what is the status of this issue? Regards |
We have had a big revamp in Mission. |
DJI Android SDK version - 3.4
DJI Product: Phantom 4
Android version: 6.0.1
Android device: Samsung Galaxy Tab S2
Android Studio version: 2.2.2
If you call DJIMissionManager.pauseMissionExecution when a mission is not running, rather than calling back the callback with an error, the call goes off into the ether and NEVER calls the callback. This can be an issue because a mission MAY be running when the call to pause is initiated, and then will complete shortly after (within milliseconds). This issue is reproducible at any time simply by calling DJIMissionManager.pauseMissionExecution when a mission has been stopped or before one is started.
The expected behavior would be that the callback will ALWAYS get called (similar to the way the iOS SDK works), and if there is no mission running (or the mission finishes execution after the call to pause is initiated but before it completes) then an appropriate error gets returned. In iOS, that is error code -5016 (No mission is running).
The text was updated successfully, but these errors were encountered: