app-store

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 dunno 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

My app is a photo-sharing app based on Facebook, and Facebook is the only option for register and login, but my app got rejected with following message: 17.2: Apps that require users to share personal information, such as email address and date of birth, in order to function will be rejected: We found that your app uses Facebook login for authentication purposes only - but does not include any account-based features offered by that site. This is not in compliance with the App Store Review Guidelines. It would be appropriate to modify your app to include account-based features of that social

Working with both app distributions services (android market and Apple App store) I have discovered a mystery. The file size of an app is in general larger for an Apple app than for a Android app. I can't seem to find any explanation for the differences, and it seems to be an untouched subject. I have tried allot of different apps and the difference seems to vary between a couple of MB to 6-8 MB. So the question is, how come the file size is larger for Apple apps? What is the extra MB used for? Examples: BBC: Android: 918K - https://market.android.com/details?id=bbc.mobile.news.ww Apple: 6.7

I installed Xcode 4, thinking it would be similar to Xcode 3, and now I cannot get my binary to the App Store using organizer which I believe is the proper way to do this. Has anyone got this working properly? Not sure what setting I need to update - All I get is an "invalid binary" message. Of course, it is a critical update I need to submit. I've had something similar. You should check your code signing settings. Xcode 4 introduces "schemes", which are a little complicated. Think of them as sets of configurations. In Xcode 3, you could only have one such set of settings. I believe that you

I use iTunes API lookup to get app data by App ID this way: http://itunes.apple.com/lookup?id=543891460&lang=ru Even if app is designed for iPhone5 , in JSON I get 3.5 inch screenshots (under screenshotUrls array). Is there any way to get 4 inch . screenshots? Check again. Apple seems to be rolling out new 4 inch screenshots since a few hours. Screenshots now also have the pixel-size in the filename. Well, kind of: it doesn’t seem to be 100% correct (yet?). The possible values are: xxx.xxxxxxxx. 1136x1136-75 .jpg (4" iPhone) xxx.xxxxxxxx. 320x480-75 .jpg (3.5" iPhone) xxx.xxxxxxxx. 480x480-75

If I have a free version of a paid app in the Android market how can I place a button in the free app that opens the paid version in the market? Add this to the button's OnClickListener's onClick method: Intent marketLaunch = new Intent(Intent.ACTION_VIEW); marketLaunch.setData(Uri.parse("market://search?q=uk.co.ashtonbrsc")); startActivity(marketLaunch); Replacing uk.co.ashtonbrsc with a search term that will find your app. Even better to use "market://details" instead of "market://search": Intent intent = new Intent(Intent.ACTION_VIEW); intent.setData(Uri.parse("market://details?id=com

I submitted my app to the app store and received the following warning (not error): Too many symbol files - These symbols have no corresponding slice in any binary [XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX.symbols, XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX.symbols] What caused this issue? How can I fix it? Will it create issues with crash reporting to Crashlytics? Same problem occurred to me, and here is why this happening and the solution. Short version : Redundant dSYM files are being produced due to improper project settings. In my case, the "project" consists of one major xcproject and several cocoapod