Is there a posting that shows the beta version numbers and the dates each was released?
I thought this might be helpful as a way of checking if a new version has been released without having to boot and open the device that has the beta software installed. That would let us easily check if a new release has happened and a history of the releases.
Is there anything like this here?
Comments
8 comments
We have an internal document of course, but nothing public right now.
Andy, I'm happy to announce on behalf of Jim the new build 249. ❤️
Hi Mats, thanks for the heads up. Sadly that has created some new questions.
How would I determine if I already had build 249 installed? When I look in the app at the ver number it shows a numbering scheme of x.x.x. it's like the 249 reference isn't reflected in what we can see.
Secondly I'm assuming that since no change log is shared we just have to test generally when a new release comes out. We have no way of testing the exact things that were corrected in that lastest release?
Thanks again in advance
If you touch the hamburger up left to show the menu and then scroll down you have both version and build number printed there.
I think I was confused because the build number that shows right now in the app is a 4 digit number and here in the forum the newest version is 249 which looked like a different numbering scheme. So I figured I was missing some important understanding.
Thanks for the help.
If there is something new and important that we want testers to focus on, we will share it, but it is usually only one major feature per set of build numbers that belong to the user facing version number being tested. For example, the focus of the 4.5.0 beta test, which included many build numbers, was testing the Mini 3 support. Having said that, the main benefit we receive from testers is actually the automated crash reports that we collect because it is impossible for us to test as many combinations of hardware as our diverse and large group of testers. In other words, if the app crashes, no need to report it here unless there are specific steps to reproduce it every time - we already have the crash report that shows us the exact line of code causing the issue. The problem is, most of the crashes happening recently are not in our code but rather in the libraries we rely on, such as the DJI SDK.
Hi Jim. So it's good news that your right on top of the issues as far as your technically Able. Historical how quickly has DJI responded to and fixed sdk bugs in the past? I'm sure we're all looking forward to a stable reliable environment. How long did it take sdk v4 to become solid from its release date?
Thanks
They gave us no timeline. In the past it has been anywhere from days to months:
https://sdk-forum.dji.net/hc/en-us/community/posts/17495566595609-mini3pro-with-msdk-5-3-crashes-app-from-time-to-time?page=1#community_comment_17963213758745
Please sign in to leave a comment.