I have an issue with iTunes Connect. When I transferred my application with watch support to another apple account after I've received an error from iTunes Connect when I tried to upload an ipa file (that was signed by new account after transferring) to.
I was transferring the applications very often and have no any problems before. Problems are for watch kit application and watch kit extension only, a main application is ok.
Have same problems for another 3 my applications with watch support which were transferred to new account. A transferring the applications without watch support is working as expected without any issue.
ps.
All mobileprovision files for transferred applications were either transferred too or recreated into a new account (old account doesn’t have any transferred bundle ids and mobile provision files with after).
Any ideas?
Thank you.
Sorry, english is not my native language.
Description of an error from Apple
Dear developer,
We have discovered one or more issues with your recent delivery for "My application name". To process your delivery, the following issues must be corrected:
CFBundleIdentifier Collision - The Info.plist CFBundleIdentifier value 'com.my.company.watchkitextension' of 'My application name.app/PlugIns/My application name WatchKit Extension.appex' is already in use by another application.
CFBundleIdentifier Collision - The Info.plist CFBundleIdentifier value 'com.my.company.watchkitapp' of 'My application name.app/PlugIns/My application name WatchKit Extension.appex/My application name WatchKit App.app' is already in use by another application.
Once these issues have been corrected, you can then redeliver the corrected binary.
Updated
The problem has been solved. I've just transferred the applications to the third my company's Apple account without any problems
Related
I'm working on a Xamarin application and I'm doing iOS builds to run and test on different devices using App Center.
Everything was ok, on Apple Developer I created the Ad-Hoc certificate, the provisioning file, and the identifier and it was all good.
During the last implementation, I added on Entitlements the Associated Domain due to enabling the possibility to use the App Link and let the user open the application using a link provided via email.
I updated the Identifier adding the feature also to it and I downloaded it and uploaded it again to the dedicated branch on App Center, but now when I try to download the app to the device I receive this message:
Unable To Install "App Name". This app cannot be installed because its integrity could not be verified.
I tried different ways trying to solve it:
Create a completely new certificate with a new identifier, provisioning, and .p12 file
Checked Entitlement feature list correspond to the identifier list on Apple Developer
Used different versions of SDK and Xcode on App Center
I already searched around on the web but they talk about the provisioning file list but I already checked and it is updated.
Thank you for your help and for your suggestions.
I want to add my first iOS application developed with Visual Studio 2017 Xamarin iOS. I created the new version for my app in the iTunes Connect, filled up all the information required. Then I went to the application loader to upload it and the process done successfully, but in the iTunes Connect no build appear. I reviewed my email and it said:
"Dear developer, We have discovered one or more issues with your
recent delivery for "E2EWorks Mobile". To process your delivery, the
following issues must be corrected: Missing Info.plist value - A
value for the Info.plist key 'CFBundleIconName' is missing in the
bundle 'com.e2eworks.e2eworksmobile'. Apps built with iOS 11 or later
SDK must supply app icons in an asset catalog and must also provide a
value for this Info.plist key. For more information see
http://help.apple.com/xcode/mac/current/#/dev10510b1f7. Once these
issues have been corrected, you can then redeliver the corrected
binary. Regards, The App Store team"
I fixed all necessary things and rebuild application again but now application loader doesn't let me to upload again. I checked iTunes activity but no application is shown however submmit to review button is enabled. Under builds section it keeps saying: "Submit your builds using Xcode 6.0 or later, or Application Loader 3.0 or later."
Please your help.
Every upload of IPA's bundle to iTunes Connect requieres a unique and distinct CFBundleVersion string on info.plist, so any issue caused just after uploaded or rejected event that must be corrected, a new CFBundleVersion must be set. In my case it started with 1.0 and after correction, string changed to 1.0.1 (minor bugs fixed) and proceeded to build and uploaded again succesfully. I'm newbie in iOS stuffs.
I hope this help to anyone in similar situation!
I am trying to publish an iOS app to iTunes Connect using Appcelerator (note: this app was created by another developer).
The app uploaded fine, but iTunes then sends the email with the following error message:
Dear developer,
We have discovered one or more issues with your recent delivery for
"XXXX". To process your delivery, the following issues must
be corrected:
Invalid Swift Support - The SwiftSupport folder is empty. Rebuild your
app using the current public (GM) version of Xcode and resubmit it.
Once these issues have been corrected, you can then redeliver the
corrected binary.
Regards,
The App Store team
I'm quite new to Appcelerator, but I can't seem to find any relevant answers to this problem (although there a few answers relating to X-Code).
You should choose "Save for iOS App Store Deployment" option at the time of exporting ipa file.
Turns out I just needed to update XCode!
I am trying to build an iOS app using RadStudio XE6 and have nothing but problems trying to get the app on to iTunes connect. These are the steps I have carried out so far:-
Have created an app id in developer portal making note of the ID used.
Have created and downloaded a provisioning profile for the app with my iPhone registered as one of the devices.
I have created the App in iTunes connect
I have gone into the Project Options in RadStudio and change the provisioning so the certificate is the certificate I have created and the Mobile Provision profile is the one I have downloaded from the developer portal for this app I created in stage 1.
I hit project deploy and the app compiles, links and builds an IPA file on my Mac.
I then try and use application loader to send the IPA file through to iTunes connect. I get the following errors:
ERROR ITMS-9000: Your bundle identifier cannot be changed from the current value xxxxxx. If you want to change your bundle identifier you will have to create a new application in iTunes connect
ERROR ITMS-9000: This bundle is invalid. The application identifier element is missing. It should contain your 10-character Apple developer id, followed by a dot followed by your identifier.
ERROR ITMS-9000: Inavlid launch image - Your app contains a launch image with a size modifier that is only supported for apps built with the iOS 6.0 SDK or later.
Anybody have a clue what is causing these problems and more importantly how I fix them?
UPDATE - 15th September
After following the instructions in the answer below and also the link contained within in I got a message from application loader that the file did not include a payload directory. So I changed the name of the file to a zip file and unzipped it to find the Payload folder. And sure enough application loader error is now no .app bundles found in the package.
UPDATE - 17th September
I created a new Provisioning profile and tried to build and deploy the app with that, changing the budnle id in the version info accordingly. Still the same message of No payload folder. So I then quickly created a new app in rad studio and attached the provisioning profile and bundle id in the version info and build and deployed that... After adding the images that worked.. So there is something in my existing project that is screwed. I just have to find out what...
In Project|Options|Version Info set:
CFBundleIdentifier to your app unique ID (like com.yourdomain.yourappname). It must match what you set up in the Apple provisioning information.
CFBundleDisplayName to the name you want to appear below your icon on the IOS device.
CFBundleInfoDictionaryVersion to 7.1 (you should compile against the IOS 7.1 SDK).
CFBundleVersion to match the version number you have set in the Apple store information.
You can read more about deployment here. You can read more about provisioning here. You can read more about what NOT to do here.
Finally, this developer seems to have had the same errors as you and tells how he fixed it.
I have an app I tried to submit to the app store. Like many others I'm getting the following e-mail from the app store approval process. The answer to the other questions seems to be, uncheck iCloud from the App ID, but my app uses iCloud and I wouldn't want to lose that functionality. Has this been solved yet?
I did double check that my App ID's Bundle Identifier matches the value of the items that are entered in the Entitlements area of the Target Project. Thanks for your help!
Dear Developer,
We have discovered one or more issues with your recent binary
submission for "XXXXXX". Before your app can be reviewed, the
following issues must be corrected:
Invalid Code Signing Entitlements - The signature for your app bundle
contains entitlement values that are not supported. For the
com.apple.developer.ubiquity-container-identifiers entitlement, the
first value in the array must consist of the prefix provided by Apple
in the provisioning profile followed by a bundle identifier suffix.
The bundle identifier must match the bundle identifier for one of your
apps or another app that you are permitted to use as the iCloud
container identifier.
Specifically, value "XXXXXXX.com.xxxx.xxxxxx" for key
"com.apple.developer.ubiquity-container-identifiers" in WeHeartApps is
not supported.
Once these issues have been corrected, go to the Version Details page
and click Ready to Upload Binary. Continue through the submission
process until the app status is Waiting for Upload and then use
Application Loader to upload the corrected binary.
Regards,
The iTunes Store Team
Found the answer, it seems as though my Provisioning and Distribution Profiles were out of sync. When in doubt;
delete your provisioning and distribution profiles on the iOS provisioning portal
recreate them on the iOS provisioning portal
Delete the old ones locally.
Download the new ones from the portal.
Clean the project
Drag the new profiles onto the xcode app
Do a fresh "Build for Archiving." ( Make sure iOS device is selected for this to be enabled )
Finally archive
Go to the organizer and Validate the Archive
Submit to the app store!
Cheers
For others who have apps sharing data between both Mac and iOS devices via iCloud, you will also run into this problem if you try to submit the platform which depends on the other's bundle identifier first. This is because the bundle identifier you're trying to share data with has not yet been registered as an app.
The solution is simply to submit the app whose bundle identifier you're using as the com.apple.developer.ubiquity-container-identifiers entitlement first.
For example, if you're sharing data between a Mac app with a bundle identifier of com.mycompany.osx, and an iOS app with a bundle identifier of com.mycompany.ios, you will likely choose one as the mutual data store. If you choose the iOS version, the your Mac app will have the value "com.mycompany.ios" set as your ubiquity storage and iCloud key-value storage. In this case you just need to submit the iOS app first so that the "com.mycompany.ios" bundle identifier registers as a valid app on Apple's side.