Issue with Socket Scanner in Google Playstore and AppStore

[Joshna1016]

Team,

MAUI mobile application is crashing when we try to scan BarCode using Socket Scanner.

iOS Version >18.* and MAUI version .Net 7

Could you please let us know if we need to change any thing in our code to achieve this.

[Benjamin-Socket]

Hi @Joshna1016,

To investigate this issue, I'll need to have some more information:

• What version of the SDK are you using?
• What version of Android are you targeting?
• Is it possible for you to use .Net 8 instead of .Net 7?
• Do you have Companion installed on both Android and iOS devices?
• Do you have any logs on the crash?
• What are the exact steps to reproduce the crash?

Then, for iOS, Info.plist needs some additions, you can check "https://docs.socketmobile.com/capture/csharp/en/latest/gettingStartediOS.html".

For Android, the AndroidManifest.xml also needs some additions, you can check "https://docs.socketmobile.com/capture/csharp/en/latest/gettingStartedAndroid.html".

Thank you,

Benjamin Goltz
SDK Engineer
Socket Mobile

[Joshna1016]

Hi @Benjamin-Socket ,

Thanks for the suggestions, we will try with the same. Please find required details from below

What version of the SDK are you using? --> 1.5.7.434
What version of Android are you targeting? --> 34
Is it possible for you to use .Net 8 instead of .Net 7? --> We are now live with both Client and MAUI with .NET7 it will be complex to upgrade complete application.
Do you have Companion installed on both Android and iOS devices? --> Yes
Do you have any logs on the crash? --> No, We will update once we get crash report
What are the exact steps to reproduce the crash?
Steps to Reproduce:
Connect Scanner from Companion application.
Navigate to MAUI application and set Socket Scanner as Scanner Option.
Scan BarCode.
Application is crashed.

[Benjamin-Socket]

Hi @Joshna1016,

Thank you for the information. Alright, first what I suggest is that you get the latest version of the SDK, version 1.7.34.67 and see if the application still crashes. Then, if it still does crash, could you share parts of your code that uses the Socket Scanner (do not include the appId, the developerId, the appKey or any sensitive information)?

Thanks

[Joshna1016]

@Benjamin-Socket ,

Thanks for the suggestions. We are able to resolve scanner issue on iOS. Still we are facing below issue in Android.

One or more errors occurred. (One or more errors occurred. (One of RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED should be specified when a receiver isn't being registered exclusively for system broadcasts))

Could you please share details for below queries

1. Behavior of Barcode scanning from MAUI application for different barcode types like CODE128, CODE39..etc
2. To scan Barcode from a distance of 50cm do we need to add any specifications or settings or properties in SDK?
3. To scan Barcodes in optimal light, low light do we need to add any properties/ specifications?
4. Barcode optimal size scan from 50cms distance .

[Benjamin-Socket]

Hi @Joshna1016,

I'm glad to hear that the scanner issue on iOS was resolved.

For Android:

• Are you trying to run the Maui Sample app or did you make your own version? With this info it could be easier for me to pinpoint the issue.
• Are you using any of the following methods from the CaptureHelper class? StartAndroidService(), IsAndroidServiceInstalled() or IsAndroidServiceRunning? If yes, then remove any references to them to see if it solves the issue.
• What version of Companion are you using on Android?
• Does the issue occurs during build or runtime?
• Could you check the Android logs via Logcat and look for this type of error for more information?

  E/AndroidRuntime: FATAL EXCEPTION: main
      java.lang.IllegalArgumentException: One of RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED should be specified when a receiver isn't being registered exclusively for system broadcasts
      at android.content.ContextImpl.sendBroadcast(ContextImpl.java:...)
      at com.socketmobile.capture.StartService.StartAndroidService(StartService.java:...)
  

For the queries:

The answers does depend on the model of scanner you have (e.g. model S720). You can check this page to get the datasheet of your scanner: https://www.socketmobile.com/support/downloads?categories. Depending on the model, you'll have supported symbologies and reading distances per symbology.

There is no setting in the SDK for range or optimal/low light configuration. The scanner should be equipped with its own light.

Let me know if this helps or if you have any questions.

Thanks

[Joshna1016]

@Benjamin-Socket

We followed the instructions that we suggested by you and found that error was resolved but the "Socket" is not connecting to the application in Android.

Also tried to give the application as attachment in .NET 7 with our Socket Scanner code. However we are unable to do so as the Microsoft has stopped support for .NET7

Please suggest the best way to achieve this as we are moving to PROD , we need your support.

Socket Models that we have right now with us : D700, S700, CHS7CI

Could you connect with us or schedule a meeting so that we can resolve this issue in meeting itself.

Thanks in advance,

[Benjamin-Socket]

@Joshna1016

Alright, let's connect to resolve this issue. Here are my availabilities:

• Today between 1 PM - 5 PM
• Tomorrow between 9 AM - 11 AM and 1 PM - 7 PM
• Other days between 9 AM - 7 PM

Let me know what suits you best.

Note: I'm using UTC+1 for the time zone.

You can either contact me directly on my email: benjamin@socketmobile.com or you can share your email so that I can send you a meeting invitation.

Thanks

[Joshna1016]

@Benjamin-Socket

Could you please confirm your availability on 31 January 2025 on 10AM in your time zone to connect?

Here is my email to connect : jlingala@quiktrak.com

Thanks

[Benjamin-Socket]

@Joshna1016

31 January 2025 at 10 AM is perfect. I'll send you an email with the invitation.

Thanks

[Joshna1016]

@Benjamin-Socket ,

Could you please share any update on this?

Thanks in Advance

[Benjamin-Socket]

@Joshna1016

I was able to reproduce the -27 error issue. Please follow the steps below to fix this issue:

1. Remove any Socket device from the Socket Mobile Companion app (remove reader at the bottom of the page) then close the app
2. In your Android settings, unpair any Socket Device in Settings->Connections->Bluetooth->[Socket Device]->Unpair
3. In your Android settings, Clear cache and Clear data of the Socket Mobile Companion app in Settings->Apps->Socket Mobile Companion->Storage
4. Start Companion app and allow Bluetooth then add your scanner (lets say the S700)
5. Start your app and check if you still have the -27 error after Opening CaptureHelper instance (.OpenAsync())

Let me know if that worked for you

Thanks

[Joshna1016]

@Benjamin-Socket ,

We have tried the shared suggestions and still the issue remains same. Could you please help us resolving this issue.

As we need to release android version into play store in coming 7 days. This will be a blocker for us.

Request you to look into this on high priority.

Thanks.

[Benjamin-Socket]

@Joshna1016

I'm working on the issue. To help me debug this could you provide logs from your Android device via LogCat precising the time when the error -27 appears.

In the meantime, could you retry the five steps I've mentioned above but between step 3 and 4, uninstall Companion and reinstall it. Let me know if this works. Also make sure you have the latest version.

Something else you could try, I've noticed that you were developing on a Mac, would it be possible for you to build and run via a Windows machine? You could use a sample app just for a quick test.

I'll keep working on this issue but your logs would be very helpful.

Thanks

[Joshna1016]

@Benjamin-Socket ,

I have tried all the steps shared multiple times and getting the same result i.e., -27.

Please find logcat file for capturesdk sample that is available in GitHub repo from the attachment.

CaptureSDKSample.zip

Could you please share resolution for this issue. As this is blocking us from the release.

Thanks.

[Benjamin-Socket]

@Joshna1016

Thanks for sharing this log. I'll review in depth and see if I can find the issue.

Thanks.