I Updated the Datawedge.db on our devices just yesterday and i can only confirm what Matt is saying.

Running on latest Lifeguard Update for Oreo.

Are you running the latest firmware etc.? As far as i know android 10 and 9 should be available for TC52.

The following Post-Install script consistently works for me with AEDO managed Zebra devices, including the TC52. This appears to match what you have. 

__chmod 777 /enterprise/device/settings/datawedge/autoimport/datawedge.db

Maybe the datawedge.db is corrupt or doesn't match the device? What happens if you manually adb push that .db file to that location on the device, does it import successfully?

Hi Matt, I appreciate the input. I performed some additional testing this morning and this is what I found.

• TC52 w/ Android 9.0 (June 2020 Patch Level) - ADB push and File Sync rules work for both DataWedge configs and profiles. No issues.

• TC52 w/ Android 8.1 (July 2019 Patch Level) - ADB push and File Sync rules DO NOT work for any DataWedge config or profile. I originally thought it was an issue of building a DataWedge profile on a newer version of Android 9 and pushing it to an Android 8.x device. But even if I create the same profile on an Android 8.x device, reset DataWedge to factory defaults, and push it back to the same device, it won't import. I even performed an enterprise reset on the device with no luck.

It's really odd, but if using Android 9 is the solution, then okay. That works.

I was having the exact same issue as the original post.

This is what I did:

I noticed that after turning ON the Auto Import option through StageNow, the DB files are getting installed.

So I run this script in the POST INSTALL:

copy \sdcard\dwprofile_OWN_NAME.db enterprise\device\settings\datawedge\autoimport\

mxconfig /sdcard/Datawedge.xml
reset /s (optional)

The DB files are not send to the autoimport folder directly, as you can see in the POST Install Script:

The DATAWEDGE.xml contains this option:

This works for me!Another option would be to use the 'DataWedge configuration file' option and set it to somewhere inside of your %SDCARD% and push your DB file to that specific folder. I tested that and can confirm that also worked for me.

Hi Ryan Grimm,

Did you get a chance to try the above method mentioned by Yannick to import the DataWedge profile?

If this post has helped you in solving your inquiry, I would request you to mark the particular comment as "is solution", so others may benefit from this information.

Regards,

No, I'm afraid that due to certain timelines we ended up moving to Android 9 upgrades to resolve the issue.

Thanks for confirming Ryan.

Regards,