,
I was able to repro the issue you were seeing with certificates and provisions. Here’s what I did based on what has already been discussed in this thread:
-
Deleted all provision profiles and certificates
-
Imported TVOS distribution certificate and both IOS and TVOS distribution provision profiles with the appropriate bundle id
-
Imported the IOS development certificate as well
With these steps, I was getting the same error as you were, regarding missing provision and certificate. In the accepted answer, you mentioned also importing wildcard provision profile. So:
- Imported the wildcard provision profile that mapped to the IOS development certificate from step 3
After this I was able to get past the errors and package the TVOS project. The build process for TVOS borrows/shares a lot with the IOS build process that’s why you need to also have IOS certificates and the provision profile that maps to it.
Separately, you seemed to have encountered the bundle id issue which should be fixed in the next update. The issue was that the project config INI files were not getting included into the config hierarchy so it would end up using the default value from Engine/Config base Engine INI files. So, after the next update is released, you should not need to go through the resigning since the plist will have the correct bundle id.
In short, your workaround is just how the build process works for TVOS and the bundle id issue will be fixed in the next update.
Cheers!