Skip to content
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

Crash Problem #58

Open
freakmaxi opened this issue May 10, 2021 · 6 comments
Open

Crash Problem #58

freakmaxi opened this issue May 10, 2021 · 6 comments

Comments

@freakmaxi
Copy link

Hello, I am using the Mega IOS app on my iphone 11 pro. When I run the application it works, but it is crashing when I want to open it from Files app or want to use the share functionality of ios choosing the mega app or files app to load the files to my cloud account. I have pro II account in Mega.

@jnavarrom
Copy link
Member

Hello,

I am very sorry to hear this.

The problem is that to use MEGA, currently, we have to load all the account information into RAM and iOS extensions have a ram usage limit, that's why the File and Share extension crashes if your account has many nodes (files and folders).

Our SDK team is working to avoid having to load all account information into RAM. Unfortunately I can't give you an ETA.

Sorry for the inconvenience.

@freakmaxi
Copy link
Author

Thank you for your answer. Actually, It is a critical problem than you can imagine. I'll be perfectly happy if it can be prioritized.

@christophberger
Copy link

I face the same problem. Thanks a lot to the Mega team for working on a fix.

Until the fix is available, would it be possible to have the app show an error message instead of just crashing silently? Other users might observe the behavior as well. An error message would help them understanding the problem and possibly work around the issue by excluding nodes from the sync. (For me, this workaround is not an option unfortunately.)

@mhaeuser
Copy link

@jnavarrom Hey, is there any update on this? Thanks!

@jnavarrom
Copy link
Member

SDK development is in internal QA stage. We will prepare a version with the fix when our QA team approves the changes.

@christophberger
Copy link

Time flies!

What is the status of this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants