I am using Xcode 8.3.3.I have already uploaded the previous version of my app to iTunes connect, but I am facing a weird issue when trying to upload from Xcode as well as application loader.The message said that my provisioning profile is invalid.I unticked "Automatically manage signing" in general tab.Then I am receiving the following issue
Signing certificate is invalid.
Signing certificate "iPhone Distribution: ", serial number "", is not valid for code signing. It may have been revoked or expired.
Please help me solve this.I am attaching the screenshot.
try Automatic sign in. select your account in drop down that you are using in itunes connect. Than export your build for iOS Distribution and try to upload using application loader because it gives perfect error that you are facing in the upload so you can solve it.
Delete All Provisioning Profile and Clear once then download all ProvisioningProfile again and again clear and remove derived data.
then try with automatically manage signing.
Related
I put together a test app simply to test In-House distribution through our Enterprise Developer Account.
Before archiving I checked that all signing settings looked good. Debug and Release show the correct provisioning profile and certificate.
Then I ARCHIVE the app. The prompts show this:
The correct cert and provisioning profile are shown. As the archive route continues I get to this screen:
I am trying to understand why it says: Certificate "Unknown" and Profile "None"
As I then try to distribute this through our MDM solution it never installs.
My question is: when distributing in-house enterprise apps, is it correct to see Certificate "Unknown" and Profile "None"?
I have same behaviour: Apps validate and distribute fine, so I guess this is just a display issue introduced by XCode 10.1
https://forums.developer.apple.com/message/338402#
Had the same issue, only downgrade to Xcode 10.0 fixed it: download old version of Xcode here
I had the same issue and spent whole today morning on it. I set certificate and profile but it showed None for both and app installation failed. I didn't fix None showing but fixed installation failing. In my case I've just remove string "Required device capabilities" from Info.plist. May be it helps you!
Hey #zumzum i have same issue with xcode 10.1
so i try with "Application Loader" and that Work
when you have failed dialog while upload app in app-store that time there is one more option to export build , just export and try to upload same build with "Application Loader"
I click to archive my app, then export, select save for Enterprise deployment, then I choose the Development Team.
Then appears this failure error:
I tried to fix it like the other similar questions but it does not fix.
What can I do??
Thank you so much.
Download Distribution certificate locally in your keychain and then archive.
I've tried to upload application to apple store using Application Loader include Associated Domains in application entitlements but I have an error:
ERROR ITMS-90046: "Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, value 'applinks:http://XXX.internal/' for key 'com.apple.developer.associated-domains' in 'Payload/MyApp.app/MyApp' is not supported."
I use distribution certificate
I have checked to ON in Associated Domains in App Ids in apple developer
I have created provisioning profile using app ids (with enabled Associated Domains) and distribution certificate
What can be the problem? I've tried recreate of all certificates, provisioning profiles etc.
I have solved this issue.
My problem was that I wrote wrong domain name. I had before:
applinks: http://something.com
and now I have:
applinks:something.com
And it's working great.
Go to xcode preferences.Accounts. Select your developer account and double click on the team name in the right. You will see all the provisioning profiles there, select anyone and show in finder. Now delete all these files and move to trash.
Now delete your account from the xocde. Quit xcode.
Now reopen xcode and go to preferences and add your developer account. Download all profiles from here.
Now re-try to build. Let me know if it works.
For anyone else stumbling across this, the problem is actually in your app ID so just deleting your provisioning profiles won't solve anything. Here's how to fix it:
1. Login into your apple developer account
2. Choose certificates and provisioning
3. Click on App ID
4. Click on the edit button for that App ID
5. Turn off Associated Domains
6. Save
This will invalidate your existing provisioning profiles so click over to Provisioning Profiles and you'll see the little icons showing the old ones are now invalid. Delete those. Generate new ones, download those and rebuild your app.
Problem solved.
I had the same problem when check
app id Push Notifications Disabled and project ON Notifications Im off Notifcation The problem was solved
Turning Associated Domains in capabilities off and then back on solved it for me.
I have invited one TestFlight user from iTunes to test my app. The app is currently under review status. When that user tried to install the app, at the time of launching in iTunes, it throws the following error :
Could not install XXXX.
The app couldn't be installed because the developer's certificate is no longer valid. To resolve the issue, contact the developer.
Anyone can provide brief explanation what could be the reason for this and how it can be resolved.
I encountered this error because the build was signed using a provisioning profile whose certificate had been revoked.
When i checked in the developer center, the provisioning profile was marked as "Invalid".
I just clicked "Edit", selected the new developer certificate and regenerated the provisioning profile. When the new build was uploaded on testflight signed with the new provisioning profile, the error went away.
However, i do think Apple should be checking if the provisioning profile is still valid rather than developers finding it out after build is already approved by TestFlight and testers complain about this error.
It simply means that the developer account from which this app is uploaded is expired OR the development/distribution certificates of the app are expired or revoked. It can be resolved by activating the certificates of the app on apple's developer portal.
We have uploaded a version to apple-test flight and apple approved app for external testers. Now we're trying to download and is not working, got same message.
But if we run app from dev phone push notification works so P12 still valid. And distributed with old test flight process works.
We're trying to upload another version and see if works.
I try and try again until I read a comment on the apple forum:
This XC profile will be acceptable for upload, but is incompatible with Testflight
When you have to check provisioning profile, be sure any "XC" provisioning profile is selected (you can change it by clicking on the right arrow)
more details on the "goldstee" answer : https://forums.developer.apple.com/thread/18446
The error CLearly states what is wrong, your Certificate needs to be renewed, as your certificate may have expired or revoked, Try to create the Certificate again along with the provisioning profiles, and it will work fine
I had a slightly different issue which was a bit more puzzling as everything was 'valid'. I encountered the issue when I needed a production push certificate (which I already set 2-3 months before and tested!).
This is what I've done to resolve the issue:
Check xocde - both Code Signing and Provisioning Profile:
I had the correct settings (they matched what I was expecting and what I used for a previous build).
Check my apple developer account - it stated that my 'prod' profile was 'Active'
Check xcode -> prefrences -> provisioning profiles - I found the profile I could see in apple developer. It had the same expiry date too!
Wet back to my Apple Developer account, clicked on the profile, downloaded it and double clicked on it.
That fixed the problem for me.
If you encounter any issues, I suggest you check Parse guide (yes, I know they are shutting down but their doc is very good!). It covers more than just profiles but you can choose the step you are having an issue with.
In my case, I found everything is fine, both provisioning profile and certificates were valid.
What I did wrong is, I upload the build to TestFligth using Transporter app, which usually needs an .ipa for same but choose adHoc type instead of AppStore while exporting the binary in the organiser.
Which somehow allow the build to upload to TestFlight but didn't authorised to install on the user's device.
So make sure you're choosing the right option while exporting the build.
I am developing since 2 years ios Projects few are uploaded to app store.
But today I found new error while uploading app with xcode4.6.2. I have searched a lot.!
Also I realesed 1st version version of product in iTunes.
please help me to sove this problem.
And
I Revoke distributed cert. Delete provision.
create new distributed certificate and using it generate new provision,
I can see that cert in my keychain aceess.
also able to get provision on xcode with labeled Valid Profile.
The app build sucessfull without any error.
But still same error I found while uploading app on to appStore.
Solved issue... I have submitted the app from origin machine where the project was created... I don't know whether it is right ans or not.. But It works for me...
Don't revoke your certificate. generate a new certificate(distributed).
generate a new provisioning profile(distributed) using that certificate.
Remove existing provisioning profile from organiser.
Download and install certificate and provisioning profile again.
Sign your code with new provisioning profile.
Clean and build your project.
Achieve it for app store.