Date
1 - 9 of 9
Developer
|
Gerriet M. Denkmann
A friend of mine has a problem:
When he installs an app (via Xcode) on his iPhone it works fine (probably the app will expire after one year). But when he installs the same app on his iPad, the app will expire after just one week. What could be the reason for this behaviour? Gerriet. |
|
|
|
Carl Hoefs
Did you find out anything more about this problem? We're experiencing it too. iPhone app builds expire after 1 year, but last only a week or two on the iPad. My boss just got bitten by this at a demo.
toggle quoted message
Show quoted text
-Carl On Oct 6, 2019, at 2:20 AM, Gerriet M. Denkmann <gerriet@...> wrote: |
|
|
|
Alex Zavatone
Seems like it’s a custom signed IPA.
toggle quoted message
Show quoted text
On Oct 17, 2019, at 6:26 PM, Carl Hoefs <newslists@...> wrote: |
|
|
|
Alex Zavatone
There are some signing options where if you are part of a TestFlight team, your install will last for a certain time. There are other install options where if you have an Enterprise cert installed (or something like that), the installation lasts longer. I’d check which certs and mobileconfigs are installed on each device. Also if one device is signed in to purchase the app from the App Store or to use TestFlight.
toggle quoted message
Show quoted text
AZ On Oct 17, 2019, at 6:26 PM, Carl Hoefs <newslists@...> wrote: |
|
|
|
Carl Hoefs
In our case, these apps are just for internal development purposes, such as student projects and the like. It's nice to be able to showcase them each semester, but the iPad apps always expire, and they have to be reinstalled onto the iPad from Xcode over and over again. All are using the same developer profile and certificate for all devices. Odd it would have an issue with just the iPad Pros? If I wipe/zero/reset the iPads clean and start over anew, might it clear this?
toggle quoted message
Show quoted text
-Carl
|
|
|
|
Gerriet M. Denkmann
On 18 Oct 2019, at 06:26, Carl Hoefs <newslists@...> wrote:Find …/Your iOS.app/embedded.mobileprovision, open in some editor and delete the first 62 bytes, so that it starts with: “<?xml version="1.0" encoding="UTF-8”?>” Save as: /anyPath/anyName.plist and open this in Xcode. Look at ProvisionedDevices and TimeToLive. It seems that every Developer Team has a List of (up to 100) ProvisionedDevices, which will build with TimeToLive = 365. Building for a device which is *not* in ProvisionedDevices will get TimeToLive = 7. So the problem reduces to: How to add a device to the list of ProvisionedDevices. And I do not know the answer. My Xcode seems to add any new device to this list by some kind of magic. The Xcode of your boss (and of my poor friend) seems not to do this. Gerriet. |
|
|
|
Bernie Maier
On Sat, 19 Oct 2019, at 5:42 PM, Gerriet M. Denkmann wrote:
Alternatively, run this on the command line to strip the security message container and signing from the contained plist: ``` security cms -D -i path-to.mobileprovision ``` I did some research into this a while ago (by I which I mean I did some searching and found other people’s research into this). I collected this and other related info into a public BitBucket snippet: https://bitbucket.org/snippets/blurkk/5LB5LM Cheers, Bernie |
|
|
|
Alexander von Below
Maybe this helps: Code to decode mobileprovisions https://github.com/below/cgjprofile
toggle quoted message
Show quoted text
Von meinem iPhone gesendet Am 19.10.2019 um 08:43 schrieb Gerriet M. Denkmann <gerriet@...>:
|
|
|
|
Alex Zavatone
Then check the certificates and profiles in the signed package(s).
toggle quoted message
Show quoted text
I use a cery and profile inspector that someone wrote for Spotlight and is on Github.
|
|
|