Doesn't work on Android 14 #1077
Comments
|
Does Logcat provide any information in this case? |
|
The whole Logcat output: |
|
The following indicates you have an issue in your code, relating to the Hero tag of floating action buttons. It seems your FloatingActionButton widgets all use the default hero tag, which is the cause of this error. Can you provide each with a separate Hero tag? |
|
Thanks for your follow-up. But I don't think that was the error related to the mobile scanner. With the same error, the mobile scanner works on all other Android versions (6.5 to 13), tested. And on the mobile scanner screen, I don't have the floating action button. I have the floating action button in the previous screen, when you click on that button it takes you to the mobile scanner screen. Please, find the attachment, the camera opens as expected, but no barcode is captured/detected. I think the ML Kit part not working.
|
|
In case of barcode errors, we do provide them as error events in the barcode stream from the native side, but we do not provide those details to users. I can look into forwarding these as error events in the stream of barcode events. (so that these show up in I added a note to the issue description to explain what I think might be happening. |
|
Thank you. I'll be waiting. My app get stucked for it and can't go to production without solving this. |
|
Hi @navaronbracke, do you have any recent plan to address this issue. I'm just stuck by it and waiting to release my app. Your co-operation will be greatly appreciated. Thanks in advance :) |
|
Hi @tanvir93, I can get started on adding this to the in-progress PR: #1086 That PR unified how we handled barcode errors in the plugin itself. On top of that, I will add some extra code to forward the barcode error events to the I can do this in a relatively small timeframe (if I can spend the time working on it). |
|
Hi @navaronbracke, sounds good. Let's learn what is happining, first. And then we can plan to fix it. I'm waiting. Please, let me know you finish your part. |
|
Hi @navaronbracke, I tested the MLKit standalone. And it works on Android 14 as expected. So, I think there is a bug in mobile_scanner
|
|
@tanvir93 Good to know. Could you provide a minimal reproducible sample of the native Android project you used to test with? Then I can look into comparing the two to see what is wrong. In the meantime, I am still going to prepare the change to the MLKit error events, perhaps that also gives us a clue. |
|
Hi @navaronbracke, thanks for your follow up. There you go: https://github.com/Apparence-io/CamerAwesome/blob/master/example/lib/preview_overlay_example.dart I tried the MlKit with CameraAwesome following the above example. That works perfectly, withouht any modification. I'm sorry to response back in a bit of late. I'm going through tight schedule. |
|
We got reports that this happens on some devices with Android 14 (Samsung Galaxy A23 5g) but not on all |
|
@f1sh1918 Thanks for confirming that this is device specific. I do not have a Galaxy A24 available to test on, though. Could you try testing out this patch on that device? #1086 That patch includes forwarding any of the MLKit error events that occur during scanning, as error events of the barcode stream. Inspecting the error events coming from the barcode stream would be very helpful. If you see any errors come up in the stream, do post them here, so I can try and figure out why this is happening. I'd love to get this bug fixed, but I need to know what's going on first. |
|
We just ordered this device to reproduce. Its not occurring on all android 14 devices which is good but even harder to debug. Update: |
|
Can confirm this issue also happen only in android 14, Running pixel 7 with the selected android version also facing the same issue |
|
@arifinreinaldo Any chance you could try out the patch mentioned in #1077 (comment) and see if anything comes out of the error details on the stream? |
Hi, I have tested this patch and I can see the camera scanning the barcode and QR code test case that I have |
|
@arifinreinaldo So that patch does work with Android 14? And you get no errors from the stream? @f1sh1918 Do you see the same behavior? Or do you see errors in the stream? |
So far I don't see any error, but I also attach the log file in case I might miss something |
|
Sorry, I should have clarified better. With the new sample, if you do do you see anything in that |
Hi I have tried few times but I don't see from my testing. Thanks |
|
It will take some time since the breaking changes from v4 to v5 for me to provide you some information |
|
But the issue is related to that |
|
will the fix merge with the this package @navaronbracke ? |
That indeed seems to be the workaround for this issue. Unfortunately since this is a bug with a specific device / camera combination, we cannot do much in the plugin. @arifinreinaldo To answer your question, yes the plan is to land the patch relating to the onError handler. But as mentioned above, this does not solve the device specific bug. |
|
For easier tracking, and now that the root cause seems apparent, I am going to close this issue, in favor of #1116 Please comment on that issue if you have further comments / observations. |
After some investigation, this seems to be related to #698 which indicates Android probably needs to use NV21 instead of YUV
I got this package as a charm.
I tested this package on Android 6.5 (API 23) to Android 13.0 (API 33), and it works perfectly.
But it does not work on Android 14 (API 34). The camera opens as expected, but no barcodes are captured/detected, and there is no error log.
Any of you are experiencing this? Got any solution?
The text was updated successfully, but these errors were encountered: