Mac Mini Profile Manager installing/updating ipad Apps - HELP!

Question

Hi,
i am hoping someone might be able to help with the following.
we have a mac mini server to remote manage 25 ipads using profile manager.
this works well as we can lock, wipe and clear passcodes etc.and attach the policies without any trouble.
However we are trying to push out an app (version 1.4) to the devices and this is sort of working but not fully.
if the app is already installed with version 1.3 it doesnt update even though in profile manager, 'active tasks' it says successful.
if you go go into profile manager and select the device and select 'update info' this registers against the device but still shows as the old version.
if we delete the app from our test ipad and push it out via profile manager it goes in active tasks as successful then the ipad has a pop up message box saying the xxxxxx.ourdomain.co.uk would like to install the app, once this has been ok'd it  installs on the ipad ok, but when you select the app it tries to open then goes back to the screen again and never opens the app.
if you download the app direct from itunes it opens with out any trouble.
here is the process i am using.
on the mac mini server.
download the app via itunes
then in apps i drag the app on to the desktop, this creates the .ipa file
in profile manager, select the device, edit apps and browse to the .ipa and upload
select the uploaded app and 'add'
when you save this, then go to active tasks it gets pushed out to the device and reports as successful
then the app either doesnt update if old version is installed or installs if no app is installed but doesnt open
any help welcome
regards
Gavin

Answer 1

Gavin,
We've run into the same issue that you mentioned. My understanding of the Push App functionality of Profile Manager is this:
Pushing apps is designed to be used to deliver In-House developed apps over the air (OTA). Meaning, if your organization develops an app for use on its own devices, you can upload the .ipa to Profile Manager and push it out while bypassing any App Store interaction. The In-House .ipa would contain its own provisioning profile that would dictate who is allowed to run it.
When you download an app from the App Store, the .ipa that you get actually contains the AppleID that was used to purchase/download the app in the .plist. If you then push that app to a device that has never been used with that AppleID, the app will fail to launch as it cannot verify that you actually own the app.
Before we go any further: what I'm about to discuss isn't officially condoned or supported by Apple, which means it is inheritly risky and could be patched over at any time.
In order to bypass the issue, what has worked for us is to sign into the App Store on each iPad with the AppleID that is used to purchase the apps on your Mac Mini. You need to download at least one app to the iPad while logged in with that AppleID in order for the iPad to retain the AppleID after the iPad users log in again with their personal AppleID. After you have done that, users may once again log in with their own AppleID.
At this point, you can push an app to any of those devices that have been paired with your Mac Mini's AppleID at least once. The apps won't (immediately) crash.
Here's the catch: I'm told that the .ipa contains an "expiration date" of sorts. Once that date has elapsed, your iPad will attempt to extend the expiration date by connecting to the App Store to verify that the same AppleID that was used to download the app in the first place is still active on the device. If it is not, the app may once again crash when you attempt to run it. Now, this expiration date or timer is not disclosed, meaning, if this is really the case, you will have no idea when the apps will stop working. It could be weeks, or months, or years. A gamble, really. So, use that at your own risk.
Currently, there is no official method for pushing App Store apps Over-the-air with Profile Manager or any other Mobile Device Management platform.
Remember!: If you are even considering pushing apps in the manner mentioned above, you will still need to account for licensing. As an organization, you must have purchased the same number of copies of an app as you intend to install on your devices. This is a non-issue with free apps, but for auditing purposes, you'd best look into VPP or steer clear of pushing apps altogether.
I hope some of that helped clear up your question.
Good luck!