Open singhayushh opened 9 months ago
I think it's the same issue as in #2300 which is open since Apr, 2023. I'm using bspwm btw.
I can contribute to fixing the issue if I can get some insights.
Have you tried to upload a file by just ignoring the error message?
@annieappflowy the file manager itself doesn't open up so that I can select files. I tried dragging and dropping as well, didn't work too.
Same problem here using awesome VM. I think it works with gnome but don't have any desktop environment based on it to try :/
@singhayushh I can confirm it's the same problem of the https://github.com/AppFlowy-IO/AppFlowy/issues/2300 issue :)
2024-02-02 07:32:47 ERROR Uncaught platform error
at dart-ffi/src/lib.rs:178
2024-02-02T06:32:47.539221Z ERROR dart_ffi: Uncaught platform error
at dart-ffi/src/lib.rs:178
It's the same problem with the button export > markdown
Hello!
The above issue has been resolved in the latest 0.4.6-1
version of AppFlowy.
This issue can be marked as closed!
Hello,
Not for me on the latest 0.4.6-1
, using the AppImage
version
2024-02-06 04:54:01 ERROR Uncaught platform error
at dart-ffi/src/lib.rs:179
2024-02-06T03:54:01.881285Z ERROR dart_ffi: Uncaught platform error
at dart-ffi/src/lib.rs:179
This time, the error is on line 179 ;)
@Whax I'll try the AppImage out Could you share your os / wm / de till then?
@singhayushh
Hi @Whax, It doesn't seem to work with the AppImage executable.
However, it worked on installing from source // pacman
Can you share a sample file that you were tying to upload with us? We'll look into this issue.
Bug Description
The modal that opens on clicking the
Upload Theme
icon doesn't allow me to upload files on clicking theUpload
button from the modal. Instead it directly shows a messagePlease wait while we validate and upload your theme
.How to Reproduce
Settings -> Upload Theme -> Upload
Expected Behavior
Should open file manager to select files to upload
Operating System
Arch Linux
AppFlowy Version(s)
aur/appflowy-bin 0.4.3-1
Screenshots
No response
Additional Context
Went through the logs to find these error logs: