-
Notifications
You must be signed in to change notification settings - Fork 0
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
No Image "Develops" after photographs #27
Comments
I'll keep an eye out for this one. |
@zspencer we don't have any information about the iOS version or device from this user, do we? |
No, but I would hope that we could learn how to instrument the applications such that when error reports come in we can trace them back somehow. Right now, we have a Sentry account and a Firebase account; but I am not familiar enough with the iOS EcoSystem to know how it all plays together. Perhaps check with @user512 about what he's seen? |
I think I can recreate the bug; but only intermittently.... If you use the camera and capture a photo every executes as it should. But, sometimes (not always) choosing an image from the on-device photo library will result in the image not "developing" on screen even though it will still be processed and saved into the library on-device. I am not sure; but it seems like the "developing" failure occurs with lighter images--that could be my imagination, though. |
Note to self: it appears to be a race condition. It's hard to reproduce. Choose an image from the image picker to "develop" and, BEFORE the animation completes, quickly choose the newly created, resulting image from the image picker to re-develop as quickly as possible . If you wait for the second development process you may see the empty frame. Best guess: this is probably related to multithreading and a background process. More later. NOTE TO CONTRIBUTORS: Please let me know if I'm too chatty in these comments. I can record my troubleshooting train-of-thought elsewhere if this is too verbose. |
Nope! This is perfect! Keep the notes flowin'! |
New Report:
|
Thanks for the report. I'm desperately trying to track down why it only
happens on some photographs and not others. There's some advanced math
that I'm brushing up on in order to run it down (hopefully). I just need
to find the time after my full time (overtime) job.
I'll squash this bug one day. Soon, I hope.
…On Sat, Dec 17, 2022 at 3:38 AM Zee ***@***.***> wrote:
New Report:
1.some photos gets all black results as the screenshots(it’s ok in the
album)
https://groups.google.com/a/zinc.coop/g/momentpark/c/XYafyTpka-w/m/7P27oigLDgAJ
—
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABASOYCD4PYK3D6BVJNBJULWNSZLDANCNFSM43EXBWXQ>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
No worries and no rush, we move at the speed we can safely move at. |
Hi, I sent in the original comment. I still get the error in this latest update (version 3.5.0). |
Hey @ErnieBarreto thanks, that is useful! We'll keep trying to isolate and fix it! |
…h the undeveloped view and polaroid frame
* issue #47 - remove forced size override. It was perturbing the position calculations in other methods. Need units. * remove dead code AND ensure that the photo picker can be cancelled cleanly * Create a method to encapsulate hiding/showing the toolbar in a clear and readable way. Migrated to Swift. * extend NSItemProvider to support properly WebP format (PNG-based and JPEG-based) * use weak reference to avoid retain cycle/memory leak * issue #27 - explicitly update the frame of the developed view to match the undeveloped view and polaroid frame * clean up: no longer need these statements (they were for debugging/troubleshooting). * super basic launch screen so the app reviewers don't deny the binary for using the 'old way' * Switch to SPM for Sentry integration (because of a cocoa pods bug that was preventing the release build with Xcode 15 on Sonoma
My instincts are there is a race condition somewhere in the process; and since the photo saves as expected this may not be urgent. Going to bucket it into 3.3.0 for now.
The text was updated successfully, but these errors were encountered: