I have read and tried all the fixed associated with releasing and app to the App Store, but I cannot find any suitable fix. I have setup an iOS developer account and created account, I have setup Xamarin to automatic provisioning but I am getting the error message "none of the currency installed provisioning profile". I have tried the following
Upgrade Xamarin and X Code
Change all Bundle Identifiers to the same
Delete all the certificates from the KeyChain
Restarted MacBook
Switched from Manual to Automatic bundles
Created a test app
Removed certificates from iOS account
Rebuild, cleaned, achieved the project several times
I just cannot resolve this problem, any help would be highly appreciated as it's driving me around the bend to release the app into the App Store.
Many thanks
You should use manual provisioning instead of automatic provisioning when releasing your app to app store.
From the official document about publishing iOS app to App Store:
https://learn.microsoft.com/en-us/xamarin/ios/deploy-test/app-distribution/app-store-distribution/publishing-to-the-app-store
In the release build steps:
Navigate to the iOS Bundle Signing tab. Make sure that Configuration
is set to Release, Platform is set to iPhone, and that Manual
Provisioning is selected.
Of course you will need to have the corresponding distribution certificate and distribution provisioning profile created in Apple Developer page.
Many thanks for the help, I managed to resolve the problem with the following setups
Update all packages
Removed x-works (it was the latest version any way)
Re-install x-works
Delete all relating certificates in Keychain
Delete any certificates, profiles etc in app development site
Re-start Xamarin and MacBook (in the end did this several times)
Log out of Apple account in Xamarin
Re-log back into the Apple account in Xamarin
Setup auto provisioning in Xamarin i..e dev, dist etc and created the appropriate certificates
Generate a certificate within keychain using iOS account details
Plugged in iPhone and rebuilt the complete project
Achieved the build
Now it connected to the App Store and released the app
I am pretty sure you don't need to do all these steps, but seems like it took it back to the start of setting up Xamarin for app releasing. One problem might have been multiple certificates in KeyChain which caused the problem.
Many thanks for all the help and support.
Afternoon all,
We have a client who recently came via our offices and installed a development version of an app we have been working on for a trip to the States to show his colleagues.
He has just gone to test it and is getting the message that '"App Name" is no longer available"' when he tries to open it. We have tested our development devices and the same build of the app here and everything is working fine.
Is there anything we can try as he does not have access to Xcode for a fresh install of the app?
We have checked the developer certs and provisioning profiles and all seem ok and in date.
Thanks a lot.
If you gave it to them via ad hoc or something, the provisioning profile has probably expired so you would need to renew that. This is a similar problem I've met before. For the IPA file providing, you could try to upload your apps to Pgyer or TestFlight and provide the installation link to customer.
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've been trying to integrate PushWoosh in my project, actually I did integrate it successfully and released apps on the appStore. Now I am planning to release very similar app but with different content. I've done the same lately and the PW was working quite fine with each new duplicated target. But recently the duplicated target causing problem. Gives this Error alert at app startup:
Title: PushWoosh Error
Description: Your provisioning profile does not have any APS entry. Please make your profile push compatible.
I made the profiles Push compatible via the Pushwoosh's auto feature and downloaded then modified profiles and used them for archiving. I'd be very thankful if you guys can point out anything that I need to look at.
[Update]
One thing worths mention that I switched computers while making replica builds. So, in the start all builds are giving the error then at the end after being frustrated I generated whole new distribution certificates for this new computer. Now, with the new certificate and stuff I got my first target pushWoosh ready but then on the the second target gave the same error as above and surprisingly the third target works well with PW. Now I am in a fix that where's what going wrong causing such random errors. Any ideas?
Thanks
Do you have the "aps-environment" string in your mobile provisioning profile? If you don't you have to recreate it in the Apple Development Portal and then make sure there is such a string in a new profile, and its' value matches the gateway you're using in PW, that is "development" for Sandbox and "production" for Production.
I just came up with a different solution to this problem that I hope will help:
My problem was that the name of my app in Xcode wasn't the same as the App ID I had manually created on the Apple Developer Portal. I have 'Automatically manage signing' turned on in Xcode, so Xcode created an App ID automatically in the Apple Developer Portal called XC com paye...
I followed the process of creating the certificates from scratch, added them to the app ID that Xcode created, and voila! It works.
Hope this helps! :-)
I trying to make a new version of my application to ad-hoc distribution.
But, unfortunately, I have a strange error:
Provisioning profile 'WL Moon' specifies the Application Identifier
'asap.WeatherApp' which doesn't match the current setting
'asap.WeatherApp'
I revoked profile, and created it again, but nothing changed.
With development profile I haven't any problems, and I can run application on my testing iPhone.
Can anybody help me?
I solved this problem myself.
I cleaned all provisioning profiles on my iPhone, from XCode Organizer. Also I restarted XCode.
I think, problem happened because I changed distribution certificate (we are added push notifications to application), and on my device was two different certificates with the same name.