My problem is that after migrating project to XCode6 I just can't submit my app - it's permanently becomes "invalid" - get status "invalid binary" after 10-30 minutes.
Before migration there was no any troubles
There is no code modifications since old XCode version (5.1)
Most frustrating is as other users I received email from ITC
support, but it does not contains any details at all!
iTunes Connect
Dear XXX,
The status for the following app has changed to Invalid Binary.
App Name: XXX
App Version Number: 2.0
App SKU: XXX
App Apple ID:XXX
To make changes to this app, sign in to iTunes Connect and open the Manage Your Applications module.
If you have any questions regarding your app, click Contact Us in iTunes Connect.
Regards,
The iTunes Store team
I wrote email to ITC support, but there is still no answer. Any suggestions? It's hard to me find any reason cos app successfully passes validation during upload.
Large amount of tests lead me to next conclusion: one of third-party libraries (AppsFlyer) uses Advertising Identifier. I removed it from my app and for now all is ok.
I think this problem is because of new builds/prereleases system - things which previously lead to warnings during validation/uploading now are not appear.
So annoying...
I'm using several libraries which uses the AdvertiserId on several apps and the builds were submitted successfully.
When submitting the app, Apple ask 3 question about your app. The third is about using the Advertiser ID. Did you checked any of the options there? If not, You should....
Related
A friend commissioned an app to be developed some years ago but the developers went out of business. It was removed from the AppStore in 2015 but she still has it running on 4 devices (she's a university professor and uses it for her research). She now wants to put the app onto other devices and as an app developer myself I'm trying to help.
Is this possible? If so, how?
We've tried to contact the original developers but they are unable to find the source code. Rewriting is out of the question as she can't get funding for this until she can prove her results - for which she needs the app on more devices.
We have managed to get the original .ipa file off one of the existing devices. When I try to put it onto my iPhone using XCode Devices it does it, but when I try to run it it pops up asking for an appstore user name & password and won't go any further, even if I enter my own valid id. Perhaps it's contacting the appstore, finding that the app isn't on there any more and bombing out?
I've tried resigning the .app with an ad-hoc development one using my own developer id but when I try to install that on my iphone it starts doing it then says "The application could not be verified". I've also tried creating a dummy app with the same name and version number and following these instructions Resign IPA from development to enterprise but that doesn't work either. I've researched the error message to no avail. I am deleting the previous app each time I try to put a new one on.
Is there anything else I can try?
Every time we upload an app with an issue (missing entitlement, privacy string missing from the project's .plist), iTunes connect emails the error to every single one of the tester emails in our list, even if they're not registered to test for the application I am uploading.
Currently I am the only person in the list for this application, and yet it's sending the email to everyone testing an unrelated app.
How do I turn this ridiculous behavior off and stop annoying them?
This is not a bug. It is a 'feature' of PEBKAB.
The issue was another developer had quietly added the users to itunes connect as internal testers on a separate project. They had all been given a 'developer' role, and when I created the app, they were automatically put on the developer email list for that one, too.
A quick diddle of the users and roles table fixed it all up, no trip to Apple Support required.
Unfortunately this is just how iTunes Connect works. I have reached Apple complaining about this, their answer was that I should use External TestFlight distributions.
Honestly I really recommend you to use other beta distribution platform like beta by Fabric, the build process is using ad-hoc builds, in our team we use beta by Fabric for small builds then once we are almost ready to push to the AppStore we run a small test by using the final build in TestFlight.
I'm not saying Testflight External distributions are bad but is not the right tool for a daily workflow some times you can't afford waste 3 to 6 hours waiting for apple to approve your new build.
I am experiencing some issues with TestFlight and I am fairly new with iOS development so I am certain I must be missing something extremely small and frustrating.
We have our personal Apple IDs on our devices to test, and we sign into iTunes Connect with our work email/Apple ID (of which we were added to an organisation).
When I upload a new build and I want to get internal testers on it (take note it is only myself and another co-worker), only I get the TestFlight notification and email and not my co-worker. No notification, no email.
The strange part is that both of us are able to sign into iTunes Connect with our work email/Apple ID. And both of us are able to see and change details on the iTunes Connect Store.
I have tried removing him from the internal testing team and re-adding him, only for the status to show "Notified" but he does not get a notification or an email.
I have also removed TestFlight and re-installed it, and once in the application, the only available version to download is an older version (roughly a week old) and can not update the version to the latest build.
Everything was working one week ago. Any clues or advice on what to check or look out for?
Thanks to all in advance for all the help and information provided.
Make sure you have verified both your work and personal accounts. Apple has weird issues with this sometimes. You will also need to verify your account details again each time you add a new email address :)
I created application in iTunes connect and download archive for beta testing. But I make a mistake in application name and now I want to delete it and create new with correct name. There are many similar topics, but the solution to deselect all countries in Pricing not working for me.
The following error(s) occurred:
You must select at least one App Store territory in which you want to make your app available.
In apple documentation it is also said, that application should be reviewed at least 1 time to be rejected by developer, does it mean that I should send my app for review and only after it I would be able to delete my app? It is kinda stupid. At the moment my app has status "Prepare for Submission" and has not released version, only beta testing.
In your case you need to create new application in iTunes Connect with new bundle id (you should also generate new in developer portal). Because you can't update it:
The bundle ID must match the one you used in Xcode. It can't be
changed after you upload your first build.
You can upload your binary and send to review and remove your wrong application when it will pass review.
Also check this question, #pion answer with comments: Deleting an app in iTunes Connect
They provided some workaround, maybe it will help you.
i follow Analyzing Crash Reports
https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/AnalyzingCrashReports/AnalyzingCrashReports.html
and still no data present.
do i miss something which dose not write on Analyzing Crash Reports.
i checked all step
but still like this,
We also had this issue for a while now and were struggling to find the cause.
Intercepting Xcode's requests showed us the actual error when Xcode tried to load latest crash reports:
The updated Apple Developer Program License Agreement needs to be
reviewed. In order to update your existing apps and submit new apps to
the App Store, the user with the Legal role (Team Agent) must review
and accept the updated agreement in their account on the developer
website.
This is the same error message we get when pressing the "Download dSYMs…" button.
This was confusing, since we've already accepted all agreements we could find in both, the Member Center and in iTunes Connect.
Later we found out that we do not just have to accept the agreements for our app's App Store account but we have to accept the agreements for all App Store accounts linked to the same Apple ID. So it depends on your Apple ID which explains why sometimes only some developers are affected by the issue.
TLDR: If your Apple ID is linked with multiple App Store accounts (in Member Center and iTunes Connect) make sure that for all of these accounts the agreements are accepted.
Just throwing in my two cents here- In my case, I wasn't seeing any crash reports except some from months and several versions ago. Turns out I had some updated agreement from Apple I haven't signed, and as soon as signed them, all the crash reports started to flow into my Xcode.
Mysterious as always, Apple, when it comes to Xcode. 😡