I want to distribute app, but I received the error. I don't know the cause.
I use Xcode Version 13.0 (13A233)
An error was Encountered:
Error Analyzing App Version (Build number request failed with error: BuildsService: ResponseErrors (1): Error status: 403, code: FORBIDDEN_ERROR, title: 'This request is forbidden for security reasons', detail: 'The API key in use does not allow this request', id: 65cc1b85-e0d4-4f86-8bab-e72d7149c9cc)
Might be temporary Apple outage. See:
https://developer.apple.com/forums/thread/705599
Here's a workaround:
Organizer -> Distribute App -> App Store Connect -> Export -> NOW DISABLE WIFI / INTERNET (else will fail) -> Exported .ipa
Now use Transporter App -> Login to same account -> Add .ipa -> Upload works !
Transporter can be downloaded here:
https://apps.apple.com/app/transporter/id1450874784
I fixed this issue by removing every Apple ID in Xcode except the one that has the developer role in App Store Connect for the app I was trying to validate / distribute. I assume Xcode was trying to use the wrong account at some point in the process.
I was able to resolve it by attempting to submit an older uploaded version and then canceling as soon as that step was completed. Then I tried to upload the new version again, surprisingly it passed that check â
. If the process fails then try to restart the mac.
Today I've faced the same problem. I tried to remove all previous versions. Then after a while I archived new version and this step successfully passed. It seems that was a problem on Apple side.
Problem at apple dev forum
Don't try to remove certificates and etc. It would bring more problems.
I got "Error Analyzing App Version" without any additional details. I just deleted the archive and create it again and it worked.
Just go to xcode preferences->accounts->Download manual profiles and try uploading again it works for me.
I am also facing the same issue from last few hours, it seemed like this issue is arising form Apple side, so doing any changes with certificates or bundle id etc may make it worst to get resolved, thought to wait if Apple respond on this thread
Solved it through Changing the app version from 1.0.0 to 1.0 on Xcode. still this is not guaranteed solution cause its not working on the other Mac.
Someone posted the following workaround on Apple's Developer Forums:
WORKING BYPASS: While Apple's Hardcore Software engineers drink coffee and figure this bug out!
Organizer -> Distribute App -> App Store Connect -> Export -> NOW DISABLE WIFI / INTERNET (else will fail) -> Exported .ipa
Now use Transporter App -> Login to same account -> Add .ipa -> Upload works !
Transporter Can be downloaded from AppStore
I managed to upload my app to TestFlight this way.
See https://developer.apple.com/forums/thread/705599?answerId=712953022#712953022
I had the same message without any description error message like below. I was trying to upload the build to Testflight and encountered this issue.
My solution is only to do with the versioning of the XCode. As I was using new Version number with a random Build number. For example Version I set as 1.2.0 and Build 17, even though I haven't uploaded Build 1 for Version 1.2.0.
After setting up Version 1.2 and Build 1, everything worked.
I changed my Apple id password and got this error.
I checked Xcode -> Preference -> Accounts and noticed that session has expired.
I re-logged in and got the same error again.
And I just restarted my Mac and it worked.
Another solution is to recreate the App Store distribution certificate and then it will work.
In Flutter, I solved it by changing the $(MARKETING_VERSION) to $(FLUTTER_BUILD_NAME) for CFBundleShortVersionString key in the Info.plist file
<key>CFBundleShortVersionString</key>
<string>$(FLUTTER_BUILD_NAME)</string>
I just had this and fixed it by signing out of Apple in XCode and then signing back in.
XCode > Preferences > Accounts > Minus (-) button at the bottom left, then plus (+) button and signed back in. Took 15secs once I tried it.
I encounter this issue suddently. I had uploaded a binary with build 0 yesterday. Then try to upload a binary with build 2 and meet 'Error Analyzing App Version'.
Instead of upload directly, I export the binary and upload it with 'Transporter' app and everything works. So strange.
In my case my apple certificate in my keychain was expired so after creating new certificate and deleting previous certificate it worked for me.
Go to Runner :
Then Go to Signing & capabilities:
Check All - Debug - Release - Profile
Team , Bundle Identifier and others information are same or Not . if not same kindly fix it . Mainly this is causing the Error.
I was able to fix this by adding a key to Info.plist: Bundle version string (short), set to $(MARKETING_VERSION).
Don't need to do anything special. As strange as it sounds, the error does not occur if you upload during the first few minutes after the top of each hour.
i just give the version number a bump, from .42 to .43,
then it all fine.
still not sure the root cause of the problem.
Related
Using Xcode beta 9 (v4), I'm trying to launch the app by clicking on the "play" button. I get a "build succeeded" but right before launching, a popup message appears in Xcode:
"iPhone has denied the launch request."
It used to work yesterday. It does work on the simulator. I've rebooted my computer, the iPhone, uninstall the app, cleaned the build. Running out of ideas.
It may be code sign issue. Make sure you're signing with developer, not distribution.
It happens using Xcode 9.x or newer.
I tracked this problem down to the "debug executable" checkbox in the product scheme (product->scheme->edit scheme->info->debug executable checkbox). I unchecked that and this stopped happening (as well as a couple other weird issues - no output in console being one).
I have a workaround:
If you change the scheme to 'Ask on Launch' it works.
In Xcode top bar
Product > Scheme > Edit Scheme > 'Info' tab > Executable: "Ask on Launch"
http://upload-images.jianshu.io/upload_images/663014-d5d182e310052664.png?imageMogr2/auto-orient/strip%7CimageView2/2/w/1240
It's slightly annoying but it works.
This issue can be resolved by unchecking Debug Executable in Edit Scheme.
After getting "denied launch request" error, do this:
Edit Scheme -> Info -> Executable -> Ask on Launch
This worked for me with adhoc profile.
The problem for me was that I was using a free developer account (simply signed in with my Apple ID). When looking at the device logs I found (bold added)
(RequestDenied); reason: "The request was denied by service delegate
(SBMainWorkspace) for reason: Security ("Unable to launch
{com.my.bundleID} because it has an invalid code signature, inadequate
entitlements or its profile has not been explicitly trusted by the
user")"
That made me realize that I needed to go into Settings -> General -> Device Management -> {My Apple ID} -> Trust
After that, everything worked as expected.
In previous versions of iOS I would encounter a dialog on my device that would tell me that this was the problem. Maybe Apple took it out for iOS 11. đ¤
Simple restarting of the iPhone helped me out.
For me issue was due to code signing the app with Ad hoc profile.
After changing the code signing to developer profile,from xcode settings general tab the above issue got resolved.
I got this issue recently and I found the solution for this crazy issue. This are the Scheme Issue to fix this issue follow following steps.
Click Edit Scheme top Navigator Tab.
Click Info on Run menu.
On Executable dropdown select "Ask on Launch" option -> Then Close and run the build once.
This solved my problem when I got this issue.
Apple Reference
Got this with Xcode 9.0 while deploying to a non-simulated iPhone 6s with iOS 10.3.
I had force-quit the app right before this arose. Otherwise, nothing had changed; all the developer signing credentials was still trusted, and the app was still marked Verified in the iPhone's Settings.
The trick that fixed it was turning the iPhone off and then turning it back on again.
Looking at my logs, it appears applicationWillTerminate was triggered a while before this happened; the instance of the app that I thought I force-quit must have been some zombie process?
The problem is that xcode 'times out' after certain seconds. The fix is to edit the scheme and ask xcode to 'wait' until the executable is launched.
In Edit Scheme, check 'Wait for executable to be launched' instead of 'Automatically'
I attentively read all answers but they don't help me. My solution:
Go to Xcode preferences, select accounts (â + ,)
Select your Apple ID, choose team and click Manage Certificates
In Pop up menu in bottom left corner click + button and select iOS Development, then click done and close popup
Try to relaunch application, now it's should fine.
It may cause with switched a wrong branch with Git, Make sure the branch you switch not too old(since it may cause code sign issue), And on the right branch if this still bothering, select the development Provisioning Profile under Signing(Debug) if u r not Automatically manage siging.
Just tick "Automatically manage signing" in General -> Signing properties of the Target. It will create Development provisioning profile for you and running on the device will work.
These simple steps helped me.
Remove your connected iPhone, iPad from the mac.
Restart your device.
Select "Automatically manage signing" in Xcode settings.
Reconnect your iPhone, iPad.
I know there are lots of answers in this thread. I've tried every one of them but none worked for me.
TLDR:
Here is the solution:
Update to xcode 11.4.1 or newer
Going through all the certificates in Keychain access I found out that all of my developer certificates has a invalid status. And, I believe that, this is the root cause of this issue. I've tried the solution here saying delete Apple Worldwide Developer Relations Intermediate Certificate and everything. But, It didn't work.
Then I came across this link. Apparently, the Apple Worldwide Developer Relations Intermediate certificate (AWDRI) is set to expire in 2023 and developer certificates or any other certificates issued after January 28, 2021 won't be using that particular AWDRI certificate. Instead of that they use a renewed certificate which is set to expire in 2030. And here comes the problem, The new renewed certificate only works in xcode versions of 11.4.1 or newer. And, I have an older version of xcode.
When I updated my xcode to latest version - 12.4 (I had to go through making space on my machine, updating macos and all) The problem went away. All my developer certificates on Keychain access are now showing valid. And, I could see two AWDRI certificates on my Keychain access one expiring on 2023 and another one in 2030.
Description from the link I shared:
The current Apple Worldwide Developer Relations Certification Intermediate Certificate (intermediate certificate) is set to expire on February 7, 2023. The renewed certificate will be used to sign new software signing certificates issued after January 28, 2021 for the Apple Developer Programs. Remaining service certificates will be updated in the future and this page will be updated to reflect additional certificate changes.
And more...
This requirement also impacts all software signing certificates generated after January 28, 2021, by developers with Personal accounts in Xcode, as well as members of the Apple Developer Program, Apple Developer Enterprise Program, and iOS University Developer Program.
The new Apple Worldwide Developer Relations Intermediate Certificate is downloaded automatically by Xcode 11.4.1 or later and is available for download on the Certificate Authority page. Confirm that the correct intermediate certificate is installed by verifying that the expiration date is set to 2030.
Also they are mentioning about an issue with older versions:
Xcode 11.4.0 and earlier may not be able to sign software using signing certificates issued by the new Apple Worldwide Developer Relations Certification Intermediate Certificate. If youâre unable to upgrade to a supporting version of macOS or Xcode on your build machine, you can build and archive your app using an earlier Xcode client and sign it for distribution using the latest release. Alternatively, you can utilize the codesign tool to sign your software using the command line.
I face this issue on Xcode 9.1
Scenario: I checked "Connect via Network" option for device. And trying to run app to this device with USB cable attached.
Fix: Simply remove USB cable and run.
I'have tried all the answers nothing worked for me,
The problem is coming form Xcode itself and has nothing to do with profiles and certificate :
Product > Scheme > Edit Scheme
In Run (Section) / info (tab) [select] the Release instead of debug as Build Configuration as follow :
It's a regression since Xcode 10.1
Config : Xcode Version 10.1 (10B61)
Iphone X / IOS 12.1.4
I had the same issue . Its a bug in Xcode 9.1. There is a trick to make it work for now. Lock your phone. Run the code. Xcode will ask to unlock the iPhone.
I just cleared the profiles with the Apple Configurator, restarted the iDevice and worked again as usual.
It's an intermittent bug in Xcode - I just stopped and started all my devices and it magically worked (after messing about for 1/2 hour)
I had upgraded MacOS overnight to 10.13.04 which obviously upset something!
Xcode 9.3, iOS 11.3 watchOS 4.3
Let me tell you a workaround which solves my problem:
Step 1: Windows > Devices and simulator.
Step 2: Unpair device.
Step 3: Reconnect device and trust.
Step 4: Run the application. BINGO.
For me this issue was related to a Manually installed Enterprise Certificate and having to use it for both development and release schemes. I had to trust the certificate on the device before it would allow the app to be launched, but it would never launch as I kept getting that denied message. Eventually, editing the scheme and setting it to wait for the app to be attached before debugging did the trick.
Open the App Groups in Capabilities, wait App... effectiveďźthen close the App Groups, it worked:
After seeing all the solutions given across web, i finally found one and here are those:
Error occurs because of it makes Runner confused about what profile to use.
You will most often get this error, when you have added new account in profile in Xcode > Targets > Signing.
You can remove this error by just using before one Profile.
There is no need to create New Users.
or you can sign in with account you are using in Profile in your iPhone (i did this!)
Happy Days :)
In case this problem occurred for you a couple of days before today, 2019-Mar-20, it is very likely related to the fact that faulty code signing certificates were issued. In that case you should be able to resolve it by just recreating the code signing certificate. This SO question already has an answer that explains you how to do so.
I'm not sure whether it's a fix, or just another workaround, but uninstalling the application from my device helped. I'm still not sure what caused it, but #MrRogers answer helped me figure it out.
For me the issue came-up because, I was using the Distribution Provisioning Profile to debug.
We cannot debug with Distribution Provisioning Profile, changing it to Development Provisioning Profile fixed the issue.
Steps: (Xcode 11.2.1)
Select Project, Under TARGETS, select the correct target.
Switch to Signing & Capabilities
Under Singing section, change the Provisioning Profile to Development profile or you can just check Automatically manage signing
None of the other answered worked -
Xcode 11+
Click Edit Scheme on the top Navigator Tab.
Launch option choose Wait for executable to be launched
You will have to run the application on your device manually but that will keep the debugger attached as for some of the other solutions debugger get detached.
Today,I also meet this question.This is my way to solve.
Xcode 9.0,iPhone 6s,Automatically manage signing with my account.
When I select "iPhone 6s",I found that there is an logo after the iPhone 6s
It's the new function of Xcode 9.0 that can run an app on the iPhone without a string connect computer(iPhone and Mac must connect the same Network).
So, I try to change this kind of connect way.
Open "Devices and Simulators"-> unselect "Connect via network"
And then, I clean, rebuild and run my project.It works!
I will be happy if this method can help you.
I'm trying to upload my app to iTunes Connect with Xcode. I chose product > archive, choose my account, it compiles and when I try to upload it hand for a long time on:
Uploading Archive
Sending API usage to iTunes Connect...
Then it shows an error message:
I've restarted Xcode and the entire machine but still it keeps repeating itself.
What's wrong here?
This usually happens to me when the phone is connected while uploading the archive, and removing the phone so far has been solving the issue for me.
My solution was to install Application Loader. At first it seemed like it's stuck as well, but after about 10 minutes it started uploading.
I solved this issue.
There is a checkbox "include bitcode" at the bottom of the Summary screen (when you validate Archive) or Send XXX to Apple screen (when you upload to App Store) where the Organizer show the Binary and Entitlements together with Provisioning Profile. In XCode 7 it is checked by default. I unchecked it and re-run Validation - worked fine. As soon as checked the checkbox back on, it started failing with same error.
I have also unchecked the other checkbox on the same screen - symbolis upload.
Successfully uploaded the binary using the Organizr just now.
Here the solution that helped in Xcode 8, summary screen:
Still getting the same error despite "unchecking" bitcode and also archiving with the bitcode under Basic Profile turned off in the info.plist.
It would only work if I used Application Loader, like this:
First, export the application Archive from Xcode's Organizer window (it saves this into a directory on the Desktop).
Then, from Xcode:
Xcode > Open Developer Tool > Application Loader
My guess is that there is a bug somewhere either with iTunes Connect back end or xCode itself.
A couple of Xcode restart didn't resolve the issue but Application Loader solved it for the very first attempt. Also, Application Loader, is more descriptive for letting one know what's going on during the whole upload process. Plus simultaneous apps upload is possible via Application Loader.
I got this error when trying to upload an app to App Store Connect (01/20/2020). Restarting Xcode fixed the issue for me.
I've had the same issue.
Tried to upload the app with Transporter with no success.
Restarting of Mac and Xcode didn't help.
Solution was to logout from Xcode and log in back
Xcode -> Preferences -> Accounts -> Select your Apple ID and click on "-" below
To submit to App Store use Application Loader but after creating the "App-Specific" password as the following:
Log in to https://appleid.apple.com and enter your 2FA (TWO-FACTOR AUTHENTICATION) code.
Then in the Security section on the bottom right area, you'll see: APP-SPECIFIC PASSWORDS.
Generate Password... Click the link to create an app-specific password, Enter your password.
Copy the app-specific password. Enter the password into the Application Loader.
Choose the exported ipa to submit it.
For developers uploading apps with Xcode: simply change network and restart your Mac.
I solved this issue with Transporter, native Apple application. You can download it from AppStore.
https://apps.apple.com/ua/app/transporter/id1450874784?mt=12
This application has a much more information about uploading process and possible errors.
Install the "Transporter" app from the MacOS app store.
From Xcode's organizer, select your archive and press "Distribute App"
Select "Export" and proceed as usual.
Choose the exported .ipa file into the transporter and press "Deliver".
I was getting the same error. Application Loader didn't work. I couldn't open any Apple Developer/Forum webpages either to find an answer there. And iTunesConnect wouldn't let me log in. I thought the site was down and I couldn't even access the Apple Status pages.
My VPN was connecting outside the US. After turning off the VPN everything returned to normal. I have been letting the VPN connect to random places around the globe, probably should keep it in my area.
In my case, The build with the same number (e.g. Version 1.0(1.6)) was already been uploaded to AppStore. I found that after logging into itunes and checked the TESTFLIGHT BUILDS -> iOS and there I saw 1.6 (Processing)
Note: 1.0 is the version number and 1.6 is build number.
Trying to submit iOS and Apple Watch OS2 extension update from ios 9.0 to 9.1. I recently updated Xcode to version 7.1 and now I'm hitting this problem without changing anything else.
iTunes store operation failed you are not authorized to use this service
What I've tried:
Removed developer account from Xcode -> added developer account back into Xcode -> Still hit the error.
I tried Xcode -> Preferences -> Apple ID -> Download All to get my latest provisioning profiles up to date. Still get the error.
Deleted all old archives, cleaned project, archive again. Still get the error.
Increased build number and version number in both the project and in itunes connect. Still get the error.
Deleted derived data in the Library -> Developer folder and I still get the error.
Cleaned the project -> Archived the project again -> Unchecked "enable bitcode" and I still receive the error.
Code Signing Settings:
Watch Target -> Provisioning profile automatic code signing iOS Developer
Watch Target Extension -> Provisioning profile automatic code signing iOS Developer
iOS Target -> Provisioning profile automatic code signing iOS Developer
Still hit the error message with the provisioning profile settings.
Reinstalled Xcode 7.1 -> Still hit the error message.
I've also confirmed that all my developer and distribution provisioning profiles are valid and downloaded.
Observations:
One thing I've noticed is that when I archive the app and look in the Window -> Organizer I notice my iOS apps on the left side for my archives. This app I'm trying to submit has no name next to it. However, if I delete all old archives for this app the app name shows up again next to the app icon. Maybe a bug with Xcode but I have no clue.
Another thing I've noticed is I've been able to successfully submit iOS archives that have no WatchKit extension using Xcode 7.1. I'm not sure if the WatchKit extension could be the problem but it is a possibility.
Also when the archive is ready to be uploaded to iTunes Connect I notice a couple of things. First, the iOS App defaults to the active provisioning profile: "MyApp" Distribution profile. However, both the WatchKit app and app extensions automatically default to the XC* wildcard provisioning profile. I'm not sure if this whole problem could just be related to a provisioning profile error but it is possible.
iOS Target -> Build Phases -> Embed Watch Content is set as:
$(CONTENTS_FOLDER_PATH)/Watch
Application Loader Submission Attempt:
Tried and failed with the following error message:
ERROR ITMS-90171 "Invalid Bundle Structure - The Binary file 'MyApp.app/Watch/MyAppWatch.app/_WatchKitStub/WK' is not permitted. Your app can't contain stand alone executables or libraries other then the CFBundleExecutable of supported bundles. Refer to the Bundle Programming Guide..."
Again, I used this exact same project structure to submit the ios app and watchkit OS2 extension on Xcode 7.0 ios 9.0.x no problem. I think the error message is inaccurate unless I'm misconfiguring something but I imagine I would've hit the error back on Xcode 7.0
Any help on how to solve this would be awesome. I've found no help googling and reading other SO posts and I've been stuck on this for far too long. Thanks!
I met the same issue today and I think it is a bug of Xcode 7.1
Finally I managed to submit my app via Application Loader. There were warnings but it did work.
Here are the basic steps:
Archive
Export
Xcode menu --> Xcode --> Open Developer Tool --> Application Loader
Double click "Deliver Your App" and choose the file exported in step #2
click next and follow the instructions until the end
I found the solution by unchecking the Include bitcode option.
In mi case, it seems that updating to Xcode 7.1 removed some account information. So, after a few attempts to upload it from Xcode, I opened Application Loader, and it asked me to login. I logged in and finally could submit to the App Store from the Organizer. Hope it helps someone.
it is the enable bitcode on the bottom when you submit the upload. uncheck the box. for some reason it comes with 2 boxes checked by default on xcode 7.1
Set team in target-> General-> Team
Check and set appropriate provisioning profile in targets/project build settings.
Try with Xcode to upload build if find same issue.
Or
Try with application loader it will work.
In my case I think it should be a xcode 7.1 bug. I re-added my account, re-generated profile, rebuild the app (restart my mac) but none of them work! I got this error when I first validated the app.
Then I created a new profile and the validation passed. But the first time uploading the app xcode still showed that error. Unwilling to give up I clicked the upload button again and this time it succeeded!
I faced the same issue then I uploaded through Application Loader from XCODE menu and it showed so many error like missing icon for iPad etc .
So please try you app to load through Application Loader and see complete detail of errors you might have in your application.
I got it working through Application Loader after fixing these issues.
I am using Xcode 7.1.1. and it appears to be an issue with Xcode, because I successfully submitted the build via Application Loader. Now, I suspect that I added too many SDKs / adapters inside the code that may have caused issues with the app's delivery. But there's no way of knowing that for sure.
During upload my API Analysis to the App Store was skipped, because it was too large, but I doubt that may caused Xcode to upload the app to the App Store.
If Xcode fails to upload, try Application Loader.
Solved for Xcode 7.2 by revoking and recreating the cert:
Image of what to click here (sorry no embed reputation)
In XCode go into this menu:
XCode -> Preferences -> Accounts
When on the accounts tab, I selected my email in the Apple Id list (on the left).
Then on the right there is a list of of teams under Team Name, select the correct Team and click on View Details.
Finally, there's a list of Signing Identities, next to "iOS Distribution" click Reset.
I didn't have to restart XCode, I just immediately resubmitted to iTunes from Organizer with no problems.
Edit: Thanks #Dover8 for the info about possible effects.
https://developer.apple.com/library/mac/documentation/IDEs/Conceptual/AppDistributionGuide/MaintainingCertificates/MaintainingCertificates.html
Resetting Certificates Using Xcode
If Xcode detects an issue with a signing identity, it displays an
appropriate action in Accounts preferences. If Xcode displays a Create
button, the signing identity doesnât exist in Member Center or on your
Mac. If Xcode displays a Reset button, the signing identity is not
usable on your Macâfor example, it is missing the private key. If you
click the Reset button, Xcode revokes and re-creates the corresponding
certificate.
Try to check your iOS Provisioning Profiles on
https://developer.apple.com/account/ios/profile/profileList.action
In my case one of profiles was marked as "Invalid" and after profile regeneration an error no longer appears
I got the same problem.
Tried to Upload To App Store.. 3-4 times.
Then I Hit the Validate... button and validation was success.
After that tried to upload again and it succeeded.
Then i cursed apple...
It seems to be related to the latest iTunesConnect update and "roles".
If I look at the "iTunesConnect Users" screen, we have three accounts,
(1) is "Admin, Legal", (2) is "Technical, Marketer", and (3) is "Technical Only".
Now when you click the email address to check the details and "roles" of #2 then only "Marketer" is checked, and only the marketer permissions are available.
For #3 the correct checkmark ( Technical ) is set, and also "Create Apps and Submit versions" is shown as an available "App feature".
It might be a work-around to change permissions to disable and re-enable "technical", or maybe give more permissions and make the person an Admin (temporary, of course).
Also - for the Jenkins users out there, you might have copied some certificates from the "login" keychain to the "system" keychain. Try removing them from the system-keychain ( I think that was this step which made my "Archive" not end up in 'not authorized ...' message and actually pass the verify again).
I have two iphone devices( 4s and 5 ) connected to my computer and i am trying to install an application in both the devices. It installs pretty well in iphone 5 but it gives an error 'The application could not be verified.' when attempted to install in the iphone 4s device.
The UDIDs of both the devices have been added in the provisioning profile generated for the application.
Also, to add a note, I have just updated my iphone version to 8.1.3 in my 4s device. I am not sure though if the error has anything to do with it.
Any help on this would be much appreciated. I have been stuck on this for some time now.
EDIT:
I just connected this to another iPhone device and the issue seems to be there again. Basically this means that the app, for some reason, installs only in the phone which I have been using for some time now and not in any other phone. Once again, I am pretty sure that the provisioning profile contains the UDIDs of all these 3 devices.
I had something similar happen to me just recently. I updated my iPhone to 8.1.3, and started getting the 'application could not be verified' error message from Xcode on an app that installed just fine on the same iOS device from the same Mac just a few days ago.
I deleted the app from the device, restarted Xcode, and the app subsequently installed on the device just fine without any error message. Not sure if deleting the app was the fix, or the problem was due to "the phase of the moon".
As I notice The application could not be verified. raise up because in your device there is already an app installed with the same bundle identifier.
I got this issue because in my device there is my app that download from App store. and i test its update Version from Xcode. And i used same identifier that is live app and my development testing app. So i just remove app-store Live app from my device and this error going to be fix.
just delete the app and try again, it happens to me when i try to launch over a device that has the same app but generated by an ipa file.
You probably used the "Fix Issue" option in Xcode when plugging in a new device. Old question but I believe this is the actual answer to WHY this is happening. When you install an app on a device it is signed with a specific development provisioning profile. If, for instance, you plug in another device that is not registered on your developer account Xcode will ask you to "fix the issue". When you press that the device is added and another provisioning profile is created/modified. If you try to overwrite an existing app you'll receive that error. Deleting the app and reinstalling it works since the profile has been altered. I find this often happens when a Team is set and a member plugs in a new device then Xcode "Fixes" the problem.
Might have figured it out... Deleting the app from the device worked for me, as others mentioned before (thanks!).
I think the reason is that the app on the device was actually signed with a separate provisioning profile, specifically a distribution profile in my case.
I faced this issue a lot. I am not sure if this is the issue, but I think, when xCode saw that there is an app with the same bundle identifier as of the app, I am trying to install, it didn't allow me. So, I had to delete the older one and attempted to install and it worked. However sometimes for testing purpose, I needed multiple version of the same app and in that case, I would change the bundle identifier and try to install. It only works if, I am using an wildcard provisioning profile.
To others not using RubyMotion and don't think that deleting the app is acceptable (as in, you want to do upgrade testing). Check out the bottom of these docs from Apple:
https://developer.apple.com/library/ios/technotes/tn2319/_index.html
It looks like they changed something in 8.1.3 to check for this new rule.
The Fix
"[Add] the installed applicationâs application-identifier value, as logged in the second parentheses, to the previous-application-identifiers entitlementâs array value for the app being installed (by resigning it or re-building it) and requesting new special provisioning profiles as shown below."
<key>previous-application-identifiers</key>
<array>
<string>{Your Old App ID Prefix}.YourApp.Bundle.ID</string>
</array>
EDIT:
In order to do this, you need special provisioning profiles. You can request these from Apple:
"To enable signing with the previous-application-identifiers entitlement new special provisioning profiles are required that can be obtained by going to the Contact US page and requesting them." (from the docs linked above).
Had the same issue on my iPad running 8.1.3 Deleting the app and installing again fixed the issue. I use two different provisioning profiles on two different machines and that could have caused this issue.
Working & tested solution, which does not require to delete application:
It looks like AppStore Distribution Provisioning Profile or just iOS Distribution certificate have special permissions and "Could not be verified..." problem does not apply to them. They will always override previous certificate.
In other words: AppStore release will install successfully, even if already installed (testing, adhoc or enterprise) app has been signed by the certificate from different team.
If you are lucky and have previously uploaded app to the AppStore account owned by the same team as in certificate you have a problem with - then things are very simple: just download & install app from AppStore.
When it installs - app certificate will be the same as the one you want to test with and problem goes away.
If your app is not on the AppStore yet - iTunesConnect beta comes to the rescue:
Disclaimer: I did not tested this but since cert an prev are the same as AppStore release, I bet it works:
Archive your app with AppStore provisioning profile (iOS Distribution cert) and upload to iTunesConnect (to the account owned by the same developer team as included in the provisioning profile not you want to run).
Invite person with the device you want to run on (yourself?) to beta test.
Download & install the app from iTunes connect beta.
Now you are able to install your testing version.
The application could not be verified" , in your device there could be already an app installed with the same bundle identifier.
So Simple solution Just delete the App & try again..
....
TL;DR answer - There is no real solution besides "delete app and reinstall".
This answer is not satisfactory for many situations, when you have an existing database that needs to not get deleted within the app.
Lukasz and plivesey are the only ones with solutions that don't require delete, but neither worked for me.
I resolved this issue by changing the Build System to legacy in xcode.
I had the same problem but the mentioned solutions above didn't work for me. Even I had no previous app on device, I got this error when deploying on my device.
How to do:
Simply, go to menu File > Project Setting, inside Share Project Settings, change Build System from "New Build System (default)" to "Lagacy Build System".
I also encountered the same issue. Deleting the app didn't work, but when I tried deleting another app which was the current one's 'parent'(I copied the whole project from the previous app, modified some urls and images, then I clicked 'Run' and saw the unhappy 'could not be verified' dialog). Seems the issue is related to provisioning and code signing and/or some configurations of the project. Very tricky.
I had changed the team but I forgot to change it in my Tests target it so it caused that. Maybe this helps someone.
Just had the same problem and I found out that the issue is with expired certificate.
My app was distributed (AdHoc) through firebase and few days ago app was working just fine.
Today I've realized that I can't install it because 'The application could not be verified'.
Finally I realized that certificate that I was using for app signing has expired 2 days ago.
You need to upload it again and you'll be able to install it.
I had the same problem. But, I realised I was using a single plist with (debug) and (release) configuration, like this.
So, I changed few things..
Keeping a separate scheme for (release).
I added a new scheme for development purposes.
Edited the new scheme > run > Build Configuration > and set it to (release)
Generated a new archive using the new scheme and voila!!..
I'm able to install on all my devices.
My case:
jailbreak'ed iPhone
Final solution:
Install tweak AppSync Unified via Cydia
to bypass signing/certificate verification
Same issue occurred for me when I was installing through link. I tried to install using different link. Then I could install the app.
I am facing an issue while submitting my app from Xcode to the App Store. I have done everything regarding my project, and its running fine on my iPhone and iPad. But when I submit my project I am facing a huge problem.
First after archive I have done the validate. Now my archive file in Organizer is showing status pass validation as well. So I believe I am at the final step of submitting the app.
I have clicked on distribute and selected submit app to app store.
After login I have selected provisioning files as well.
I am stuck here. You can see in the screenshot below. And I have never seen any
progress bar where I can see the submission progress or something like that.
Only screen I can see is:
Edited:
It was near about 1.30 hours. And internet connection is working. My ipa file is only 3.5 MB.
And last when I tried Application loader to upload the same I received the following screen as well for a long time in Authenticating with the iTunes Store... ..
What should I do now?
As I felt a serious issue on this. I believe this answer might be helpful.
After trying for around 10 to 12 hours to fix this issue and as everything else regarding my project and coding was fine enough, it became a headache for me. But after getting some valuable comments from some of the expert users of stack-overflow and after doing some more search on the internet, I have found some quality answers.
This answer helped me the most:
application loader stuck at the stage of "Authenticating with the iTunes Store"
If you are going to upload it through Application Loader and it gets stuck on "Authentication with the iTunes Store..."
or
You are going to upload it through XCode and it stucks on âYour application is being uploadedâ
Then just keep your head cool and check this first method:
Check if your firewall protection is off. If not then turn it off. It maybe blocking you to connect your computer with iTunes
Store.
Try a different internet connection. The purpose for trying a different internet connection is that your current internet connection maybe blocking a required port for connection to Apple servers.
If the above steps doesn't help you then follow this second method:
Xcode needs java runtime for uploading your apps to the App Store.
enter 'java -version' in the terminal, java version should be 1.6 .If not then download
latest compatible java only from apple download center:
http://support.apple.com/kb/DL1572?viewlocale=en_US
If this still doesn't help then follow this third method:
This method enables the application loader to use the HTTP port instead of HTTPS.
Go to
Application Loader java folder :
/Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/MacOS/itms/java/lib
Open net.properties file using any text editor application like text mate or sublime text
Change this particular line : #https.proxyPort=443 proxy port to
https.proxyPort=80
Save the file. And that's it !! You can easily upload your binary file to App
store now.
If the above methods still doesn't help then follow this fourth method: Regenerate your certificate
Goto iOS developer portal (https://developer.apple.com/membercenter).
Revoke current certificate which is used by your App for signing.
Remove current "iOS distribution provision profile" from Developer
portal.
Regenerate the iOS distribution certificate and add them in developer portal.
Regenerate "iOS distribution provision profile" for app store
distribution and download to mac.
Install it.
Try again using xcode/application loader to upload the build.
There is definitely a problem if your app stuck on "application stuck process". I suggest you to go with Application loader rather than Xcode itself as Application loader shows the activity status. You can clearly know in which step you stuck.
The most frequent issue faced is to stuck on the "Authentication with the iTunes Store..." step.
There are possible two work around which I followed and finally submitted my app to app store. You can try both. For me both worked at least once.
Method One : This method plays with proxy port to use http connection over https
Go to Application Loader java folder : /Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/MacOS/itms/java/lib
Open net.properties file with "sublime text" or "text mate"
Change "#https.proxyPort=443" proxy port to "https.proxyPort=80"
Save the file and reopen Application Loader and Try again.
Method Two : Regenerate your certificate and iOS distribution provision profile and Try to upload
Goto https://developer.apple.com/membercenter
Delete previous certificate referenced by your App for signing.
Revoke your distribution certificate and download it to your mac. And install it by double clicking it.
Delete current "iOS distribution provision profile" from Developer portal.
Regenerate "iOS distribution provision profile" for app store distribution and download to mac.
Install it by double clicking it.
Try again using application loader to upload the build.
Edit: I again got this problem while uploading new build. Both of above methods were followed but was stucking in "Authentication..". Restarted the mac book and it worked. When you restart, the previous itunesconnect connection (which you might have opened in browser prior to submit your app) are reset which allows restarted mac to easily authenticate iTunes Connect. Yesterday (jan 26, 2014) the iTunesConnect authentication step proceeded within 2 mins. Hope this helps someone who is loosing patience while stuck on authentication step.
Edit 2: Before deleting distribution Certificate, try only regenerating "iOS Distribution Provision Profile". It worked for me else you can redo as above.
I Hope this helps. All the best.
I tried all the steps from Rajan's solution; none worked. However, this threads on apple dev forum (https://forums.developer.apple.com/thread/76803) gave me the solution in my case :
Try this, it fixed it for me. Open Terminal and run:
cd ~
mv .itmstransporter/ .old_itmstransporter/
"/Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/itms/bin/iTMSTransporter"
iTMSTransporter will then update itself, then you can try uploading in XCode again.
For me, just logging out from ituneconnect website and developer.apple.com does work.And just using xcode to upload. No need to restart
I got this issue today. But finally I found it's caused by my wrong settings.
In 'Build settings' of the target, change settings "Code Signing Identity -> Release" to your production certificate, and "Provisioning Profile -> Release" to your distribution provisioning file.
Then archive and distribute it again.
You can try to cancel the upload and retry. If that does not work you may want to try the Application Loader from Apple. It essentially does the same thing, but does not resign the binary. You can download the application loader from itunes connect. See https://itunesconnect.apple.com/docs/UsingApplicationLoader.pdf (Getting Started, Page 9)
I had the same issue.
I cancelled and ran a validation check. It turned out I had written a URL Scheme incorrectly.
Xcode did not gave any errors when uploading and simply got stuck but validating gave the error.
So, try validation first. Hope this helps someone.
try this on terminal
cd ~
mv .itmstransporter/ .old_itmstransporter/
"/Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/itms/bin/iTMSTransporter"
worked for me after hours of researching
This is Happened Due to the iTMSTransporter
Try this, it fixed it for me. Open Terminal and run:
Use these commands one by one on the terminal. Hope it will help you
cd ~
mv .itmstransporter/ .old_itmstransporter/
"/Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/itms/bin/iTMSTransporter"
iTMSTransporter will then update itself, then you can try uploading in XCode again.
I met this issues many times, I tried all steps but it still not working (home network) and try other network work fine (company network).
I fixed this problem by update latest Java SE from 1.6 to 1.7 and it work like a charm
To be honest, this may not be an answer but it really worked for me.
I launched Application Loader and started submitting. While sumbitting was going on,
I launched Organiser and select Distribution over archiver in Xcode as well and started uploading concurrent.
They worked together and 2nd one completed the submission.
Just my experience.
For me the issue was that I've changed my Dev. Account at some point of time and Application Loader itself was not authorized anymore. You have to manually to go it (Xcode -> Open Developer Tools -> Application Loader) and fill in your account details
I had the same issue. I as able to fix it by:
Remove/delete all distribution certificates and provisioning profiles from my machine.
Revoke distribution certificates and delete distribution provisioning profiles from Member Centre at developer.apple.com
Create a new Distribution certificated by generating a new certificate signing request from keychain access
Create a new provisioning profile for app store distribution
Download newly created certificate and add it to keychain access
Download newly created provisioning profile and add it to xcode. OR sync from Xcode from account settings.
Try to upload again.
This is some silly issue that Apple needs to fix asap. I wasted 2 days from something as silly as this.
I had the same issue. Trying all these answers may work sometimes, but usually it takes much time and may not work at the end like in my case.
I figured out a solution which will probably work for all.
Create your .ipa file by: Product -> Arcive -> Disribute(Save for Enterprise or ...) -> Next and save .ipa at target
Xcode -> Open Developer Tool -> Application Loader -> Deliver your app -> Pick your .ipa file
Withing few minutes your app will submit to iTunes. Good luck
All i did was duplicate my Application Loader.app in /Applications and ran both Application loaders at the same time.
I had the same issue after updating Xcode5 to Xcode6. After hours of craziness, the one and only thing that helped me was to delete my account in Xcode preferences and add my account again.
Last week I had the same issue after update to Xcode7, this helped me again...
If you are running inside a virtual machine (e.g. VMWare or VirtualBox), try setting the network adapter mode from the default NAT to Bridged.
This worked for me:
Logout from iTunes portal in all the browsers.
Restart your Mac machine.
Open Application Loader
Click on your Apple Login in the Top Right corner of the Application Loader Window.
Clicking Next will succeed your authentication process.
Now, do your process as usual by clicking upon the "Deliver Your App" and following the procedure beyond that.
My problem was I forgot to change the Bundle Identifier in info settings for the target. Hope it help someone.
I had similar issue while uploading iOS apps through application loader.Then once after i opened iTunes parallel all of the sudden uploading apps was faster.Not sure if iTunes has any dependency with application loader.
None of the answers worked for me and my upload was hanging for days without any error. (my build was generated using Expo). Here's what I did to make this work:
In the apple's guideline, it says one way to upload the build is to use the Transporter.
Using the Transporter, it was able to detect and output the error.
It turns out the root cause for me was the XCode version was 9 but it has to be 10.
I hope this helps others who are struggling on this issue.