I am currently using OSX Snow Leopard with Xcode 4.2 and Titanium v 2.1.1. and I installed iOS 5.1.1 Sdk as per this quesiton: How to get iOS 5.1 SDK on Snow Leopard.
However when I try to build my generated xcode project file from the Titanium studio in Xcode I get a whole bunch of warnings. See image. I have set the base sdk target as 5.0 for the app in Xcode. Can't find much on Google or their forums.
I tried creating a new project and copying the contents of resources over and still get these warnings. Is there a better way and of course a fix? I need to get this app complete for this weekend and this is making me nervous that the app store will reject it.
Any ideas?
Thanks!
Unfortunately, that's the way a Titanium project looks like. If you're app is compiling and you're not receiving errors, you should consider yourself happy.
App Store will not reject your app because it has warnings. They won't even see that. You're getting compilation warnings and they are not visible on the binary you send to Apple.
Related
I have found similar questions in this and this articles, but neither can solve my problem.
The message given by Apple Store Connect was also "ITMS-90725: SDK Version Issue - This app was built with the iOS 14.4 SDK. All iOS apps submitted to the App Store must be built with the iOS 15 SDK or later, included in Xcode 13 or later."
However, I have checked that I am using xcode 13.2.1 which works with iOS 15.2 SDK, running on macOS Big Sur 11.6.4 (well.... a 2015 iMac, kind of old though). I believe it is capable of building a project with iOS 15.2 SDK, but I just can't find where I shall tune (if necessary) to avoid it keeping using iOS 14.4 SDK to build my project. Could you please help me solve the issue? Thank you very much!!
The figures below show the environment I mentioned above:
Looks like you have multiple Xcodes installed, please make sure you have selected the correct version for your Command Line Tools
I found that it was an embarrassing reason which caused the problem I raised above. I think I am responsible for showing what was going on to all who have read this post, and especially to those who had paused to think about this issue.
In short, Xcode 13.2.1 does build the app using iOS 15.2 SDK.
I was able to successfully archive, verify in Xcode, and uploaded the binary to app store connect. However, I was not familiar with the app store connect and did not aware that there was another binary built with iOS 14.4 SDK which was left by my predecessor.
Though I tried several times rebuild and re-upload, I kept falsely submitting the old binary to Apple's reviewer.
That's it, and no bug or secret about Xcode using older version of iOS SDK to build apps, it is just not true. Xcode does build using its latest SDK. Again my apologies to those who also worried about this issue.
I have tried to build an app through to the AppStore but they rejected it due to the app using sdk 11.4. Stating that it needs to use the updated version of 12.1.
The current Xcode I have installed is 10.1 or 10B61 which is the latest without making use of a Beta. I have searched through the settings trying to find how to update the sdk as well as maybe target that newer base SDK.
Things I have tried:
Searched for newer Xcode (stated above)
Searched through settings for the base SDK version number so it can be changed.
Went to AppStore to find any updates for Xcode (there were none)
Tried googling how to change/update the sdk, but none give an explicit answer on where this can be done. It merely states that Xcode 10 should come with a base SDK of 12.1, but that does not seem to be the case here.
Please note that this is not to target the minimum version. I know where that is and it is set accordingly. No issues there.
EDIT:
I have run $> xcodebuild -showsdks and it shows that sdk 12.1 is the sdk that is installed.
However, it seems that it is somehow overriding it to 11.4 when it is trying to build to AppStore. Not sure why.
The issue did not seem to be with Xcode itself but rather Bitrise that we were using to build and publish the app to the AppStore. Once the correct stack was selected for the building/publishing, it managed to build, however, we then found a different issue.
Using Xcode 10.1 we built the app in iOS 12.1, however, Bitrise seems to have an issue with React-Native third-party dependencies when it comes to Xcode 10.0+. It just doesn't seem to install them correctly and throws an error while compiling. (dependency: double-conversion)
The only advice we could find online was to downgrade xCode to 9.4 and then manually add the Device Support files (from targeted SDK to 12.1) to the app. This is something we don't want to do.
We are waiting for Bitrise to sort their stuff out, but in the meantime, we are looking into building straight from Xcode or Fastlane.
I have been converted my swift code to 2.3 version. App is running perfectly in simulator for all the version like 8.0+, 9.0+, 10.0. But it is not at all running on physical device, showing multiple errors like "Could not build module Frameworkname" and many more regarding frameworks and I am using some classes which were written in Objective C to my swift project those are totally showing errors while running in physical device. Any help would be appreciated.
Eventually, I get rid of this issue, Its all about the Xcode issue, may be some files been deleted from the Xcode. Installing new copy of Xcode is resolved the issue.
I have searched Stack Overflow, Google and fellow peers for a current workaround in Xcode 6 for this error but have failed in doing so.
Note that this error occurs ONLY when attempting to run my app ON A DEVICE USING XCODE 6.
(This is not an issue when using the simulators, and I can build my app on a device using Xcode 5)
It seems to be a framework or library issue, but since it is able to work in almost every other possible way, I am not sure where the solution resides. I was using Xcode 6.0.
Here is the error:
I have checked my architecture settings, my frameworks and project files. Everything that needs to be included seems to be there.
This looks like it might be a silly error to do with Cocos2d and/or Xcode6. I have used SpriteBuilder to create the app. If you have a fix or have this error, any insight would be appreciated, thank you!
Found a fix. Downloaded the new Xcode6 version from the App Store. Xcode 6.0.1 (6A317) and it runs on all devices and simulators.
(There was no notification to update Xcode, you must search for it and download the new version)
I can't upload an app to iTunes Connect.
Xcode uploader says that I'm using allocBatch:withEntity:count:, allocWithEntity:, IndexForKey:, fastIndexForKnownKey:
I'm not using this methods, and I don't know where they could be. A week ago same code was uploading successfully. What can be the cause of such behavior?
UPDATE
Submitting with older Xcode is not working anymore, this error reveals on binary processing.
I had this exact issue using Yosemite with Xcode 6.1 and using Objective C. I also got a warning on validation saying you can't upload an app created with a beta version of Xcode, which 6.1 is at the time of writing this.
I trashed Xcode 6.1 by dragging it to the trash form Finder then downloaded Xcode 6.0.1 GM from the App Store. I tried twice to install 6.0.1 over the top of 6.1 but it didn't work, hence the trashing of 6.1
Having cleaned and recompiled my app with Xcode 6.0.1 it validated and submitted to the app store with no problem. I hope this helps.
I fixed it by changing the deployment target from iOS4.3 to iOS5.0 all fixed using Xcode 6.1
I encountered the exact same error when using Xcode 6.1 (and its bundled Application Loader) on Mac OS 10.9.5. Clicking "Back" within the Application Loader and re-submitting the same binary worked. In other words, trying a second time succeeded. My app was built with iOS SDK 8.1.
You don't have to delete XCode 6.1. It would become handy in couple days. Just download XCode 6.0.1, copy it somewhere, and use sudo xcode-select --switch /Applications/Xcode601.app/Contents/Developer/. Then start it, and build your great app with it.
The API differs between iOS 7 and iOS 8. I got my App validated by switching to Deployment Target "8.0" - built with XCode 6.1. It might not be the solution to all you guys but you could give it a try.
Might have happened to me because I recently started using UIAlertController -> seems to be an iOS-8-Feature. On iOS 7 this would be UIAlertView. So if you use some nifty new features they might not have been available with previous iOS versions - thus non-public API.
Increasing the version number of my app did the trick for me.
EDIT: Just saw a comment in my bug report to apple
So most likely the version number had nothing to do :D
I got the same problem in Xcode 6.0.1 if I use the archive created by Xcode 6.1. It works if I recreate the archive by Xcode 6.0.1. That means the non-public API is added by Apple in Xcode 6.1.
I tried to delete all DerivedData.
/Users/{user_home_folder}/Library/Developer/Xcode/DerivedData
and I validated successfully.
http://qiita.com/PGMY/items/831618ad416780e0dc7c
i had meet same issue when i cancelled archiving to app store. Apple send me email about this subject. And than i recreate archiving and send to App Store. Everythink is ok for a now.