-
Notifications
You must be signed in to change notification settings - Fork 379
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 in AssetsViewController.photoLibraryDidChange #254
Comments
why use Is there a problem if I only handle it with
|
It won't crash if you use reload data, sure. Put a breakpoint in the performBatchUpdates block and figure out what is going on. Does it have incremental changes? Does it have deleted, inserted or moved items? And are we updating the collection view with those changes. I'll look into too whenever I have time. |
If the UI blinking is the only problem, is it okay to take temporary action by using I'm still analyzing it with |
If you are fine with that.
|
So I just tried reproducing the crash, but it works for me.
|
Yeapp, reproducible on iOS 12. Thanks :) |
Oh, this is not a crash that occurs only with iOS 12. It also happens in 13. |
Alright, worked for me on iOS 13 but crashes on iOS 12 :) |
Try 3.1.4 - it should be fixed now. Thanks for helping out :) |
Hi! Thanks for such a great library.
When I switched the app to the background, and launched the camera app to take a picture, when I came back to the foreground, it crashed in
AssetsViewController.photoLibraryDidChange(_:)
every time.The log is shown below.
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Invalid update: invalid number of items in section 0. The number of items contained in an existing section after the update (67) must be equal to the number of items contained in that section before the update (67), plus or minus the number of items inserted or deleted from that section (1 inserted, 0 deleted) and plus or minus the number of items moved into or out of that section (0 moved in, 0 moved out).
The text was updated successfully, but these errors were encountered: