I've ran into quite an odd problem today. Today my app successfully got onto the app store. However, when I downloaded it I immediately noticed that the apps basic functionality wasn't working. It just hangs when trying to get outside information. I went back to my xcode project, ran it and it worked perfectly. I removed the app store version, and re-deployed the xcode version to my phone, and again it worked perfectly.
Did Apple do something to my code? The part that messes up seems to be a where my app creates a NSURLSESSION that is used to gather data from a website. Perhaps they "cleansed" the url strings that I use? This functionality that messes up is crucial to my app and hasn't been changed since I've submitted to the app store.
Anyone have any ideas why this is happening or how to fix this?
Thanks
Just posting the "solution":
Edit your Scheme and set the "Run" build configuration to "Release". After saving that, clean the project (cmd+shift+k) and run again on your device. By default, that will make you run the app in your device just as it will be ran when published in the AppStore.
And yes, unfortunately you will have to wait another week for Apple to aprove your app's new version as it will go through the review process again. Good luck! :)
For me it was that I was using old promocodes for testing.
That promocodes were from old version of the app (ios downloads app version that corresponds to promocode version), but I was expecting new functionality. So use latest promocodes!
Related
I have created a developer account for two weeks, and now I want to submit my first App. However, when I click new app, the bundle ID list does NOT show the project I would like to submit, but It do show some projects I used to practice. I have look up a variety of solutions on internet, including sign out and log in again, or clean up my Safari data. I have suspected some reason, but I'm not quite sure if it right?
First doubt : some SDK import?
The Bundle ID shows on the list are some small project I used to practice when I was a beginner. Recently, I have tried to use some SDK like Facebook SDK and Firebase. Facebook and Firebase works fine on my simulator and iPhone devices. So I'm not quite think this might be the reason, nut just type on in case I missed something
Second doubt : Xcode version?
When I tried to using Firebase, since iOS 13.3.1 seems not to support, so I update my iPhone to iOS 13.4.1. However, the Xcode should also be updated to 11.4.1, otherwise it cannot connect to my devices. When I look up the bundle IDs listed on App Store Connect, I think those projects are created before I updated Xcode. The project created after updated not showed on the list. But I have created too many projects to practice, so I'm not quite sure I remembered right. I suspect this might be the reason, anyone else met the same problem after updated Xcode?
By the way, there is also a strange thing confused me. I have deleted some projects I used to practiced on my MAC, but they stilled shown on the list... I have manually deleted on my Apple Developer Web.
1) Go to https://developer.apple.com/account and set up the app with its explicit bundle ID.
2) Then go to https://appstoreconnect.apple.com > "Create new app" > Select the previously created bundle ID.
This does not really have anything to do with SDK usage or Xcode setup. (Automatic code signing might do some steps for you, but the most bullet-proof way is mentioned above)
The app is uploaded without errors, but when I press the install button I get this message:
I'm using macOS Sierra 10.12 and Xcode 8.
This has never happened to me in old versions of Xcode. What could be wrong?
TestFlight is currently unavailable, i can't either install from TestFlight or see any of my builds in Itunes Connect. Also my app was in processing for 4 hours, then this happened.
Please check here https://developer.apple.com/system-status/
or this screenshot
Update: Confirmed by Apple
I had the same issue. I never had an issue with setting or not setting the encryption flag. So I thought maybe they made a change today. So I added the key in and it still didn't work. I decided to remove the last build from testing then re-added it. That worked for me. I was immediately able to download and install the app. Hope that helps.
Build another version and upload to Itunes Connect.
Maybe your time uploading have some problem from Apple Server.
I have just checked.
Seems to be working for me this morning now. Incidentally Brad my app had GPUImage embedded in it so just for giggles I also added the "App Uses Non-Exempt Encryption." switch to the embedded GPUImage plist. Not sure if that was relevant.
I regenerate all of the certificates, update the version number of the application, but the problem persists.
Follow the below steps.
Go to My Apps Page.
Remove the Build. Then Save It.
Re Add your Build. then Save It.
Now try to Submit It must work.
I do not know what the reasons are, how to do?Thanks!
In Prerelease section the status of your build should not be "Processing". Just wait some time (10-20 min) after build upload, and it will be ready to use.
I got this problem in Chrome browser. Switching to Safari worked like a charm for me.
I had the same issue. To solve it, the unique thing I had to do was "Clear History and Website Data..." within Safari (version 8.0.3 in my case).
Please, keep in mind that I speak from my experience and that worked for me. I cannot guarantee this as a general rule to fix the problem. Nevertheless I can assure that I tried several alternatives explained here and the one I just described was the solution for me.
It seems to happen if you are too quick between the build finishing "processing" and it being attached to a version and the version being submitted. I just published two apps in quick succession and the second submission had this problem while the first was fine. The only difference - speed of clicking the submit button.
Logging out and back in made no difference - the "problem" is with the submission.
I removed the just uploaded build from the version and then re-attached it, proceeding as normal to submit the release to Apple with exactly the same build and submission artifacts as before, except this one "saved" and went into the review queue.
I got the strange but working solution.
I had tried submitting the app using Safari browser but it didn't work and showed same error. Submitting the App using Chrome worked for me in the first go...
I'm stuck on this too; and have had to work around several other iTunes Connect bugs just to get to this point. What were Apple thinking by releasing this iTunes Connect version? It's completely ridden with bugs!
Sorry, I've tried everything I can: Filing a support case with Apple appears to be the only 'solution' at this point.
Make sure the Version you have on iTunes Connect and the version you gave in the Info settings in xCode are exactly the same.
I had 1.0.0 in iTunes Connect and 1.0 in xCode and it kept giving me this error message. I changed it to 1.0.0 in xCode and it worked perfectly.
I had the same problem. just sign out and sign in again. it should work.
I had the following issue when submitting a build which was uploaded couple of days ago for test flight testing. Then figured out that the provisioning profile of the application has expired so I renewed the prov profile and downloaded and re-archived the application (by increasing only the build number ) and uploaded and submitted it. And it worked like a charm.
I guess apple need to be specific of these error scenarios
In my case we contacted apple and they said the issue is that it seems that we don’t have a correct certificate generated on developer.apple.com. We use Xcode automatic signing management. I refreshed correct profiles, rebuilt and I could submit successfully.
I had the same problem. Tried from different system and it got saved
I have a very mysterious problem.
I am somehow not uploading my new app versions correctly even if everything it seemingly correct. I determine this by download the "new" versions and seeing nothing has changed.
1)
Before release I test my changes are included and working on device-debug + device-adhoc.
2)
I then build and deploy for app store. Before uploading my .ipa file into "Application Loader" I make sure the .ipa file has just been generated. I then select it and the upload/verification process goes find without errros and some days later I get a message new app has been released...
3)
I then uninstall my existing app (just to make sure) and download and install the new app version from appstore - it is still the same. This is driving me nuts. I think I have tried to eliminate potential places where I could have errored, but somehow somewhere something is going terrible wrong for me. This is a fairly recent new problem - never had it in the past.
I am hoping if somehow can think of ways I can diagnose at what steps this is going wrong... I know it must be me that have an error somewhere. I recognize when something looks like a "Doh!" thing, but I believe I have tried a varity of methods to pinpoint it.
I have also tried clear out out scratch/temp directory before building + deploying. However, I am still wondering. Could it be some cache/path setting somewhere that makes Delphi compile incorrect app executable only when doing release builds? (I have of course also long time ago deleted all old directory paths that could contain earlier builds, but still...)
I did not see that you have already tried it on a new buddy phone & it worked. So editing my answer.
Can you try to remove your device ID from the profile settings in developer page & give a try downloading it.
There may be problem in building & compiling with Delphi.
Here is a post that differentiates between the same.
Please do see the accepted answer for that question here.
Hope that helps. (I know you are really pissed off waiting for the whole long app approval process & annoyed seeing the same old version.)
I had a buddy try download the latest app version, and he successfully and ran the new version... So I now must assume it is somehow my iPhone that is strange. I remove all app instances (debug, old appstore download) - then download the new version from app store. After that, my iPhone shows the "new" text on the launch icon, but still launches an old version... somehow
I've updated my app from iOS5/iPhone 4 to iOS6/iPhone5 compatible. The app was approved by the apple store and is available to download, when downloaded from the app store it crashes on start-up. However, installing the app from xcode onto devices works perfectly, I'm at a loss. I've attached a link for the crash report
any help would be most appreciated
http://pastebin.com/epgh2Jxv
Delete the app from your device completely, clean the product, then run again from xcode. I bet the problem comes out on yours too. It seems that a storyboard doesn't exist. You probably removed it by mistake but it is still existing cached in your product since Xcode doesn't actively go searching for old files to delete.