-
Notifications
You must be signed in to change notification settings - Fork 2
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
No_key #11
Comments
Hi, I found out, that NO_KEY filename/dirname is set only for items that are copied / shared etc. |
I have searched for what could cause the NO_KEY folder, and it could be a one of a few causes: https://reddit.com/r/MEGA/comments/11u4v68/temporary_solution_for_those_having_undecrypted/ Because you can access the folder on the official Mega app, I think this is caused by the FsMega plugin using an older version of the Mega SDK. When I get some time, I will release a new version of the plugin that uses the newest version of the Mega SDK to check if this problem will be fixed. |
Thanks, I will wait :)) |
I have released a new version of the plugin that uses the latest Mega SDK version. Please try it out and let me know if it fixes the issue. |
As I'm on holydays now, I tested it quickly. All files / dirs looks good now. tested on fresh TC / W7 . Super work, thanks... |
Just tried MegaFS, works great. But one folder has NO_KEY instead of its name, and everything stored in it, including subfolders and their contents, has the name NO_KEY.
Am I doing something wrong or is it a bug?
here are screenschots from android, lin browser Firefox and mega addon TC :
https://mega.nz/folder/FJMTRJJL#xP95nVHJn4dd9LsueN7j9Q
The text was updated successfully, but these errors were encountered: