iOS Developer Enterprise Program

MDM APNS push notification problem.

Shivam's picture
Your rating: None (2 votes)

Hi,
We are trying to enroll iPhone devices with our 3rd party server,I downloaded the APNS certificate in the PEM format form the portal and installed it in the keychain access. I selected the APNS certificate (APSP:an23.....) and the private key that is associated with the MDM vendor certificate(Am i doing any mistake here???) and exported those into .p12 file. Using this .p12 file i am sending the wakeupcall to the iOS devices by sending push notification using python-apns library. I am getting feedback that the message is been delivered but the iOS device is not hitting back to the Checkin-url with the Idle status.Help is appreciated.
Thanks,

Let the App Migration start in the enterprise

Your rating: None (3 votes)

Apple, Inc. quotes “The iPhone is being used in 97% of Fortune 500, and the iPad is used in 98% of Fortune 500 and 93% of the Global 500 companies”.

What these numbers really mean? This means either employee bought their own devices (iPads, iPod Touch, iPhones) to connect to corporate network for checking emails or employee got their iPhone through corporate mobility programs or few brave companies deployed iPads for a specific use case.

What is their potential use? Mainly to use corporate emails, phone calls, imessages and other personal stuff.
While the devices are perfectly capable of handling many complex corporate applications that are in use as intranet applications or windows applications they are still restricted for several reasons until now. Even intranet sites are not mobile optimized to be viewed in iPhone or iPads. If you ask the question why, here are some obvious answers…

• We can’t manage iOS devices similar to how we manage windows laptops
• User experience is bad when they need to login through each App individually
• Data is not secured or encrypted on the device
• Secure connectivity to corporate network cannot be easily configured or managed
• App distribution is not easy – Users need to manually download the app and upgrade them
• Cost is high to develop enterprise Apps due to limited developers with Objective-C experience

At WWDC, Apple has clear response and answers for all these questions. With the introduction of new programming language “Swift”, opening up Touch ID and keychain to 3rd party Apps, App extensions, and B2B Apps they made adoption to enterprise easy and quick. There were several sessions focused on enterprise app development and deployment and dedicated resources to provide additional information. This will accelerate the migration of boring, non-intuitive windows applications and intranet sites to iOS Apps which will be secured, silently installed and managed by corporate programs.

Here are the details if you still think the questions are not answered…

list.png

Within the next few years this will change where new applications, functionality and use cases will be developed specifically for iOS devices once ROI (Return On Investement) can be justified through increase in employee productivity.

Stay tuned for more updates and feel free to add your comments…!

Signup for the iOS Developer Enterprise Program

cdburt's picture
No votes yet

Hello,
I have a dilemma. My boss wants me to signup for the Enterprise Developer Program but I don't have the legal authority to act on behalf of my company. This is the third time he has asked me to complete this task and I have explained I don't have the authority to complete the registration. I'm not sure what to do and want some advice to complete it or tell him what to do.

Can someone help me or has someone experienced the same problem with there boss and how did they solve it?

We also want to sign up for the Apple Deployment Program but it is the same problem with sign up.

Chris

Testing iOS Enterprise App Deployment

Your rating: None (3 votes)

My company Tekserve has helped a number of enterprises distribute in-house apps to their employees. All too commonly, the distribution is delayed due to problems with the app provisioning profile. Below is the test we use to make sure apps have a correct provisioning profile and can be distributed correctly.

Step 1: Prepare the iOS device

Make sure the device is not registered on the Apple Developer Portal. Devices registered here may be used for ad-hoc distribution, but that is more limited than Enterprise.

Also, in Settings > General > Profile, the device should not have any provisioning profiles. Delete any profiles that may be listed. (The example below has lots of profiles that should be deleted.)

Step 2: Prepare the app

You should use Xcode to distribute and Save for Enterprise deployment. Select the provisioning profile that matches your app ID. You can not use a team provisioning profile here. Export as an IPA file.

Step 3: Launch Apple Configurator

Use only the “Prepare” pane for the following steps.

Step 4: Set up Apple Configurator as follows

To avoid erasing your device, be sure Supervision is off, and Update iOS is “Never”.

Step 5: Drag the IPA into the “Apps” tab

Check the checkbox when done.

Step 6: Connect the iOS device and click “Prepare”

If there are provisioning errors or bundle ID errors, Configurator will present an error at this step.

Step 7: When done, disconnect the iOS device and tap the app to launch.

The app may present a certificate to confirm that you want to run the app. That is OK. The app should launch successfully and not immediate quit to the home screen.

Recent Activity