Custom APN settings incompatible with iOS 9

  • strict warning: Only variables should be passed by reference in /var/sites/e/ on line 61.
  • strict warning: Only variables should be passed by reference in /var/sites/e/ on line 61.
  • strict warning: Only variables should be passed by reference in /var/sites/e/ on line 61.
  • strict warning: Only variables should be passed by reference in /var/sites/e/ on line 61.
  • strict warning: Declaration of views_handler_field_user_name::init() should be compatible with views_handler_field_user::init(&$view, $data) in /var/sites/e/ on line 61.
Jay991's picture


Joined: Jan 15, 2016
Your rating: None (4 votes)

Hi All,

"You can define a custom Access Point Name (APN) for cellular data access using either of two different configuration profile payloads – APN or Cellular. In iOS 9 you currently must use a Cellular payload for your APN profile. Apple plans to address this issue in a software update."

If you are affected by iOS 9 APN issue please refer to Apple's KB.

dcsii-appinhouse's picture


Joined: Sep 23, 2015

iOS 9 APN issue

Your rating: None (1 vote)

Hi, we have the same problem.
We have 1000 devices in all over the country used by employee that work on the road. Some of them installed iOS 9 and lost custom APN configuration previously installed by an APN Payload.
This issue causes the impossibility, for our employees, to use network as well enterprise applications.
Besides we can't control any iOS 9 devices by our MDM because our devices can't connect anymore.

Please help us to solve this issue

Anas S.p.A
Via Monzambano 10
Rome - Italy

Jay991's picture


Joined: Jul 12, 2015

@dcsii-appinhouse Issue has

Your rating: None


Issue has been fixed in iOS 9.0.1 release.

Please see release note:

Uroshnor's picture


Joined: Nov 5, 2012

I'll add, there are 2 kinds

Your rating: None (1 vote)

I'll add, there are 2 kinds of profile payload that can set a custom APN :


Apple introduced the latter in iOS 7, and deprecated the former. This is all in the Configuration Profile Reference.

Apple dropping something it deprecated 2 years in, is pretty much their tempo.

The problem is that Apple Configurator and OS X Server Profile Manager, were never updated to deliver the new profile type (vs say Air-watch 8.x or other recent version of commercial MDM/EMM systems), and a large percentage of users who use APNs have the deprecated profile type present on their devices. (apparently if you say "Apple is not an Enterprise Company" 3 times in a mirror, it will summon the spirit of Steve Jobs)

Apple published a support article as to how to hand craft the new profile type :

9.0.1 really just kicks the can down the road and re-introduces support for the old payload type. Presumably there will be an update to Apple Configurator and OS X Server to move them to the new type, and presumably Apple will remove support for the old payload type AGAIN, at some point in the future.

Even if you deployed via AC, you can fix this via MDM, using the technique in the support article. If you have MDM push a profile containing the old style APN payload, named exactly the same as your existing one, AND it is set to expire (ideally in 0.001 hours, i.e. 4 seconds), then you will effectively remove the old profile from the device.

MDM can then push the new profile safely (the old and new payloads can not co-exist).

So given that at some unknown point in the future, Apple is likely to pull support for again, you probably need to work on a migration strategy off it.


Who is online?

There are currently 0 admins, 0 users and 251 guests online. Connected users: .

Recent Activity