MA2 beta support

Quadman1227
I was just wondering if the only issue with the beta app (135) was that it “crashed” when you closed it? So technically it doesn’t crash in a way that effects anything then why it was removed? Seems like that’s not a big enough issue, a pop up when closing the app in exchange for fully removing support for an item that worked otherwise.
0

Comments

16 comments

  • Comment author
    Quadman1227

    Won’t let me edit. Had meant 131 not 135.

    0
  • Comment author
    Jim McAndrew Dronelink Staff

    It crashes when you open it and requires you to delete and remove the app to work-around the issue. The reason is was removed was because we needed to get 2.0.0 released to production and Apple does not let you have multiple active versions at once.

    0
  • Comment author
    Forest Weston

    Thanks for your diligent work on the update, Jim, even over the holidays! I’m eagerly anticipating build 135. The MA2 will be a real workhorse when you are finished. 

    0
  • Comment author
    Jim McAndrew Dronelink Staff

    135 is available on iOS (TestFlight) already. 

    1
  • Comment author
    Quadman1227

    Is this due to the current SDK that’s out? If that’s the case will the MA2 be added back into support when that’s fixed?

    Im staying on 133 until that happens or support for that build expires.

    0
  • Comment author
    Forest Weston

    Only in beta, correct? I’m not a beta tester, prefer to let you guys do the testing and I’ll give it a shot when the actual app is updated. 

    -1
  • Comment author
    Quadman1227

    Haha this is generally why I prefer email support so I’m not taken over but that’s ok gotta do as asked......

    0
  • Comment author
    Forest Weston

    Sorry, Quadman. I thought our questions were related. 

    0
  • Comment author
    Glendon Waldner

    I’ve been testing the mapping feature the the past few days and I keep getting the same error..

    I’m flying a large map where I have to use multiple batteries. So when I fly the first portion of a flight plan it goes without any issues.. but when I pause to change batteries and restart, the drone flies to its pause point, starts and immediately errors out saying, too far off course D76m.

    I can confirm that it wasn’t too windy because the first portion worked perfectly.
    It’s not just an issue that’s random, I simply cannot get the drone to fly a second battery in a flight plan. It’s repeatable.

    Has anyone else experienced mapping bugs?

    0
  • Comment author
    Ron

    DJI has an updated SDK out since Jan 2.  Is this going to fix the crash issue?  I'm just anxious to get my new MA2 working so I can begin learning.  Thanks!

     

    0
  • Comment author
    Glendon Waldner

    Yes! You are correct! I reinstalled the app and it’s working now. So it definitely was a bug that I was experiencing

    0
  • Comment author
    Ron

    So if there is a beta version that works except that you have to crash and then reinstall it, how do I get that version to use until the official fix comes out?

    0
  • Comment author
    Ninja_Geezer

    i have the latest beta test and it does the same everytime i close it ,any ideas ?

     

    0
  • Comment author
    Jim McAndrew Dronelink Staff

    It is a bug that DJI is aware of.

    0
  • Comment author
    Waynedeeln

    On my IPad with Beta version 137 ,I deleted and reinstalled the app. No crashes after that. I have not ran a waypoint mission on the IPad yet but on my Android phone it works great. 

    Thank you for the great app

     

    0
  • Comment author
    Ninja_Geezer

    i found on the ipad if i dont close the app straight away and let it sit down in the background then drag and close it the app does not report a crash ,it behaves different to all my other apps ,im guessing it is a bug noting major .

    0

Please sign in to leave a comment.