It turned out there were 2 issues causing this same end result. 1 was
front end (dev), 1 seems to be an Adobe back end issue. 1 - Front
endDeveloper forgot to put the lifecycle start code into their
app...@Overridepublic void onResume() { super.onResume();
MobileCore.setApplication(getApplication());
MobileCore.lifecycleStart(null);}@Overridepublic void onPause() {
super.onPause(); MobileCore.lifecyclePause();}When lifecycle start was
included the device was registered correctly. 2 - Back end is...