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

Navigation back pressed #133

Closed
vcirstea opened this issue Aug 12, 2015 · 10 comments
Closed

Navigation back pressed #133

vcirstea opened this issue Aug 12, 2015 · 10 comments
Labels

Comments

@vcirstea
Copy link

Hi,

When pressing back navigation button (Photos) with or without selecting image(s) freezes the app. Processor goes to 100% and need to kill the app.

I'm using iOS 6.4 for testing and this occurs on iPhone simulator and real device (iPhone 6/iOS 8.4).

Can you please point me to the right direction?

Thank you,
Vlad

@Dids
Copy link

Dids commented Aug 12, 2015

+1

Also just noticed this, no idea what's causing it. Easily reproducible.
Note that this also happens even if you have an asset selected, as long as you press the back button.

@Remyoman
Copy link

+1

Happens when I go back from an album and then press cancel, otherwise it dismissed as usual (in the album selection).

@Dids
Copy link

Dids commented Aug 12, 2015

I do recall this working the last time I used it, which was 3-4 days ago, meaning that the last commit(s) might've broken it.

@Dids
Copy link

Dids commented Aug 12, 2015

I can confirm that reverting back to v3.0.0 "fixes" the issue, so for now, just downgrade until this gets fixed.

@1and2papa
Copy link
Owner

Thanks for all reporting this issue. Will put it in first priority. In the meanwhile, please fallback to v3.0.0 as suggested by Dids.

@vcirstea
Copy link
Author

Thank you for your prompt response!

@1and2papa 1and2papa added the bug label Aug 13, 2015
@1and2papa
Copy link
Owner

This commit, f82fca5, introduced captioned issue. I have no clue why it freeze the app. I might need more time for fixing it.

@1and2papa
Copy link
Owner

Found a proper way. Please update to v3.0.2.

@Dids
Copy link

Dids commented Aug 14, 2015

Can confirm that this is indeed fixed, thank you!

@1and2papa
Copy link
Owner

That's good.

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

No branches or pull requests

4 participants