[TIMOB-13625] CLI: Using iOS app store provisioning profile during Adhoc Distribution results in app that can be run on device
GitHub Issue | n/a |
Type | Bug |
Priority | Low |
Status | Closed |
Resolution | Cannot Reproduce |
Resolution Date | 2016-08-30T04:24:55.000+0000 |
Affected Version/s | Release 3.1.0 |
Fix Version/s | n/a |
Components | CLI, iOS |
Labels | qe-3.1.1, usability |
Reporter | Olga Romero |
Assignee | Chris Barber |
Created | 2013-04-18T23:55:49.000+0000 |
Updated | 2017-03-23T20:24:50.000+0000 |
Description
Description:
Code-signing an app with an appstore distribution provision should not allow the app to run on device. In our case it did. When removing installed provisions on the device, we were only unable to install the app (as expected) when no provisions were present. The last one removed was an adhoc provision. We attempted to use each of our active provisions, and only our adhoc provision allowed app installation, indicating that the app was somehow associated with this provision.
We opened the .ipa produced and looked at the embedded provision, which seemed accurate.
We also verified on the Apple Developer site that the provision we used was in fact NOT an Adhoc provision, but a App store provision.
This occurs with both studio and CLI builds
Test steps:
1. Create a project
2. Distribute via studio with: Adhoc/Enterprise option, using an iOS app store provisioning profile. (or use CLI target dist-appstore)
3. Open Xcode and try to add the App to a device
4. Run the app on device
Result:
The app will install and run if an adhoc provision is available on the device
Expected:
Failure to install the app since the provision is app-store only.
Attachments
[~emerriman] Is this really Titanium's fault? Shouldn't this be an issue with Xcode?
I could not reproduce this with Titanium SDK 5.5.0 and Xcode 7.3.1.
Closing ticket as "Cannot Reproduce" with reference to the above comments.