EMDK Intent not working with EHS auto_launch

I am trying to get the following scenario to work:

* I have a Zebra MC33 running Android 8.1
* The device needs to run one simple app that has one activity which is an EMDKListener and reacts to one intent
* I want to use EHS to restrict the device to this app only

So far I have found everything I need, except for one oddity:
If I autostart the app in EHS (via <auto_launch> or <kiosk>), the app does not react when scanning. After disabling autostart and starting the app by tapping the icon it works normally. Attaching a debugger while the app is running autostarted doesn't even hit the breakpoint of the scan arriving in the app.

The relevant passages from the enterprisehomescreen.xml file are:
<config>
<auto_launch>
<application delay="5000" package="com.mycompany.myapp" activity="" />
</auto_launch>
<!-- ......... -->
<preferences>
<auto_launch_enable>1</auto_launch_enable>
</preferences>
</config>

Can anyone point me into the right direction?

Darryn Campbell
Are you using DataWedge or

Are you using DataWedge or EMDK for scanning?  I ask because I am confused when you talk about the EMDKListener reacting to an Intent

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Jeanne Fayolle
I don't know, how can I tell?

I don't know, how can I tell?

I have a native Android App where I configured some parameters in the EMDK Manager Plugin in Android Studio and my one activity in the app implements the EMDKListener interface.

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Darryn Campbell
Can you please share your

Can you please share your EMDKConfig.xml, it can be found in the assets directory of your application and would have been created as a result of using the EMDK Manager Plugin for Android Studio.

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Jeanne Fayolle
This is the generated

This is the generated EMDKConfig.xml: https://pastebin.com/LAg0ViBF

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Darryn Campbell
You have:

You have:

<parm name="package" value="com.mycompany.mobileapp"/>

I presume you have anonymised this but is it the same as your app.  You may want to go into the profile by launching the DataWedge application on the device and ensuring it is associated with your application, which can be found after you select the profile under 'Associated apps'. 

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Log in to post comments