I have implement mapbox in the project , its ok work in simulator and device but when i am going to create build the issues has come . the issues attach here with screenshoot.
If I remember correctly, you will have to select your projects target, go from the General tab to the Build Settings tab, search for Enable Bitcode and set it to No. Of course, remember to do a new Archive before uploading it again.
I had many many issues with Mapbox and zero support from their team. I also had a bunch of error messages when uploading. One work around was using Carthage and manually adding in the frameworks instead of using Cocoapods. I hope this helps.
Good luck!
We are actually trying to upload our Xamarin mobile application to AppStore. Application is built using Xamarin.Forms and uses Pspdfkit for pdf viewing on Ipad. This is the only external library we are using. Project builds correctly but when we try to upload to AppStore, we are getting the following error:
Heading
Invalid Signature - Code object is not signed at all. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html Once these issues have been corrected, you can then redeliver the corrected binary
Can someone gives me the details steps to sign an external library on Xamarin Studio?
The problem you see is most certainly not caused by the PSPDFKit library but by your app itself. iOS apps must be signed using different certificates:
There's one for development
one for Enterprise distribution
one for App Store distribution
You will have to create a proper distribution certificate in order to upload to the store. This involves setting up an App ID, the certificate itself and a provisioning profile which holds everything together.
Your entry point to those certificates is Apple's developer site.
You can read more about the publishing process with regards to Xamarin specific things (it really isn't that different from using an app built with Xcode, other than the different IDE) in Xamarin's documentation.
To automate the process and make it easier to manage you might also want to have a look at a collection of tools called Fastlane.
I'm new to this, so please bear with me. I have an app live on the App store, developed in Xamarin. The current version is 1.0.3 and I want to keep it that way. I want to send a new build (i.e build 85) via Application loader with the same version number (1.0.3).
I want to know:
Will it become live as soon as I send it or will I have the option to keep the previous build (i.e 84) live and not this one (i.e 85)? I want the previous build (84) to be live.
Can I upload a build that I got from Ad-Hoc > iPhone => myApp.ipa / currently I'm doing this only or should I generate an ipa from a different configuration like "Release" or "App Store"?
If you try uploading your build with the same version number as your current live build, Application Loader will give you an error message saying you need to create a new app version profile in iTunes Connect.
You should be able to upload an Ad-Hoc build to ITC. However, you may need to tweak your entitlements to enable beta testing via TestFlight:
App "does not contain the correct beta entitlement"
My development environment is:
OSX Mavericks, Xcode 5 Cocoa mac application
I have been using FANN to train and run a ANN. It has worked so far and I have been able to train and run an ANN. I have even made a simple command line application to train ANNs using FANN. However I have run into a problem that may have to do with the way FANN is distributed.
I wanted to export and share the application I had made, so I archived the Xcode project. When I did this I made sure to copy libfann.2.2.0.dylib under Build phases, so the end user would have the library which is needed to use the FANN code in my app. However when I tried to save a developer ID sign application using Xcode it failed to code sign it. I can still save it without code signing it. The interesting thing is that if I remove libfann.2.2.0.dylib from the copying phase under Build phases, Xcode can successfully code sign the application and save it. However if I do this the resulting application is corrupt because it cannot find the FANN library.
I made libfann.2.2.0.dylib according to the instructions on http://leenissen.dk/fann/wp/help/installing-fann/.
I understand that this may not be a problem with FANN, but with Xcode. However I have other static libraries in the same project and FANN is the only one that is creating these issues, so I believe there is a high chance it has something to do with the FANN library. I am not an expert in code signing, but my guess is that there is a conflict between the way the FANN library is made using Cmake and code signing.
Thanks in advance.
I was able to find a solution after playing around with code signing.
I decided to try manually code signing my app with instructions from http://www.digicert.com/code-signing/mac-os-codesign-tool.htm. This did not work. However the code signing tool pointed me to a problem with libfann.2.2.0.dylib. So I checked if libfann.2.2.0.dylib was code signed and it was not. When I saw this I thought I would try code signing libfann.2.2.0.dylib with my developer ID and re-importing it into my project. This strategy worked and I was able to export a developer ID signed version of my application.
I am having some problems when trying to submit my iPhone app to store using Xcode 5 that my app is always failed validation with below errors:
Apple's web service operation was not successful
Unable to authenticate the package: [My app id, ex: 123456789].itmsp
ERROR ITEMS-9000: "The bundle [Bundle ID, ex: com.myapp.mobile] at bundle path 'Payload/[My App Name].app' is not signed using an Apple submission certificate." at SoftwareAssets/SoftwareAsset (MZItmspSoftwareAssetPackage)
I am quite sure about settings (bundle id, certificate, profile, entitlement) because this is not first time I submit app to store, jut don't know why these issues come up, I have tried to search and found some related article but they don't help.
I have this issue for 1 week.
I just selected Standard Architectures in both Project and Target, and it worked for me.
I had the exact the same error, after hours of trying, adjusting all the parameters like the bundle ID or display name, etc. None of them worked.
Finally I got it work. Here is what I did.
I started all over by deleting all the records in keychain, certificates and provision profiles. And just added one certificate and profile for app distribution. There was only one record to make no confusion. And then boom, it uploaded successfully.
I guess my mistake was to submit multiple times of certificates or provision profiles earlier (although I deleted multiple entries but I did see something strange) because I thought the creation process was stuck so I refreshed the browser. Being patient in each steps will eventually saves more time! :) Good luck!
I got the same error today with xCode 7. I resubmitted with no changes and it went through. Probably Apple bug. I am letting you know that sometimes it is not an issue with our project/target settings.
As far as I can tell, this specific error is intermittent and not caused by anything in the app package. I think many of the answers here are people that saw this error, changed something, and saw the error go away, and assumed that their change made it go away.
I would suggest, if you get this error, just try again (worked for me). If it fails in this exact way a second time, and you have some theory about what will fix it, do that and try again. If that works, undo your fix and see if the failure comes back. In this way you will have proven that there was an identified root cause and a fix.
I don't know the cause, but I had the same exact issue crop up this week and just got things to work. I had checked the build, distribution certificate, provisioning profile. I went through all of the troubleshooting steps in Technical Note TN2250 -- no luck! However, I just got it to upload successfully. I happened to have an old Mac Mini that had Application Loader 2.5.1 on it. I created a zip file from the .app within the Payload folder of the .ipa, put this on a USB drive, and watched as it finally uploaded after trying about 50 times with both Xcode organizer and Application Loader v2.9.
Other people have reccomended reverting to a previous Application Loader version. Perhaps the web service endpoint uses a different (and properly working) certificate validation method for older AL versions.
I too have had the same problem and after many hours I managed to solve.
I finally fixed the problem. You needed to download the "Apple Root Certificate Authority" (http://www.apple.com/certificateauthority/) and put it in your login keychain & system, I also put your iPhone disitrbution certified in your system and set all keychian trust values for all certificates to "system default". Finally went through!
For me the problem was in selecting the wrong iOS distribution code signing identity, where I was using a different team as the provisioning profile.
Probably make sure your Code Signing Identity is set to automatic, which will probably fix this issue.
In XCode 6.3, You have connect actual device and selected in the XCode.
I didn't see this listed on here, but I received this issue and realized that I already had a build for this specific Version # waiting for review on iTunes Connect. I rejected the build in ITC and then tried uploading the build again and it uploaded correctly after that. Just in case this could possibly help anyone else out there with this issue!