Update: [Here is a screencast of the whole process.][1]
Update 2: Discovered a workaround. Scroll down to the “accepted answer” at the bottom of the page.
tvOS distribution packaging is not working at all for me. I managed to workaround the development packaging issues through the [patch + workaround in this answerhub post I started in October][2].
Now I need to package for distribution, and I am having no luck.
My app is named “Topple Town”. The certificate(s), app id(s), and provision(s) are all brand-new, made just for this app. I will list the various things that I have tried thus far.
HERE IS EXACTLY WHAT I HAVE TRIED
This is on a Mac Pro (Late 2013), 10.11.6, Xcode 8.1
All of the certificate/id/provision stuff is done using the web gui of Apple’s “Certificates, Identifiers & Profiles” section of developer.apple.com
Generate Production certificate of type App Store and Ad Hoc. You can’t choose it’s name…they auto name it ``, because that’s my name. Type is set to iOS Distribution. I am somewhat concerned that there is nothing tvOS-specific, but there are no options for App Store certificates other than this one that I selected.
Generate App ID on Apple’s site: Name: Topple Town, ID com.agileperception.toppletown
Create Distribution Provisioning Profile. Name: Topple Town tvOS Distribution Profile, Type: tvOS Distribution, App ID: Topple Town (com.agileperception.toppletown)
Delete ALL certificates from Keychain Access and delete ALL provisions on my Mac from ~/Library/MobileDevice/Provisioning Profiles
Download the certificate from step #1. In Project Settings > iOS I click Import Certificate and select the downloaded certificate file, which succeeds (see screenshot after step 6)
I download the provision from step #3. I click Import Provision and select the downloaded file, which succeeds (see screenshot below)
Try reinstalling your certificates and provisions through the Editor, not Xcode. There is a known issue for this which isn’t fixed in 4.14.0 ([UE-38006][1]).
I deleted all certificates from Keychain access. I deleted all provisions from ~/Library/MobileDevice/Provisioning Profiles/. I opened my project in 4.14.0. I imported the certificate and provision through the Editor. I attempted to package for tvOS on the desktop and received the same set of errors.
As a side note, please be aware that the commit linked to from UE-38006 is present in the 4.14.0-release tag in GitHub. (ie the listed patch is IN 4.14.0).
I have never seen that before! Unfortunately, that also does not change the errors at all. Same behavior. I tried deleting all certificates and provisions, then deleting the expired WDRIC (the new one is already there), then also deleting all other expired items in Keychain, then importing the distribution certificate and provision through the editor. All that, and the exact same “not found” errors. This was all on 4.14.0.
On the bright side, it did fix [this other issue][1] I was experiencing, so I will update that answerhub post. That’s something. Now I have two machines I can try things on.
I get the same error on a Windows. I haven’t tried it on a mac yet. I have a valid certificate and tvOS mobileprovision profile and they both show green in the Project settings and I’m using a new blank project.
If I have the iOS mobileprovision profile present also with the same bundle identifier it tries to use the iOS profile instead of the tvOS profile and of course I get an entitlement error because it used the wrong profile.
I’m so happy to hear that at least one of your issues has been resolved thus far. So I ran a test today and I ran into the ‘provisions not found’ error while packaging for tvOS.
I spoke with our tvOS Specialist to ensure there wasn’t an actual issue. He then tested and did not have a problem.
I was able to resolve it by doing the following:
Closed the Editor
Removing my provisions from the provisioning profile
Opened the Editor back up
Added only the Provisions that I needed for tvOS
Added only the certificate that would be used for tvOS
Packaged the project for tvOS
This corrected the issue for me. I know you have double checked multiple times that you’ve used the correct provisions and certificates, but you might need a complete refresh.
There was some provisioning logic changed when Xcode was updated therefore, any older certificates/provisions were causing errors during packaging.
I have deleted ALL the provisions and certificates every time. I have only been using certificates/provisions for tvOS during this process. I don’t know what you expect to change(?)
Nevertheless, I will run through the entire process again as you laid out with both 4.13.2 and 4.14.0 and attach the logs as you request. I just upgraded my workstation to macOS Sierra last night, so perhaps that will affect something as well (though my laptop is already on macOS Sierra and exhibits the same behavior).
By the way, there is only one certificate type for distribution. Were you testing with production/distribution settings? This is different than developer settings. Also, what value did you put for your App ID? Did it use a wildcard at all?
The certificate I created was the “Production: App Store and Ad Hoc” certificate, and it names itself ios_distribution.cer externally and iPhone Distribution: (...) internally, despite the fact that I’m using it for tvOS.
Thank you for pointing out that it’s distribution having the issue. I have submitted a [UE-39501][1] to our developers for this issue. Please check our public for updates.
Next, it appears that you marked my [issue regarding development provisions and certificates][1] as a duplicate of this one and that the comments were locked.
I never received a notification email that that issue was marked as a duplicate. In addition to the comments being locked, that makes it really difficult to notice and tell you that it’s not a duplicate! Is this an AnswerHub bug?
It’s not a duplicate. It’s a problem with development provisions, instead of distribution ones.
I notice that you seem to be able to run the development profiles fine, yourself, but I can’t get it to work following those same steps.
I am really trying to get to market on the AppleTV, so these issues are really important to me. So, I’m going to wipe my hard and install macOS Sierra from scratch and reinstall programs individually without restoring from backup. At the very least, perhaps I could deploy to the AppleTV in development mode to continue QA testing.
If you would go unlock the other AnswerHub post, we could continue our conversation there.
Thanks for pointing that out, it’s very easy to believe questions are duplicates when they’re so similar. I’m opening it back up. Please reply back to it when you’ve done the checks on your end to try and resolve the issue.
I’ll post the steps on that one too, in case anyone else runs across it.
This suggestion may seem obvious and something you may have tried already but I was getting a slightly different error than yours when I didn’t check the box for the provision and certificate in the project settings.
I am happy to (re)try anything that could possibly get it working again. Thanks for the suggestion.
Checking the boxes of my distribution certificate and a distribution provision with a specific app id doesn’t appear to have any effect.
I’m on UE 4.14.1 now, with a from-scratch installation of macOS Sierra, and I revoked/deleted all my production certificates/provisions and recreated them from scratch just a moment ago.
