I have to distribute an app via AdHoc distribution. With Xcode 5 after the archiving, I select the option "Save for enterprise distribution" and then insert the web url where I upload the .ipa and the .plist.
Now in Xcode 6 this option is disappeared and I can't able to generate .ipa and .plist, but only the .ipa.
There is someone that know how to create .ipa and .plist in Xcode 6 for upload this files on a web site to allow an easy way for tester to install the app on iOS7 where testglight doesn't run?
Solution 1):
Download Xcode 5.1.1. and install it separately from Xcode 6.1. (in a different folder).
This way you can generate .plist files easily since you mentioned that you need it for iOS 7.
You can always keep Xcode 5.1.1. around and open your current project from it.
Solution 2):
Use your old .plist files or create a new one :
Xcode 6 Save for Enterprise Deployment does not create plist for ipa anymore?
Solution 3):
Wait for apple to fix this "bug" in the upcoming Xcode versions :).
If you have a plist from previous exports, you can use the same one. I distribute an app using enterprise deployments and all I do is create the ipa and upload it to the server. I created my plist file quite some time ago. You can also update the data in there if you need to, but so far I have not run into any issues with pushing a new version with out updating that file.
When you press export you get 3 options one of them is save for enterprise deployment.
But you can use testflight instead and save the app for adhoc deployment.
Related
I am trying to upload my app to the App Store connect but I'm not able to.
I was testing my app using Xcode 12 and without realising it was beta software, I archived my app and uploaded it. Now when I click on submit for review it says Binary Invalid. Then, I realized that I wasn't supposed to upload it using Xcode beta. Now, when I try uploading it with Xcode 11.5, It isn't letting me sign the app as I get an error saying Profile doesn’t include the com.apple.application-identifier entitlement .
I have tried the following Methods and none seem to work.
Close Xcode and Delete all provisional Files from ~/Library/ApplicationSupport/MobileProvisions/
2.Change the Bundle ID and also tried repeating (1.)
Create new certificates and profiles from the developer website(Both original and new bundle IDs)
Delete Xcode and reinstall it.
But in the end it only uploads it with Xcode 12 beta. (And throws an error saying Binary Invalid)
Please help me rectify this issue.
I struggled with this problem for two days, simple fix is to;
Build with 11.5
Archive / Upload with 12 beta
Here is the answer. Create your archive. In the organizer, select your archive. Choose distribute app. Then instead of upload, choose export. Export the archive to a folder on your hard drive. Now download transporter from the App Store. Transporter replaced "Application Loader" or whatever it used to be called in the developer tools menu of Xcode.
Now sign into Transporter with your dev account and upload the .ipa found in your exported archive folder using Transporter.
It will work under Big Sur!
I have application for iOS created on Go language, I compiled it to .app file. Can anyone tell me what should I do to:
Load application to my iPhone
Load application to iTunes connect (I loaded another via Xcode, but there are no objective c or swift code here to do so)
PS: I have valid developer account, able to create any certificates that will need. Versions: XCode 7.2, iOS 9.2
Thanks a lot for your help.
For submission part there is Apple tool called Application Loader. It is a part of Xcode, but I think can still be downloaded separately. It can deliver app to App Store without having to use Xcode Organiser interface.
You need to deliver your app as .ipa file. If your .app is properly signed and contains a valid .mobileprovision (which is a different question), all you need to do is to create a new folder named "Payload", put copy your .app into ito it. Then you can rename the .zip file to .ipa and upload it using Application loader.
My project was initially build with the early version of Xcode.
Even with Xcode 6 I was able to export the app (Ad Hoc, ipa file).
After that we started to use continuous integration & upload of builds to iTunes.
Also, I have deleted my working copy.
Recently, I have to make fixes in the project.I checked out the source code, updated my Xcode to the latest version - Xcode 7, updated the project.
But now when I am archiving the app, it goes under unknown app in Organizer, I can't create ipa ( Validate button is not active).
For some reasons the app, in the Organizer doesn't have a valid identifier
I tried to use a new
PRODUCT_BUNDLE_IDENTIFIER
and directly to set correct bundle ID, but I still have 2 items, instead of one app.
In build setting under build option Disable bitcode.
In build setting under deployment set false to skip install.
I can archive my project in XCode 6 and choose the Enterprise Deployment Option. In XCode 5 when you go to choose the location of the archive on the file system you get a check box that says "Save for Enterprise" and you get several other options to complete like url. This generates the plist file. I dont get that in Xcode 6, just the ipa. Is this because XCode 6 is Beta? Or do you no longer get a plist as well as the ipa?
I couldn't get a plist either so I used a trick.
To distribute my app Over The Air anyway, I used a plist formerly generated with XCode 5 and changed manually the link to my newly generated IPA.
Once you managed to do that, there is one last thing to know. When you'll open the link to the plist, you'll have the impression that nothing happens because iOS don't close you current window + slide to the downloaded app anymore. But it doesn't necessarily mean that nothing happen! Go to your home screen manually and check.
UPDATE
If that still doesn't work, try this workaround: change your bundle ID, generate your new App ID and provisioning profile accordingly, regenerate your IPA and redo the above. For some, it works only the first time for a given bundle ID!
When we try to upload a new version of our app to Apple's App Store we get the following error in Application Loader:
ERROR ITMS-9000: "This bundle is invalid. New apps and app updates submitted to the App Store
must be built with public (GM) versions of Xcode 5 and iOS 7 SDK. Do not submit apps built with
beta software." at SoftwareAssets/SoftwareAsset (MZItmspSoftwareAssetPackage)
We are already building with the latest available version of Xcode, 5.1.1 (downloaded from the Mac App Store) and v7.1 of the iOS SDK (which came with Xcode 5.1.1).
Our app is built with Marmalade 7.2.1. We've tried rebuilding all of the EDK extensions and static libraries that our app uses.
What could be going wrong? Is there anything more anyone else can tell us about the error to help us track it down?
Starting May 15, 2014, new apps and app updates submitted to the App Store must be built with Xcode 5.1.1
You have to update your xcode.
Just clean all the things.
Check the developer/distribution certificate and mobile provision profile properly created, if not then revoke them from developer account and create all new one.
Remove all profiles from /Users/yourSystemName/Library/MobileDevice/Provisioning Profiles
Now, Export all certificates and keys from your keychain and Save them as backup for using them again.
Now install your developer/Distribution certificate first and install provisioning profile. And upload your application. This is tested way and should resolve your issue. Thanks.
When Xcode creates an .ipa package, it adds a number of elements to your project's Info.plist.
As our package is created with Marmalade's deployment tool, these elements need to be manually included in an Info.plist that is copied directly (with a much smaller amount of pre-processing) into the final .ipa.
Marmalade includes a standard Info.plist file within its installation for this purpose. However, you can override this, and we had done so by making a copy of their file, and updating it with changes we needed to make.
A later version of Marmalade made some changes to this file, and we hadn't copied these over into our file, and the difference is apparently what was causing the App Store to think that the App was built with an earlier version of Xcode than the version actually used.
The values which differed were DTSDKName, DTSDKBuild, DTXCode, DTXcodeBuild, DTPlatformBuild, and DTCompiler.