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

[BUG] Crash in ownCloud File Provider #1266

Closed
marcomasser opened this issue Aug 3, 2023 · 4 comments
Closed

[BUG] Crash in ownCloud File Provider #1266

marcomasser opened this issue Aug 3, 2023 · 4 comments
Milestone

Comments

@marcomasser
Copy link

I noticed a crash in the file provider extension because Files.app showed an error about content not being available (sorry, I forgot to take a screenshot and don’t remember the exact wording). I haven’t come across this before, so I looked into the analytics section of Settings.app and found one crash log: ownCloud File Provider-2023-08-01-221518.ips.zip

Steps to reproduce

Unknown. This only happened once so far and it’s not clear what triggered it.

Client

iOS version: 16.5.1 (iPadOS, actually)

ownCloud app version: 12.0.3 (274)

Device model: iPad 8th generation (iPad11,6)

@michaelstingl michaelstingl added this to the 12.0-Current milestone Aug 3, 2023
@michaelstingl
Copy link
Contributor

ownCloud app version: 12.0.3 (274)

Another? crash was fixed in the 275 build:

Maybe it solves your crash too?

@marcomasser
Copy link
Author

Thanks for the hint, I will make sure that build is installed and report back in case this comes up again. But as I don’t know how to reproduce the crash, it might just not happen again. Feel free to close this issue and I’ll reopen it if necessary.

@felix-schwarz
Copy link
Contributor

Thanks for sharing the crash log. It pointed to a strange issue where iOS invokes a FileProvider method with a nil parameter for which nil values aren't allowed, leading to an exception in another system call that doesn't allow a nil parameter.

In build 276 (currently processing in App Store Connect, should be available within an hour via TestFlight), I added a mitigation for that case, so iOS using a nil parameter where it shouldn't should no longer lead to a crash.

@marcomasser
Copy link
Author

Oh nice, thanks!

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

3 participants