[TIMOB-24008] iOS: Can't use Xcode managed provisioning profiles to build app?

GitHub Issue	n/a
Type	Bug
Priority	High
Status	Closed
Resolution	Fixed
Resolution Date	2016-10-12T11:12:06.000+0000
Affected Version/s	Release 5.5.1
Fix Version/s	Release 6.0.0
Components	iOS, Tooling
Labels	cb-tooling
Reporter	Chris Barber
Assignee	Chris Barber
Created	2016-10-10T16:28:10.000+0000
Updated	2019-08-30T16:09:04.000+0000

Description

Apparently the iOS build fails when tryign to build with an Xcode managed provisioning profile. We need to investigate this.

[ERROR] Error details: Provisioning profile "iOS Team Provisioning Profile: *" is Xcode managed, but signing settings require a manually managed profile.

Comments

Dan Wilson 2016-10-10

Chris, I have confirmed that creating a "manual" provisioning profile solved my problems. I am able to build to device. Once you find a solution for the xcode managed profile, please let me know and I will be happy to test. Thanks.
Chris Barber 2016-10-10

[~hansknoechel] Perhaps it's based on the name? Easy to test, manually create a provisioning profile with the name similar to that of a managed provisioning profile. Or, perhaps managed provisioning profiles are registered in the Xcode cache db?
Hans Knöchel 2016-10-10

They are stored in the same location (~/Library/MobileDevice/Provisioning Profiles). The names are: <string>iOS Team Provisioning Profile: *</string> vs <string>WILDCARD</string> so maybe the star causes problems? Probably too easy to be responsible for the issues.
Chris Barber 2016-10-10

I checked the local Xcode database and there's nothing in there that flags a specific provisioning profile as managed. After some more research, Xcode generates both an App ID and a provisioning profile, however only the App ID shows up in the Apple developer website. I created a bunch of provisioning profiles using the generated App ID and here's what I found: ||Name||Result|| |CBTest|Built app just fine| |iOS Team Provisioning Profile: *|Failed to create because name was already used even though it wasn't in list| |iOS Team Provisioning Profile: CBTest|Failed to build app| |iOS Team Provisioning Profile CBTest|Failed to build app| |kiOS Team Provisioning Profile: CBTest|Failed to build app| |iOS Team Provisioning CB|Built app just fine| |ios team provisioning profile: cbtest|Built app just fine| So, it is just a naming thing. If the provisioning profile literally contains "iOS Team Provisioning Profile", then we can't use it. Note that it IS case sensitive. I will update ioslib to return a managed property, then the Titanium iOS build and info will act accordingly.
Chris Barber 2016-10-11

Ti SDK master PR: https://github.com/appcelerator/titanium_mobile/pull/8497 I don't know if we want to take this in 6.0.0, but here's the PR: https://github.com/appcelerator/titanium_mobile/pull/8498. To test: 1. Make sure you have at least one managed provisioning profile installed where the provisioning profile must contain "iOS Team Provisioning Profile". 2. Run ti info -t ios and verify that it prints that it is unsupported. 3. Run ti build -p ios -T device -P foo and make sure that managed pp-uuids are not listed in prompt. 4. Run ti build -p ios -T device -P <managed-pp-uuid> and make sure the build errors with [ERROR] Specified provisioning profile UUID "<managed-pp-uuid>" is managed and not supported.

Hans Knöchel 2016-10-12

PR's approved and merged! When using ti info -t ios, the following output is given:

     iOS Team Provisioning Profile: *
       UUID                      = 9f0c6453-5bd0-4068-9a6e-de6dc112a2cb
       App Prefix                = 6K4KHD4NQF
       App Id                    = *
       Date Created              = 9/16/2016 4:19 PM
       Date Expired              = 9/16/2017 4:19 PM
       Managed                   = Yes and is NOT compatible with Titanium

When running on the device using appc run -p ios -T device, the managed profile is not listed:

   Which developer certificate would you like to use?
   /Users/hknoechel/Library/Keychains/login.keychain-db
      1)  Hans Knoechel (xxxxxxxxxx)  (expires Sep 15, 2017 10:52:02 am)
   Select a certificate by number or name: 1
    
   Which provisioning profile would you like to use?
   Available Development UUIDs:
      1)  cc937768-xxxx-4461-xxxx-ca545bf96505 WILDCARD: *  (expires Sep 16, 2017  4:06:50 pm)
   Select a provisioning profile UUID by number or name:

Looks great!

Jonathan Nakouzi 2016-11-08

Hi All, what is the fix for this issue? Must I wait for the next update? or is there a published fix now.? I may have missed it above, My first time in this forum or in appcelerator internals. I just want to compile to device cleanly, as it used to. Thanks Running on Appcelerator Studio, build: 4.7.1.201609100950 Build: jenkins-appcelerator-rcp-master-358 (origin/master) xcode Version 8.1 (8B62) Date: 10 September 2016, 09:51:58
Chris Barber 2016-11-08

[~jn] This issue has been resolved and the result is Titanium does not support managed provisioning profiles. It simply displays an error and fails out. This is because the Xcode project we generate doesn't support managed provisioning profiles. We may fix this in the future and remove this limitation. This "fix" will be released with Titanium SDK 6.0.0.
Eric Merriman 2018-08-06

Cleaning up older fixed issues. If this issue should not have been closed as fixed, please reopen.

JSON Source