Hello,
We are using the TC26 and TC27.

In our custom application, we utilize the EMDK and have adhered to the programming best practices outlined here: Zebra EMDK Programming Practices.
We want our application to run on both Zebra and Non-Zebra devices. So we do the check as described in the before mentiond Programming Practices.
However, after updating from Android 13 to Android 14, we've encountered an issue with the EMDK version check that employs the PackageManager. The following code snippet, recommended in the programming practices, no longer functions as expected, the EMDK service does not exist on the device:

try {
    String emdkPkgName = "com.symbol.emdk.emdkservice";
        PackageInfo pinfo = getPackageManager().getPackageInfo(emdkPkgName, 0);
        String emdkVersion = pinfo.versionName;
} catch (PackageManager.NameNotFoundException e) {
    // EMDK does not exists on the device.
}

With:

<uses-permission android:name="com.symbol.emdk.permission.EMDK" />
<queries>
    <package android:name="com.symbol.emdk.emdkservice" />
</queries>

Upon investigation, it appears that the emdkservice is no longer running on devices updated to Android 14. I've checked this with adb. 

adb shell dumpsys activity services com.symbol.datawedge.emdkservice 

Which returned 0 results on the latest Android 14 Zebra release. (it does on Android 13).

Now the Programming Practices documentation we have used and linked above have been written for Android 13.0, but these have not been changed since Android 11.0. There is no updated documentation page for Android 14.0 yet.

Could you please confirm whether this programming practice is still valid for programmatically checking the EMDK version on devices running Android 14? If not, what alternative method would you recommend for retrieving the EMDK version in this environment? I know it can be checked with the EMDKManager, but we need to do the check before this is initialized.

I have noticed there is a EMDKService running on Android 14:  com.symbol.datawedge/.EMDKService
Did the package name change?

Thank you for your assistance.