Unable to delete app in iTunes Connect with "Developer Rejected" status - app-store-connect

My app was rejected. There was no Delete App button in iTunes Connect. I uploaded the binary again, rejected it, and there is still no "Delete App" button under "Transfer App."
How do I delete this app altogether?
I don't have enough points to post an image, but you can see a screen shot here:
The iTunes Connect Developer Guide states:
You can delete your app when its status is one of the following:
Prepare for Upload
Waiting for Upload
Invalid Binary
Developer Rejected
Rejected
Metadata Rejected
Developer Removed from Sale
Removed from Sale"
So why can't I delete an app? I even tried with another app. Same problem.

I had a similar problem and contacted iTunes Connect support.
They replied with this:
I believe the reason that you are unable to delete this app is that it does not have one delivered and approved version. Apps must have at least one approved version before they can be deleted; if your app has never had an approved binary delivered, you will be unable to delete it.
Basically, you're unable to delete an app that was rejected and never approved.

Related

Can review rate app after delete and reinstall of the app iOS

I gone through the appirater sdk(iOS) on git, I have question.
If i rated the app and then i deleted the app from device and again installed. In this case will appirater allows to rate again ?
Yes, in that case Appirater will prompt the user to rate the app again.
The data about whether or not the user has rated the app is only stored locally, so deleting the app deletes that info.

Xcode 8 GM upload app to iTunes Connect issue

I use Xcode 8GM for build & upload app to iTunes Connect (Testflight). No error messages, no warnings, no e-mails from apple team but after 'Processing' status on iTunes connect I see red badge with exclamation point as status of my build. Third-party libraries are: Google Maps, Google plus, VK-, FB- SDKs. No bit code enabled, no private API used.
The only message that I can see on iTunes Connect is 'There was an error importing this build.'
Someone faced with such a situation the last 3-4 days? Can I see where a reason for rejection of my application?
TNX

Key Chain Access issue when app distribute through MDM

In our ipad application user has to enter his details for registration. After user enter his details we save those details in the Device's keychain. So next time user launched the app user can use the app without registering again. Since we save it in the keychain even the app reinstall by deleting is also works fine.
To write to key chain we use sskeychain class as most developer do. This feature is working properly in devices without any issue.
One of our client use their symantec (unitymobile) mdm to distribute this app to their users. But when user install it through the mdm app gives following error when saving data to the key chain.
"The operation couldn’t be completed. (com.samsoffes.sskeychain error
-34018.)"
Initially we thought this is due to one of the policies they have included. But no luck. Can some one please tell me what has happened here and how to solve this issue.
P.S.
Actually underlying error was this.
(OSStatus error -34018 - client has neither application-identifier nor keychain-access-groups entitlements)

Trouble generating MASReceipt during development

I am working on developing a Mac application that has an in app purchase. I have done this before on iOS, but I cannot get it to work with the Mac app. After doing some research it looks like I will have to get and validate a receipt from the Mac App Store before this will work.
I believe that I have followed the steps to do this correctly,
1.) Build the app in Xcode.
2.) Launch the app through finder
3.) When prompted sign in with a TestUser account created in iTunesConnect
4.) The app closes with the error message
“AppName” is damaged and can’t be opened. Delete “AppName” and download it again from the App Store.
When I open up the bundle though I do not see the _MASReceipt/receipt folder and file - and I am still getting invalid product identifiers from StoreKit.
These steps seems to work for me the last time this happened:
Log out from Mac App Store.
Force quit storeagent and softwareupdated processes.
Try double-clicking the app to start it again.

iTunes Connect Reports "Invalid Binary" for Mac App

I am trying to submit my first application to the Mac App Store. I have setup the signing certificates on my computer, as well as setting up the application in iTunes connect. Xcode allows me to produce an archive of my app, and even export a signed pkg file. Both Application Loader and Xcode say that my binary passes "validation", but shortly after uploading my app to iTunes connect it is reported to have an "Invalid Binary." I read on Apple's iTunes Approval Process page some reasons why this might happen:
Appears when a binary is received through Application Loader, has been processed, but your binary is invalid. Examples of an invalid binary are: your binary icon does not meet our requirements, you have placed the payload directory at the wrong level in the .app wrapper, you attempted to use a non-increasing CFBundleVersion, etc.
Unfortunately I am not receiving an email when this error occurs, and nothing is telling me what the problem is. I am kind of hoping that Xcode would tell me if I signed my binary wrong in the "Validate" stage, but I may be wrong.
My question here is: why might iTunes connect be reporting an "Invalid Binary" and how on earth can I fix it?
EDIT: I have taken some screenshots of my project's configuration settings, and of iTunes connect:
iTunes connect app page
Application in the Archive list
Entitlements plist
Code signing settings
Info.plist
Build settings (architectures, etc).
You most likely are trying to submit a build that has the same version number as an earlier build. All builds that you upload to iTunes connect must have different version numbers. For example: Joe submits his first build of his app to iTunes connect as version 1.0, next time he submits he must change the version to 1.1 or any other higher value.