-
-
Notifications
You must be signed in to change notification settings - Fork 992
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
Blank Screen-DroneDB Import #1563
Comments
Also, I have updated Linux, Docker, and the WebODM to the latest version. In both the console logs of WebODM and DroneDB I am not seeing an error. |
I'm experiencing this exact same issue. To expand a bit more on the steps to reproduce:
The react error message suggests using the development build when debugging instead of the minified version. I'll confess I'm not exactly sure how to do this but happy to try with a pointer in the right direction. I flipped through the Dockerfile & start.sh but it's a bit hard to parse as I have no background with react/npm/webdev. The same errors occur in up-to-date versions of both Firefox & Chrome Thank you! |
CC @HeDo88TH |
We are investigating the issue. EDIT: The issue is confirmed, we are making a fix. |
At first glance nothing has changed dronedb-side. This is the error
It seems that the "cloudimport" plugin gives the same error. Did anything change in the underlying react/libs of plugins? @pierotofy |
I don't remember making breaking changes, but that error comes from a Modal which is part of |
By setting a precise version in package.json the dialog now opens: When starting the import process a new error (very similar appears):
Progress can be tracked on #1576 |
Closed via #1576 |
How did you install WebODM (docker, installer, etc.)?
I installed WebODM using Docker on a Linux VM running Ubuntu 22.04.5.
What's your browser and operating system? (Copy/paste the output of https://www.whatismybrowser.com/)
Chrome 129 on Windows 11
What is the problem?
When I use the DroneDB Import button, the page displays a blank screen with only the header and navigation visible. This issue occurs for both a self-hosted DroneDB and a cloud-based one. As a follow-up, I can confirm that I am able to export to DroneDB successfully.
How can we reproduce this? (What steps trigger the problem? What parameters are you using for processing? Include screenshots. If you are having issues processing a dataset, you must include a copy of your dataset uploaded on Dropbox, Google Drive or https://dronedb.app)
Currently running version 2.5.5 on WebODM. Enable and configure the prebuilt DroneDB plugin.
The text was updated successfully, but these errors were encountered: