We've just switched to MobileIron here, using the per-app tunnel provided by
MobileIron. We hand off IPA files to our IT (which controls the MobileIron)
and they run it through MI system and publish it. MI wraps the app with some
type of protection so that it can operate through their tunnel
Xcode plays nice with subversion in all respects - checkout - status listing -
comparing with previous versions, except commit. And only on my home computer,
the same project commits fine with no complaints. The complaint I get is:
Commit failed (details follow):
Unable to connect to a
In my build results, I get a list of expiring or expired provisional profiles.
These show up as warning messages. Almost all of them have no connection to my
project, they're for other projects. Anybody have a way to get rid of them?
-Owen ___
Do
My build script has the pleasant feature of changing CFBundleVersion to the
current Subversion revision number during a build phase.
Here's the line of script code:
/usr/libexec/PlistBuddy -c Set :CFBundleVersion `svnversion -n`
${TARGET_BUILD_DIR}/${INFOPLIST_PATH}
Now that I've added a
