-
Notifications
You must be signed in to change notification settings - Fork 877
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
captureImage callback not being called #467
Comments
@UmarBhutta thanks for the issue. To help us better diagnose could you provide some more information about your setup.
Closing this issue for now, I'll reopen when you respond with the information. Thanks again! |
It can happen even when not clicking fast, just calling it several time in a row will break the captureImage randomly.
Thank you! |
Confirming - Pixel 3XL. Android 9. When I capture a couple times in a row, no callbacks are called from CameraKit. Not from captureImage, nor errorListener. Interesting fact - when you stack "clicks", take app to background and bring it back, callback is delivered with the latest captured image. Here are some random logs pointing on CamX:
|
XML
Implementation:
|
Same problem here.
by
in Any news @emersoncloud ? |
My implementation is simple that is mCameraView!!.captureImage { cameraKitView, bytes -> and xml is
while version i am using is can you guide me how to solve it |
Same here, Pixel XL, Android 9
|
@UmarBhutta my experience lines up with your video This is what I was seeing
@MaximeMaravalLunabee I think my fix also fixes what you were doing kinda fixed #504 @emersoncloud |
That CaptureStillImage from both the front and back camera fixes this problem for me also, but I assume there is a good reason it isn't supposed to work that way. Looks like when Interestingly when I closed my phone screen the callback immediately got triggered repeatedly, first resulting in ramping up the |
same issue on Nokia 7 plus (Android 9). With the code below the callback is triggered very randomly: (camerakit:1.0.0-beta3.11, jpegkit:0.1.0)
|
Same issue on Xiaomi 8, Android 9. This problem occurs after a few normal calls. Once the callback is not called, it will never be called again unless you re-enter the app. XML:
Java code:
|
Any update about this issue? I have the same problem. |
As far as I see there is a Pull Request to solve this problem... When will be available a release with this? |
We are not ignoring this, and plan to be back in touch by next week. This is one of our biggest bugs we plan to resolve. Thanks for the healthy discussion around this! |
Very nice, thank you for the update and also for the great work, this library is great! |
Same here, capture Image is called very randomly OnePlus 5t |
Hi any updates on this issue |
sorry to ask, is this one already fixed in 3.12-expensify? |
I have the same issue on HMD devices. Specifically HMD Global TA-1052. |
same issue |
Samsung Galaxy S8, Android 9 - same issue. |
¿How did you manage to import the library as a module? |
Same issue here, very frustrating and I can't seem to find a way around it |
Any updates for this issue? |
I have the same issue with Samung S7. |
Same issue here with Samsung S10. |
I think it might be because of the type of threading for me. I called it within asynctask, I'm trying to use Handler instead. |
Same here Samsung S6 |
It works with Handler |
@roya90 Can you show an exaple please? |
I changed back to using the regular camera, but I found this link very helpful. https://www.youtube.com/watch?v=adPLIAnx9og |
Essential Phone PH-1 |
Downgrading to beta3.10 worked for me. |
Same, it works on my emulator now. |
Same here with Nexus 5 and beta3.11. |
@jtn-d go back to the original camera. Check out this link https://www.youtube.com/watch?v=adPLIAnx9og |
Same here with Xiaomi 8, Android 9 and beta3.10 |
This is very long long issue and still not resolved. I do, have the same problem. |
The same problem on Honor 20. We are waiting for the fix for 6 months already. |
Same issue here, it pretty a major issue. Same effect with focus=continuous or focus=auto, no callback ever call to really take the photo as the library propose to. Downgrading to 3.10 by:
|
thanks. i have same issue. -> Downgrading to 3.10 |
Thanks |
Thanks, this also worked for me |
when i downgrade to beta3.10, i got this error :
|
I have fixed in my case when remove this
|
Couldn't take a picture using this library even with all answers above :[ |
same issue |
Nokia6 Android9 is same issue |
Xiaomi Redmi Note 8, same issue. Downgrading to 3.10 solved the problem. |
According to my problem, there is multiple activities open and in background. LG Nexus's prints error; multiple camera clients active. It is difficult to destruct activities from background, have tried many methods. Hopefully .onClose() really frees all allocated resources. Some explicit destroy()-method would be nice. |
After updating my project with new version(1.0.0-beta3.10 and 3.9) of camerakit and migrating to kotlin 1.3.11 for and coroutines 1.0.0 rapid calling for the image capture callback is being lost.
if you try to call captureImage method very quickly like clicking very fast. You will not get any callback for that click. Any suggestion?
The text was updated successfully, but these errors were encountered: