Deploying to App Store using MonoTouch - ios

I have read the documentation to allow deployment of an iOS App to the AppStore using MonoTouch. Here is a link that explains the same:
http://docs.xamarin.com/ios/Guides/Deployment%2C_Testing%2C_and_Metrics/App_Distribution_Overview/Publishing_to_the_App_Store
I have been able to create the MonoTouch Archive using the 'Build Archive' option as explained. However, when I go to the XCode Organizer, I do not see my Archive in there. Is there a specific reason why this doesn't show up in Archive as documented?
Have any developers found any alternate means of deployment? I also saw an option called Zip App Bundle. However, I do not know if that is used anymore.
Any guidance on this issue would be highly appreciated.

This wasn't known until recently, but the archive format that MonoDevelop outputs is only compatible with Xcode 4.5 (maybe 4.4 as well, not sure - but I know that it doesn't work with Xcode 4.2)

Related

Problem uploading my iOS app with C++ libraries to app store connect

I've been developing an iOS apps that implements some C++ libraries which are later converted into .dylibs in order for iOS devices to be able to run the app. I can run the app in any iOS device without any problem. I also can archive a development .ipa and test the app in other's people devices.
The problem that I'm having is when I submit the app into app store connect in order to test it using TestFlight and be able to distribute it into the app store. I'm getting the following errors when submitting it:
TMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it.
TMS-90424: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it.
I have tried some solutions, including the ones suggested in here: https://developer.apple.com/library/archive/technotes/tn2435/_index.html#//apple_ref/doc/uid/DTS40017543-CH1-TROUBLESHOOTING-BUNDLE_ERRORS
I'm not sure if I'm correctly implementing the libraries into the project. I did what the link said, which is embedding the libraries into frameworks, but that didn't solve the error. I would like to know if there is any tips or solutions to what I'm doing to see if I'm doing it right or if I can take another path to solve the problem.
Make sure you build and export using an official release of Xcode, and not any Beta version.
Have you tried contacting Apple support for some insight into the problem you're having?

Xcode 7.1 (7B91b) You are not authorised to upload to the App Store

I downloaded Xcode 7.1 from the App Store today after working from 7.1 beta downloads from developer.apple.com and have a new iOS app build to upload. So I did:
Product > Archive
Upload to App Store (or Validate)
But the response was:
You are not authorised to use this service
Intriguingly, when I 'Export' the build to the Desktop and then use Application Loader 3, it uploads without error.
Is this an iTunes Connect bug? Or is there a new Xcode checkbox I've missed?
Note: I've also tried removing and re-adding my AppleID as suggested here, and restarted my Mac for good measure (which actually allowed the validation to work once), but still no luck uploading directly from Xcode > Organiser.
I met the same issue today and I think it is a bug of Xcode 7.1
Finally I managed to submit my app via Application Loader. There were warnings but it did work.
Here are the basic steps:
Archive
Export
Xcode menu --> Xcode --> Open Developer Tool -->
Application Loader
Double click "Deliver Your App" and choose the
file exported in step #2
click next and follow the instructions until
the end
Here's the quick solution:
Don't use Xcode beta versions to submit apps for release — it's beta for a reason and shouldn't be used with production code.
Submitting Apps
Apps that are created using beta versions of Xcode or that are built
for beta versions of operating systems will not be accepted on the App
Store and Mac App Store. Apps that you submit should be developed
using the latest version of Xcode from the Mac App Store and should be
built for publicly available versions of iOS, OS X, and watchOS —
except when GM seeds are available. When a GM Seed of Xcode becomes
available, use it to develop your app for submission. When GM seeds of
iOS, OS X, or watchOS become available, build your app for these
versions.
↳ https://developer.apple.com/support/pre-release-software/
Having the same problems as all of you, just thought I'd share that I found a way to Validate successfully, you have to disable the "Include bitcode" checkbox before moving forward. As for the actual upload to App Store, no work around for that one other than use the Application Loader...
Also I've been seeing this too since XCode 6.4, but it seems once the current version has a couple of months after it's originally released it starts working again... fingers crossed that it starts working again soon, because uploading straight from Organizer is so much better. (I saw the Beta Version post, when I say after a couple of months for current version I'm not talking about Beta versions, just in case ;) )
Same problem here.
Downloaded Xcode 7.1 from the App Store and it refuses to upload a new version.
Happily Application Loader worked ;)
Hopefully this gets fixed quickly.
One possible reason for the issue could be multiple development accounts under one name (personal and company). I've read elsewhere (apple radar) that that caused earlier problems of this kind.
Happens here if the dev account is only admin. I had to use the central account for uploading our apps. I think this problem startet sometime with XCode 6. Didnt investigate further though since Application Loader works in cases when I dont have access to the central account.
I also have the same problem today.
Finally, I used the application loader to upload successfully,too.
Theres a few solutions I have come across to solve this issue.
Most common being to remove and re-add your developer account.
This won't work on its own though, you need to also 'view details' on your account and have Xcode download your provisioning profiles again.
The other alternative is to upload your build using application loader. The disadvantage to using this solution is that should you be trying to upload using a beta build of Xcode or OSX you won't be able to change your apps .plist in the archive folder to trick iTunes connect into accepting it. In this instance all you have access to is your ipa.
Disable the "Include bitcode" checkbox worked for me.

Xcode 6.4: OS X and iOS Targets, Cordova

So I just installed Xcode 6.4 to start some development on my new Mac, and after creating an empty iOS project, I see the message "No OS X or iOS Targets Found". I also see a message under my project folder: "base SDK missing. But I was under the impression a normal install of Xcode also installs all basic SDKs required for Mac and iOS development?
It seems there is absolutely no information on this message on the web. I think it is not an error per-se, more like I need to create or import some build targets, but can anyone explain what I need to do to get my project built and running?
I also need to use XCode with Cordova (or PhoneGap), but there does not seem to be any clear information on how to get XCode properly set up for that. Any pointers for this would be appreciated.
I haven't created an empty project in a long time so can't really comment on the empty project. But to make your life MUCH simpler, I would use one of the default templates and go from there. The simplest is probably the "Single View application".
Admittedly, this does not solve the issue, but it will get you going (which I assume is really what you want to do).
Go to the Project menu, then Edit Project Settings. Select the Build tab, and near the top, there is a Base SDK setting.
Choose the latest iOS.
You might need to clean the project or restart Xcode.

Archive validation failed with errors during app store distribution process

I have been trying to send my application to apple for submission and it is my first experience about it. I have searched the errors and applied all suggested solutions. However none of the solutions didn't work for me. I got the error below.
I set the ios deployment target as ios 7.0 and later versions for both of the project target and Alamofire framework. Also, my Xcode version is 6.1.1 . However, I could not understand that why not working.
Could you help me please ?
Thank you for your answers
Best regards
Unfortunately, iOS 7 does not support frameworks. Here is some additional information about it. The known workaround is to add Alamofire to your project by dragging the Alamofire.swift file directly into your project.
A good way to track this type of usage in your project is to use Git submodules. You could also download a version and copy the file into your project, but then it gets more difficult to track what version you have compiled into your project.
This will build Alamofire into your project as though it was just another Swift file associated with your project.
This is also why most Swift CocoaPods are iOS 8 only.

Testflight SDK version not updating in project

I recently downloaded Testflight SDK version 3.0 and added header files in the project as shown in https://www.testflightapp.com/sdk/ios/doc/3.0.0/. Previously I was using SDK 2.1.4
But when I archive the app and try to upload it to Testflight it still shows me my previous SDK version 2.1.4. I dont know whats the issue, i tried so many times but the sdk is still not updating to 3.0 in my project.
Just ran into and fixed this problem. In my case, the library search paths were pointing to the wrong place (with an older version of the library). Search for "Tetflight" in your Build Settings and delete or change any incorrect paths.
Only adding the header files is not enough. You also need to update libTestFlight.a to the latest version. Replace the older static library with the new one. Also make sure it is properly linked (Project, Build Phases, Link Binary With Libraries). Then clean the project, rebuild, and you should be fine.
If you already did that, you should say so in your question. Now you only mention header files. But based on your description it could be that you are still linking an older version of the TestFlight static library.
I ran into this issue first from the question, but then immediately couldn't upload my ipa into TF because it contained the SDK. TestFlight appears to be purchased by Apple and also TF has since removed support for Android.
TestFlight does not accept builds with TestFlight SDK

Resources