Migration path from LinkOS 1.2 to LinkOS 2.15


Audience

Hello and thank you for reading the post.

We have an Android application built using Xamarin which prints on a Zebra ZQ510. The application targets min API of 26 and max of 29. We had deployed the app to inexpensive BLU phones API 28 and all was working well. (Using Visual Studio 2022)

We deployed same app to a new tablet device DigiLand API 29 and the printing stopped working, unable to discover device.

We noticed that our LinkOS version is 1.2 and the latest is 2.15. I think this is where the problem, at least its the only NuGet package NOT up to date.

Our questions:
1. Is the reason our app no longer works on API 29 because of LinkOS 1.2?
2. Is there a migration path or documentation for LinkOS 1.2 to 2.15?

Much thanks in advance
Aditya

Attachments
IMG_4619.jpg (4.06 MB)
Submitted by SSi1 on August 03, 2022 Permalink

Your app also needs to explicitly request the permission from the user. After the user grants the permission, then the Bluetooth discovery would work. Check the Android documentation on how to request the permission explicitly.

Submitted by aditya.arora@c… on August 03, 2022 Permalink

Yes, good point. We updated the permission in code as well to make sure we explicitly ask for AccessFine as well. The code started to work on API 30 but not the Digiland Tablet API 29. It may be worth noting the Tablet does not have a phone; I don't know if that matter.

Submitted by SSi1 on August 04, 2022 Permalink

It should work with the API level 29. Looks like the Digiland tablet may have a different way to manage the user permission. Go to the Settings -> Apps on the tablet and select your app. Then click on the Permissions to verify and grant the location permission from there.

Submitted by aditya.arora@c… on August 04, 2022 Permalink

I took a picture of that screen and uploaded it to this case. It looks like the permissions is there unless I'm missing something.