-
-
Notifications
You must be signed in to change notification settings - Fork 982
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
Multiple Selection mode crash when photo library is empty #347
Comments
We're seeing the same crashes in our app. |
@daveleenew what is the status for this issue? |
Sorry i don't know. Please contact the author.
「Victor Mihaita <[email protected]>」在 2019年5月31日 週五,下午2:57 寫道:
… @daveleenew <https://github.com/daveleenew> what is the status for this
issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#347?email_source=notifications&email_token=AIGMU6LA2AFHYAKYQQKJDA3PYDD53A5CNFSM4HL5OFOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWUMCUY#issuecomment-497598803>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIGMU6N3BZIMD6337RPW6YTPYDD53ANCNFSM4HL5OFOA>
.
|
Having similar issue where pressing multiple selection button after denying photo library access permission results in a crash |
Update: Just hid the button on first launch until permission is checked public override func viewDidLoad() { |
This should be fixed with @hansemannn PR. It will be in the next version, hopefully by the end of the week. |
Describe the bug
Multiple Selection mode crash when photo library is empty
Temporary solution:
YPLibraryVC.swift
if selection.isEmpty {
///Temporary solution:
if(mediaManager.fetchResult.count == 0){return}
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Installation Type
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: