itunesconnect

I am trying to upload my app but I get this error when I try to upload it through Application Loader: A new version of the iOS Paid Applications Agreement with updated pricing information is now available in the Contracts, Tax, and Banking module. To be able to continue creating new apps and upload binaries for the App Store, your Team Agent must review and agree to the updated terms of the iOS Paid Applications Agreement. To access the iOS Paid Applications Agreement, you must have accepted the latest version of the iOS Developer Program Agreement in the iOS Dev Center on developer.apple.com.

I am trying to submit a new version of my existing app in itunes connect but I am having difficulties. So I uploaded my build like usual and upload done. I went into pre-release and saw the status processing. This was 12 hours ago, now though it has changed from processing to inactive. I ignored that and went and chose the build anyways and clicked on "Submit for Review" I get an error saying You must submit your builds using Xcode 5.1.1 or later, or Application Loader 2.9.1 or later. After you’ve submitted a build, select it in the Builds section below. But I did submit a build using Xcode 6

I have noticed using different applications that, even when you remove the iPad compatibility from xcode (see picture below) the app will still show that is compatible with iPad in the iTunes app page (see picture below): Therefore, I am wondering, how did Whatsapp removed the iPad compatibility from it's app? (see image below): Thank you Because WhatsApp does not work without telephony (the app requires the phone number) they did use telephony as UIRequiredDeviceCapabilities value in their info-plist. This limits the app to devices that are designated as telephones. Which currently covers

I have been fighting this issue for days now and about to beat my head against the wall and put myself out of my code signing/app submission misery. I have an application that has been submitted to the app store and accepted no problems (ver 1.0.0). I was able to publish the first update (ver 1.0.1) with a little bit of trial an error using XCode 3.2.4 and iOS 4.1 via Application Loader. Now I am on XCode 3.2.5 and iOS 4.2 and am trying to publish an update (ver 1.0.2) via XCode Organizer. I can successfully build my application against the AppStore Distribution provision when I set my Bundle

I know how to sign an app with Appstore mobile provision, and how to re-sign an Adhoc-signed IPA with Appstore mobile provision. This is not my question. My question is, can you submit Adhoc-signed IPA to Appstore / iTunesConnect, and have it pass Apple verification and eventually be distributed through Appstore. Why? So that I don't have to store a redundant Appstore-signed IPA along every Adhoc-signed release candidate IPA, and don't have to do the extra step of re-signing that requires a Mac machine. When using Application Loader , it is able to find all the stupid little errors, like

Got a build rejection The app's Info.plist must contain an NSMicrophoneUsageDescription key with a string value explaining to the user how the app uses this data. The app does not use microphone. Or so I think. How do I track down where mic is used? UPD23112016: given that the lazy answer is being upvoted I've filed a new feature request with apple to close this security hole. UPD05042017: it is still bothersome that once you proxy mic access into some 3rd party framework via some half baked NSMicrophoneUsageDescription you have zero control on where and when it can be used if user agrees to

i developed an app for on Online Magazine with non-renewing subscription type. Apple Developer Guide say : " it's not appropriate to track the subscription using the UDID or the Apple Store ID. The subscription should be tracked with an external server that you should provide in order to deliver subscription to multiple devices. Additionally, please keep in mind that it is not appropriate to force user registration to meet this requirement; such user registration must be made optional. " and i recently had my app rejected by apple for those reasons: 11.6: Content subscriptions using IAP must