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
getParameters failed ( empty parameters ) for ZXing 2.4.1 on Android 11 #1011
Comments
We have the same issue on the 3.0.0 beta. Are there any steps how to reproduce it ? We have logs from prod, but couldn't reproduce it locally |
I have the same issue on multiple devices and multiple Android versions. I have yet to reproduce it deliberately, but according to the users it tends to happen mostly when the device orientation changes. There are also multiple other reports of the same problem here within the issues list (#1003, #924) that have (up until I last looked) not been addressed other than to suggest the 3.x version(s) - all of which still display the same problem. |
I also have this issue. Multiple devices and multiple crashes per day on each. One user has orientation locked and is still experiencing the crash. I am unable to reproduce it, seems random. |
Is this product even supported anymore? I havn't seen any updates for a long time. I now also get this exact error but it is hard to replicate.
|
One way we where able to duplicate is:
At this point and before the scanner opens we would CheckAndRequestCameraPermissions using Xamarin.Essentials. If they have yet to Accept or Deny permissions it will prompt them to do so. Once they Accept we then would go and do our normal camera/scanner startup. At this point it would crash. if you would go in and try it again it would work being they already accepted the permissions. Our solution was to add a Delay of 100 milliseconds after they accepted the permissions and before they open the camera. So it appears for us that if the camera opens up to quickly after they accept the permissions it would fail. |
5 years this issue persists, and it's not acceptable for our applications to CRASHE violently in production :-( Related Issues : #728 #924 #1011 (and maybe more ? I stopped my search here...) A pull request #1002 has been kindly submitted by @rdfordatascience-ops (thanks ;-)) but has never been merged, accepted or included in a new version... So :
https://www.nuget.org/packages/Respawnsive.ZXing.Net.Mobile/ -> 1 hour, that's all what it takes to me... So I hope this will be usefull for some peoples... because the "real production world" is not focused on MAUI (not yet at least ;-)) |
I am also seeing this happening I haven't looked at causes at all but this IS a issue that needs looking into |
Error : Unhandled Exception
System . Exception : CurrentDom ainOnUnhandledExCeption ---> Java . Lang . RuntimeException : getParameters failed ( empty parameters )
at Java . Interop . JniEnvironment + in stanceMethods . CallObjectMethod ( Java . Interop . JniObjectReference nstance ,
Java . Interop . JniMethodInfo method , Java . Interop . JniArgumentValue * args )[Ox0006e] in :0
at JavaInterop . JniPeerMe mbers + JnilnstanceMethods . InvokeVirtualObjectMethod
( System . String encodedMember , Java . Interop . lJavaPeerable self , Java . Interop . JniArgumentValue *
parameters )[Ox0002a] in :0
at Android . Hardware . Camera . GetPara meters ()[Ox0000a] in <0052a949de514c3fa49f58e679d0986c>:0
at ZXing . Mobile . CameraAccess . Cam eraControler . ApplyCameraSettings ()[0x00033] in <819b29aa6d91462699e19a679be55a44>:0
at ZXing . Mobile . CameraAccess . C ameraController . RefreshCamera ()
The text was updated successfully, but these errors were encountered: