From your screenshots, please list/identify the following:
Now I have the same problem on iOS after I upgraded to 4.13.1, I opened another place here iOS Failed to find a valid matching mobile provision
The resolution to this post and the new one you have created lies in the answer to the 4 questions above:
You must have separate Certificates and matching Provisions for all 4 listed cases. You cannot use the same iOS Certificates and Provisions for both the tvOS Project and iOS (phone) project and thus, the Bundle identifiers must be different between the iOS and tvOS Certificates and Provisions.
Please verify that you have all of the above by listing them in the order I have requested the information. If you do not provide this information we can only assume you have mismatching Certificates, Provisions, and Bundle Identifiers as indicated by your logs.
I am attaching the screenshot of the iOS settings screen. With the 4.13.0 version could be in distribution and development to complete the operation on iOS, except TVOS. While after upgrading to version 4.13.1, the operation fails even on iOS. The other post that I opened was for another project, but it has the same problem.
Based on your screen cap, you have the cert/prov pairing manually selected.
However, you have selected the Distro provision and the Development certificate.:
This why the log states: UATHelper: Packaging (iOS): env: Provisioning profile “RFTDevelopmentAdhoc” doesn’t include signing certificate “iPhone Developer: Vasco Wollschlaeger (YXA4Y4RPEM)”.
It just appears you had bad naming convention when creating the provision.
If you don’t manually pair these, it will select the correct pairing.
During the 4.13.0 release, there was a pairing bug (UE-35316) which was fixed for the hotfix (4.13.1).
Try not manually pairing these (uncheck all boxes) and if it fails to package, try creating a new Certificate and Provision pair with less confusing name conventions.
“RFT Development Adhoc…Distro_RFT Development Adhoc.mobileprovision”
NOTE: you can only use Adhoc. mobile provisions with distribution ceritficates, not development
Now as you can see from the screen they are highlighted in green, but still does not begin compiling. In 4.13.0 Now as you can see from the screen they are highlighted in green, but still does not start to build. In 4.13.0 I had no problems, only with TVOS, now I can not with either of them, as soon as I click on File - Packege Project - iOS, the error is displayed immediately, while on Project Launcher could complete the task but Application Loader Apple does not accept the .ipa file.
I am attaching the file of settings so you tell me if I have done correctly, the positive thing that has now highlighted green clearing the casellle. Then I wanted to ask the AdHoc distribution is not only limited to a few devices? How does it then to publish it in the app store so that it is available to everyone?
We have the same problem. It is not possible to build an iOS / iPhone Distribution, the Unreal Engine is always selecting the development “profile and certificates” instead of distribution.
1, Development:
2, iOS Provision (Development):
3, Distribution:
4, iOS Provision (Distribution):
5, Manuell selection and Output Log (combined):
110873-
As you can see/read, the Engine is selecting the development profile and certificate instead of the distribution version.
They said they had corrected with the 4.13.1, 4.13.0 but instead I could fill with no problems, except for TVOS.
We were able to do a distribution build after deleting the developer cert, key and provisioning on our Mac machine. If we add the developert cert and key again we are able to build a dev version again but no distribution version.
It’s not a good solution but a workaround.
Now I was able to do this, using Project Launcher, if I do it from File - Package Project - iOS, appears the license error. I tried to download the .ipa with Application Loader and Apple sent me this email
Dear developer,
We have discovered one or more issues with your recent delivery for “Opposite Ball”. To process your delivery, the following issues must be corrected:
This app attempts to access privacy-sensitive data without a usage description. The app’s Info.plist must contain an NSCalendarsUsageDescription key with a string value explaining to the user how the app uses this data.
Though you are not required to fix the following issues, we wanted to make you aware of them:
Missing Push Notification Entitlement - Your app includes an API for Apple’s Push Notification service, but the aps-environment entitlement is missing from the app’s signature. To resolve this, make sure your App ID is enabled for push notification in the Provisioning Portal. Then, sign your app with a distribution provisioning profile that includes the aps-environment entitlement. This will create the correct signature, and you can resubmit your app. See “Provisioning and Development” in the Local and Push Notification Programming Guide for more information. If your app does not use the Apple Push Notification service, no action is required. You may remove the API from future submissions to stop this warning. If you use a third-party framework, you may need to contact the developer for information on removing the API.
Once the required corrections have been made, you can then redeliver the corrected binary.
Regards,
The App Store team
Smoky Minds,
Could you provide the complete log for your editor session? That will help me figure out where the problem lies. We don;t do anything with the key specified by Apple, so I am not sure why that would come up, but seeing the whole log may help me determine what is going on.
-Pete
This is log from project launcher
This log this last one shows a successful build, - just a problem exiting UAT… Did it not create a package at all?
The .ipa file is created now, the only problem is TVOS that does not work, and what message that sends me apple after they complete the upload for testflight.
What do you mean by the tvOS does not work? Do you mean that you have tested this on a tvOS device and it is not working at all? Or do you mean that you simply cannot upload the tvOS to the App store and are getting the above message from Apple?
Looking at the above message from Apple, the part about having push notifications is easily corrected by enabling push notifications on in the iTunes connect settings. Also, even if you did not correct this, it is only a warning and would ultimately allow you to publish regardless of if you fixed this.
However, this part: “This app attempts to access privacy-sensitive data without a usage description. The app’s Info.plist must contain an NSCalendarsUsageDescription key with a string value explaining to the user how the app uses this data.”
-Your app is trying use the end-user’s personal data and you have to do just what it says. This is not a bug with UE4 but something you have to correct.
As I explained to you, I have two projects:
The first is for TVOS and iOS
The second is only for iOS
After doing upload with Application Loader, I receive the email from Apple, but as you can see on the picture I attached the Push Notification is configured you.
On TVOS I can not create the .ipa, I am attaching the TVOS log in another answer
This is instead the error log with TVOS, the error is present on all projects
Since the title of this thread is “4.13 tvOS problem with packaging” we are only dealing with the tvOS issue. Bringing in information about the iOS is only adding confusion. We need the ENTIRE output log and Project log in a text document for the tvOS issue only! Please don’t post screenshots unless requested.
The last log I have sent is TVOS
The last tvOS log sent was from project “OppositeBall.” The last screenshot you sent, which is of no value to us, is from project “BeeRoll_” If you do not want to send your entire tvOS output logs as text files then we cannot help you.
