Popular Resources
-
<% blocks.forEach(function(block, index) { %>
-
<% if (imageHeight) { %>
<% } %>
<% if (block.name) { %><% if (block.html_url) { %> <%= block.name %> <% } else { %> <%= block.name %> <% } %>
<% } %> <% if (block.description) { %><%= block.description %>
<% } %>
<% }) %>
Comments
10 comments
Sounds like maybe you should wait until its out of beta.
I thought the app automatically provided crash reports? I can't provide crash reports if I'm not using the Beta ;-)
I know my post is a bit emotionally loaded, but that's due to my (maybe incorrect) sense that a lot of the blame was placed on DJI (who I also blame for a fair share of stuff), while the Dronelink platform honestly also has a lot of work to do.
I'm aware that we live in an age were most systems have become extremely complex, and thus hard to optimize, but I can't help but to think of that word a lot while using this platform: optimization. But again, I'm aware that I might be totally wrong.
I'm also learning a lot and having fun.
But I just thought it might be valuable feedback to tell about the app crashes while not connected.
It is unclear which code is to blame, but the only data we have is the MSDKv4 version of Dronelink doesn’t suffer from any of the crashes that the MSDKv5 version suffers from. It is exactly the same code base, with the only difference being which version of the DJI SDK that is included. DJI has asked us to give them a working example that demonstrates the crashes, and since we can’t ship them our entire codebase for obvious reasons, that is what we are currently working on. A drone does not need to be connected for DJI’s MSDK code to run.
If you are having a problem with the web app crashing on a PC, this is not likely related to the beta. Please post steps to reproduce / mission plan links in a new bug report here: https://support.dronelink.com/hc/en-us/community/topics/360001440074-Bug-Reports
I think you must have problems with your network or PC somewhere along the line, I use Dronelink web app on PC, Laptop, Galaxy Tab 7FE, and Galaxy Z Fold 4, using either Firefox or Waterfox and don't have problems like you describe
Jim, We've been waiting for more than a year. When will it be updated?
We're paying for something that doesn't work properly :/
Carlos Rodriguez, its not been more than a year, the SDK for the mini3 was only released back in April, and Dronelink DJI is beta, have you read the RED text in this article https://support.dronelink.com/hc/en-us/articles/15304402363411-Mini-3-Mini-3-Pro-Support-Overview and also the bullet points at the start of this article https://support.dronelink.com/hc/en-us/articles/360033520874
From what I'm reading, when it will be updated is very much in DJI's court
@Jim McAndrew
Thanks for the info. It appears I'm wrong about DJI's side not being the most causal factor.
Re: Firefox — roger that. Will check that out.
@Carlos Rodriguez
To their credit, I have never been in doubt about what I got myself into by using the beta, as Dronelink has been very clear about the purpose, and about what would be wrong reasons to join the beta.
@Jim McAndrew
Feedback regarding today's 4.8.0 update.
It appears the update includes a beta warning upon every app launch now. While I understand why that might feel fitting in the face of seemingly wrong expectations of some beta users, I would like to add that it made the user experience worse for me today; every time the app crashed (i.e. constantly), I would quickly relaunch the app to resume the mission, but now I also had to wait for the "beta warning" pop-up and dismiss that every single time, before I could get back to the ongoing mission.
Again, I understand it might seem fitting, but I would argue that it doesn't actually serve a purpose to display that message more than once. If a given user is going to ignore the information, then they will ignore the information. Whereas users who actually understand the implications of participation in beta use, they get "punished" through an additional, redundant pop-up box containing already known information, at an extremely inconvenient point in time.
I'm genuinely just interested in giving constructive feedback. I participate actively in a lot of beta programs, and I enjoy giving thoroughly considered feedback. It's always interesting to see how teams behind various products actually receive and engage when they do get feedback. It varies wildly.
The beta should not be showing this warning every time (assuming you have 270 installed). This warning is only supposed to show up for people that have the production version installed and are connecting to a Mini 3 (which is still in beta). The idea is that they should actually install the beta intentionally if that is what they want to do, and then they won't see the warning anymore.
I just checked the app. It says:
"Version 4.8.0 (270) | Kernel 4.8.0".
I use the beta with Mini 3. I can confirm that I specifically and intentionally installed the beta. Just re-checked my downloaded APK.
I can try uninstalling and reinstalling next time.
I got the in-app notification about the update, which I downloaded and installed. It connected to the Mini 3 just fine. But it showed the beta warning upon every launch and re-launch.
Please sign in to leave a comment.