List all the Provisional Profiles on the device at Runtime and get their EXPIRY dates
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
My Enterprise app is being distributed with a Provisioning profile (oldPP) that expires in 3 months. I have created a new provisioning profile (newPP), placed it on a device which has my app already installed. Now there are 2 profiles, I can see them when I hook up the device with the App Configurator 2 tool.
Using this link i was able to get the expiry date of the embedded provisional profile (oldPP)
I also tried
let urls = Bundle.main.urls(forResourcesWithExtension: "mobileprovision", subdirectory: nil)
But this only returns url of (oldPP) which is in my main app bundle.
Where is (newPP) located? I just cannot figure it out.
My goal eventually is to notify the user after opening the app with a message if the latest profile is expiring. For this I need to read the expiry dates on both (oldPP) and (newPP).
ios swift provisioning-profile provisioning ios-provisioning
asked Nov 23 '18 at 15:14
user2416933user2416933
32
add a comment |
My Enterprise app is being distributed with a Provisioning profile (oldPP) that expires in 3 months. I have created a new provisioning profile (newPP), placed it on a device which has my app already installed. Now there are 2 profiles, I can see them when I hook up the device with the App Configurator 2 tool.
Using this link i was able to get the expiry date of the embedded provisional profile (oldPP)
I also tried
let urls = Bundle.main.urls(forResourcesWithExtension: "mobileprovision", subdirectory: nil)
But this only returns url of (oldPP) which is in my main app bundle.
Where is (newPP) located? I just cannot figure it out.
My goal eventually is to notify the user after opening the app with a message if the latest profile is expiring. For this I need to read the expiry dates on both (oldPP) and (newPP).
ios swift provisioning-profile provisioning ios-provisioning
asked Nov 23 '18 at 15:14
user2416933user2416933
32
add a comment |
My Enterprise app is being distributed with a Provisioning profile (oldPP) that expires in 3 months. I have created a new provisioning profile (newPP), placed it on a device which has my app already installed. Now there are 2 profiles, I can see them when I hook up the device with the App Configurator 2 tool.
Using this link i was able to get the expiry date of the embedded provisional profile (oldPP)
I also tried
let urls = Bundle.main.urls(forResourcesWithExtension: "mobileprovision", subdirectory: nil)
But this only returns url of (oldPP) which is in my main app bundle.
Where is (newPP) located? I just cannot figure it out.
My goal eventually is to notify the user after opening the app with a message if the latest profile is expiring. For this I need to read the expiry dates on both (oldPP) and (newPP).
ios swift provisioning-profile provisioning ios-provisioning
asked Nov 23 '18 at 15:14
user2416933user2416933
32
My Enterprise app is being distributed with a Provisioning profile (oldPP) that expires in 3 months. I have created a new provisioning profile (newPP), placed it on a device which has my app already installed. Now there are 2 profiles, I can see them when I hook up the device with the App Configurator 2 tool.
Using this link i was able to get the expiry date of the embedded provisional profile (oldPP)
I also tried
let urls = Bundle.main.urls(forResourcesWithExtension: "mobileprovision", subdirectory: nil)
But this only returns url of (oldPP) which is in my main app bundle.
Where is (newPP) located? I just cannot figure it out.
My goal eventually is to notify the user after opening the app with a message if the latest profile is expiring. For this I need to read the expiry dates on both (oldPP) and (newPP).
ios swift provisioning-profile provisioning ios-provisioning
ios swift provisioning-profile provisioning ios-provisioning
asked Nov 23 '18 at 15:14
user2416933user2416933
32
asked Nov 23 '18 at 15:14
user2416933user2416933
32
asked Nov 23 '18 at 15:14
user2416933user2416933
32
asked Nov 23 '18 at 15:14
user2416933user2416933
32
asked Nov 23 '18 at 15:14
user2416933user2416933
32
32
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You won't be able to access the other provisioning profiles installed on the device because of iOS sandboxing. You will only get the oldPP because that is the only .mobileprovision file in the applications bundle. I do not believe Apple will ever let apps query for PPs on the device, as this could be used to get information about other apps installed on the device.
I would recommend simply repackaging your enterprise app each time the PP is expiring, so that the embedded.mobileprovision file is always the latest. Then you can use the notification feature (I have a way to get the pp expiration as well as the certificate expiration here) to inform the user that they need to install a new version of the app. Even if there are no code changes, the ipa will at least have the bew embedded.mobileprovision file in it.
And if you use MDM, rather than pushing the new provisioning profile to the device, you can now push the new ipa, with new embedded.mobileprovision file to the devices. If you are asking them to update their provisioning profile, it's probably just as simple to provide them a link to the .ipa file.
Unfortunately, it's unlikely that Apple will allow developers toquery other PPs installed on the iOS device.
answered Nov 24 '18 at 17:59
wottlewottle
8,80421449
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53449121%2flist-all-the-provisional-profiles-on-the-device-at-runtime-and-get-their-expiry%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You won't be able to access the other provisioning profiles installed on the device because of iOS sandboxing. You will only get the oldPP because that is the only .mobileprovision file in the applications bundle. I do not believe Apple will ever let apps query for PPs on the device, as this could be used to get information about other apps installed on the device.
I would recommend simply repackaging your enterprise app each time the PP is expiring, so that the embedded.mobileprovision file is always the latest. Then you can use the notification feature (I have a way to get the pp expiration as well as the certificate expiration here) to inform the user that they need to install a new version of the app. Even if there are no code changes, the ipa will at least have the bew embedded.mobileprovision file in it.
And if you use MDM, rather than pushing the new provisioning profile to the device, you can now push the new ipa, with new embedded.mobileprovision file to the devices. If you are asking them to update their provisioning profile, it's probably just as simple to provide them a link to the .ipa file.
Unfortunately, it's unlikely that Apple will allow developers toquery other PPs installed on the iOS device.
answered Nov 24 '18 at 17:59
wottlewottle
8,80421449
add a comment |
You won't be able to access the other provisioning profiles installed on the device because of iOS sandboxing. You will only get the oldPP because that is the only .mobileprovision file in the applications bundle. I do not believe Apple will ever let apps query for PPs on the device, as this could be used to get information about other apps installed on the device.
I would recommend simply repackaging your enterprise app each time the PP is expiring, so that the embedded.mobileprovision file is always the latest. Then you can use the notification feature (I have a way to get the pp expiration as well as the certificate expiration here) to inform the user that they need to install a new version of the app. Even if there are no code changes, the ipa will at least have the bew embedded.mobileprovision file in it.
And if you use MDM, rather than pushing the new provisioning profile to the device, you can now push the new ipa, with new embedded.mobileprovision file to the devices. If you are asking them to update their provisioning profile, it's probably just as simple to provide them a link to the .ipa file.
Unfortunately, it's unlikely that Apple will allow developers toquery other PPs installed on the iOS device.
answered Nov 24 '18 at 17:59
wottlewottle
8,80421449
add a comment |
You won't be able to access the other provisioning profiles installed on the device because of iOS sandboxing. You will only get the oldPP because that is the only .mobileprovision file in the applications bundle. I do not believe Apple will ever let apps query for PPs on the device, as this could be used to get information about other apps installed on the device.
I would recommend simply repackaging your enterprise app each time the PP is expiring, so that the embedded.mobileprovision file is always the latest. Then you can use the notification feature (I have a way to get the pp expiration as well as the certificate expiration here) to inform the user that they need to install a new version of the app. Even if there are no code changes, the ipa will at least have the bew embedded.mobileprovision file in it.
And if you use MDM, rather than pushing the new provisioning profile to the device, you can now push the new ipa, with new embedded.mobileprovision file to the devices. If you are asking them to update their provisioning profile, it's probably just as simple to provide them a link to the .ipa file.
Unfortunately, it's unlikely that Apple will allow developers toquery other PPs installed on the iOS device.
answered Nov 24 '18 at 17:59
wottlewottle
8,80421449
You won't be able to access the other provisioning profiles installed on the device because of iOS sandboxing. You will only get the oldPP because that is the only .mobileprovision file in the applications bundle. I do not believe Apple will ever let apps query for PPs on the device, as this could be used to get information about other apps installed on the device.
I would recommend simply repackaging your enterprise app each time the PP is expiring, so that the embedded.mobileprovision file is always the latest. Then you can use the notification feature (I have a way to get the pp expiration as well as the certificate expiration here) to inform the user that they need to install a new version of the app. Even if there are no code changes, the ipa will at least have the bew embedded.mobileprovision file in it.
And if you use MDM, rather than pushing the new provisioning profile to the device, you can now push the new ipa, with new embedded.mobileprovision file to the devices. If you are asking them to update their provisioning profile, it's probably just as simple to provide them a link to the .ipa file.
Unfortunately, it's unlikely that Apple will allow developers toquery other PPs installed on the iOS device.
answered Nov 24 '18 at 17:59
wottlewottle
8,80421449
answered Nov 24 '18 at 17:59
wottlewottle
8,80421449
answered Nov 24 '18 at 17:59
wottlewottle
8,80421449
answered Nov 24 '18 at 17:59
wottlewottle
8,80421449
8,80421449
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53449121%2flist-all-the-provisional-profiles-on-the-device-at-runtime-and-get-their-expiry%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
