Please be aware that this application / sample is provided as-is for demonstration purposes without any guarantee of support

This repository is out of date - please refer to the updated 'getting started' guide at https://github.com/darryncampbell/DataWedge-GettingStarted-Samples

DataWedge-Intent-Example-4

This application shows how to configure the DataWedge service through the DataWedge API on a Zebra mobile device with a Xamarin application. Compare this with the Android equivalent of this example.

• Build application with Visual Studio & Xamarin
• Install application on Zebra device
• Observe that the scanner can be controlled with the buttons on the UI. Scanned data is inserted into the text area
• If the UI buttons do not work or scanned data does not appear in the text area, see troubleshooting below

Troubleshooting:

DataWedge Version

This application will only work on Zebra Android mobile devices running DataWedge 6.3 or higher. To check your datawedge version, launch the DataWedge application then go to the menu (3 dots), then 'about':

It is possible to use a version of the DataWedge APIs that work on 6.0 or higher, for the sake of simplicity I have used the more recent 6.3+ APIs in this example but you can see the 6.0+ APIs in my more fully featured project (Note the more fully featured project is Android only).

Vysor or other keyboard applications

This application depends on DataWedge sending keyboard output to the application after a successful scan. Vysor has been known to interrupt this workflow, it is recommended to uninstall Vysor or ensure a non-Vysor keyboard is selected (you may need to select the Vysor keyboard and then re-select the Google keyboard):

DataWedge configuration

Unless you have changed any of the DataWedge configuration on the device, this application will use the default profile (Profile 0) with:

• Barcode input Enabled with common decoders
• Keystroke output Enabled

If you have changed any of these settings then you may find the application does not work e.g. disabling keystroke output or disabling the default profile.

There are multiple ways to resolve this including:

• You can restore DataWedge back to its default settings from the DataWedge application --> Menu (3 dots) --> Settings --> Restore
• You can create a new profile and associate it with this application, ensuring Keyboard output is enabled.