I am trying to publish my extension on Microsoft Edge Add-ons. I submitted my package but it failed in the certification review because of a small error in my store listings as flagged in the review report. I fixed the error but I am unsure about how to submit my package again.
What should I do to resubmit my extension?
Is there any official document that explains how to resubmit an extension that has failed once in review?
Will there be an immediate update to the extension once I resubmit or will there be another review cycle?
If your extension failed the certification process, you need to update your extension and resubmit your extension that incorporates the feedback shared in the review report.
To edit your extension, complete the following steps.
Navigate to your developer dashboard: https://learn.microsoft.com/en-us/microsoft-edge/extensions-chromium/publish/update-extension and choose the extension that failed the certification process.
Update either the extension package or the metadata incorporating the feedback received from the certification process. If you update the extension package, ensure that you increase the version in the manifest file.
After making changes, choose Save > Publish.
You could also refer to the link here for the same details: https://learn.microsoft.com/en-us/microsoft-edge/extensions-chromium/publish/update-extension#update-your-extension-on-the-microsoft-edge-add-ons-store
The above process will initiate a new review with the latest submission.
Related
How to update my app in app-store to a newer version?
Earlier, I successfully offered my app into the app-store. That's the starting point. But it's been a while, I've updated my app, and would like to offer a new release. Since a misstep in preparing the app can take a bit of time, I'd like to have the specific steps required to offer an updated release on the Apple app store.
Summary
The process of releasing a new version of an iPhone app to the Apple app store requires quite a number of steps, but not all the steps will be required, depending on whether certificates are up to date, builds are targeting required versions, if you have screen shots for the required devices, etc. Below is an example of the steps you might need to execute to put a new version into the Apple app store.
Steps
1. Versioning and Signing
Within the XCode application, update the version of your application. Also check to see that there is a valid provisioning profile. In this example, the profile is expired, so additional steps will be required. If you have a valid profile, skip the (lengthy) step 2.
2. Updating Provisioning Profile
Skip this step if you have a valid profile.
This process does not use the Automatically manage signing feature of the XCode application. Automatic signing only works if you have a physical, registered Apple device, which I do not have. So automatic signing might be easier, but is not used here in this example.
2a. Add signing certification
Here we see there are no valid signing certificates, so one is created and associated with the apple ID.
2b. Manage certificates using `developer.apple.com`
By using the Apple developer web site, we see that an old provisioning profile is expired and we also see our new distribution cert is available. We create a new distribution profile for the app store and generate a new provisioning profile, then download it.
2c. Import the new Provisioning Profile into XCode
After the creation of the new Provisioning profile on the Apple developer web site, we import the new profile into XCode. If there is a problem with no signing certificate, you might need to select (project) -- > Build Settings and searh for PROVISIONING_PROFILE and tweak that. Or turn on, then off automatically manage signing.
3. Build and Upload the Application
Here we build the application using a generic device, archive, and upload using the provisioning profile from step 2, or an earlier valid provisioning profile.
We also must wait for the automated processing to complete. An email is generated and sent by Apple.
4. Prepare Application Submission
This is where we assign a `Store Version` number, assign the build file we uploaded in step 3, and reaffirm the application meta data.
The meta data includes screen shots of the application, and Apple requires that certain screen dimensions are represented. This answer will not explore the challenges associated with the case where Apple creates an additional burden on the developer by requiring different screen shot resolutions. Instead, an reference to another post will be included: Submit iOS build update without re-uploading screen-shots and app-previews
. My conclusion for screen shots is that you can often request (through Media Manager), that screen shots you've uploaded be used on various other devices, but when new hardware is released, you'll probably need to generate new screen shots manually.
Once the meta data is complete, the version can be submitted to Apple for approval. This process requires a real person, I think, and has taken at least over night, if not longer. This answer will not address the application-specific review process, but even though the new version didn't change anything significant, you may be asked to alter things in your submission or even within your app.
steps:
in your project in xcode go to Target -> general
there you see version and build,
if your last version in app store was 1.0, now if you have made minor changes in app, new version might be 1.1 0r 1.0.1 etc, and if major app changes, version changes accordingly, i hope you understand what i am saying here
and for build, add 1 to the last build number which you used to upload app in you developer account, not the one in app store.
Now clean app, change your provision profiles and certificates accordingly for app store..
now clean build the app, and then archive the app
after archive completed, a window appear and from there,
either you can export your ipa and browse to your ipa file, use application loader to upload app or
click upload button there in window itself.. and follow steps, this might take some time
depending upon your app size.. and after app upload success, 10-15
minute time takes, to show your this uploaded build in your
developer.apple.com console.
open the developer console, go to itunes connect -> my apps -> select this app uploaded from list of app available in list
since there is already aversion of your app in appstore.. click on add version, give the version number and select the build you uploaded earlier
and then fill in necessary details and submit for review.
i might have missed a few steps, but thats the general idea.. you will figure it out.
First you have to update version of your app choose target ---> Version Like from 1.0 to 1.1.
Choose device it's Generic ios device then clean and build the project.
Make sure you have a valid Production Certificate and provisioning Profile, installed in your mac.
Go to --> Product --> Archive --> it's open archive window --> then click validate button or it's check validation, if any error occur you have to resolve it.
then it ask for Certificate and provisioning Profile - Choose correct one.
if it success then Upload to app store.
If all work done successful then build show on app store after some time.You will get a email.
So for Submit a new build go to itunes connect by login your apple account and open your app then click (+) button version or plateform
give the version name that you provide for app version and create it.
then you can change info for this version like new Updates and screen shot if you want otherwise no need to change anything.
when build your ipa is connect to your account, In Build section of this version it show a (+) button. by clicking Then you can select your build and save changes and submit to app store.
I am not able to submit my build which supports watchkit extension using xcode7.3....I recieved following error mail from itunesconnect ...
"We have discovered one or more issues with your recent delivery for "xxx Mobile". To process your delivery, the following issues must be corrected:
1) Invalid WatchKit Support - The WatchKitSupport2 folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it.
2) Invalid Executable - The executable'***.app/Watch/watchkitapp.app/PlugIns/watchkitapp Extension.appex/watchkitapp Extension' does not contain bitcode."
I am having few questions regarding submitting native apps to itunesconnect
1) In order to submit update for existing apps with watchkit extension (watchos1.0) do we need to remove our existing watchkit extension & add new seperate watchos2 target?
2) My present watchkit extension is having bundle ID as "AppBundleId.watchkitextension" which is used as provisioning profile as well...But now we have to change bunde ID to "AppleBundleId.watchkitapp.watchkitextension"..do we need to change bundle Id in our provisioning profile as well & regenerate it again?
According to apple, it should be possible to ship both 1.0 and 2.0 extensions in your app. Some people have reported trouble doing this however. If I were you I would just go to 2.0, as it's so much better, most watch users have probably already upgraded.
Yes, you will need matching provisioning profiles.
iTunes store operation failed
No eligible software found. Make sure this software is owned by your developer organization.
I get above error while validating app from xcode 6. I don't understand this error why it is coming. Can anyone help me to solve this error?
Thank you
I was able to upload by using Application Loader as suggested in iTunesConnect.
Archive your app with the distribution provisioning profile
Export the archive for distribution to somewhere you can find it again.
Download Application Loader 3.0 from iTunesConnect, if it isn't already installed.
Open Application Loader
In AppLoader, Log into the iTunesConnect account you want to release the app from
In AppLoader, Upload the archive
Not exactly painless, but it does allow you to build with an iTunes developer account and release from a different iTunesConnect ID.
I got this error while validating my app. The problem was that the developer account of which I was using the Provisioning Profile was different from that of the account that I was using to validate my app. In simple words: They were two different APPLE IDs.
You need to add the APPLE ID from which you are using the provisioning profile.
Follow the following steps to get rid of this error and add the APPLE ID:
After clicking on "Validate button" ---> Click on "View Accounts".
The following window will open. In this window click on + button as shown below.
A pop-over showing three option will be opened as shown below. Select "Add Apple ID".
A new window will be opened asking you to enter your Apple ID and password as shown below. Enter your Apple ID and password of the developer account from which you have used the provisioning profile. Then press "Add":
You will see a new Apple ID added in the list of the Apple IDs.
Close the Organizer window. ----> Archive the product again and Validate the app choosing the newly added Apple ID.
This happened to me because I had a different developer and itunesconnect accounts. Make sure you build app with your developer account and submit validation with your itunesconnect account. That worked for me.
As noted by a few others, I was able to resolve this problem by using the Application Loader rather than xCode to send the iPA file to app store. In my case, both xCode and Application loader were using the correct iTunesConnect account, but for some reason, xCode was failing on submitting this app. I could submit other apps without incident, which led me on a wild goose chase thinking the problem was app specific.
Steps to Resolution were:
Download to Application Loader from iTunesConnect Website (as of 2/18/15, it's under the Resources and Help button).
Install App Loader
From xCode, Build/Archive to create distribution package
From xCode Organizer, Export the package to a location
From App Loader, select the Exported Package IPA file and upload to App Store.
Glad to be past this one!
For me it helped to upload with the credentials of the account agent. A developer account didn´t work.
in my application this issue was coming due to of one error that's i uploaded wrong size image in ipad2x that's 152*152 by 144*144 , but some how i export the build and i uploaded it through application loader. application loader told me abt two warning after uploading the build that was not proper icon size image for ipad #2x and the other was 64 bit warning so i solved the icon problem and now i was abled to validate my app successfully with one warning still that's of 32 bit. if u had repeated the steps like you uploaded the build first from application builder than donot forgot to change build number.
Please check the application bundleID from itunesconnect & your project in Xcode.We will get this issue if our bundleID mismatch from itunesconnect & project..
I was getting same error. After some investigation, I identify the issue with bundleID. I changed the bundleId as per itunesconnect. App was validated & submitted successful in App Store.
I am about to deliver an application on the App Store with an "Ad Hoc" provisioning profile (generated from a valid certificate in the apple developer center).
I have to specify that the xcode project file was generated by "phonegap".
Never the less I archived the application from Product/archive) and moved to the following steps consisting in validating the application.
xcode fails and suggest to download identities : I did proceed but xcode failed pretending "No identities are available for signing".
"An administrator must request identities before they can be downloaded"
At this step I have the choice
+ download identities
+ import developer profile (which I don't know what it is - probably some certificate from an other machine in case i d like to used it)
First choice failed miserably as before and second is a dead end.
Any idea's what I should be doing ?
Normally I wouldn't give a link only answer but it is necessary in this case. You can't use an Ad hoc profile to deliver to the app store. You need a distribution profile.
Please follow apples steps to achieve this:
https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/SubmittingYourApp/SubmittingYourApp.html
You need to have distribution profile with iOS app store submission (which you can acquire if you are the Agent) and then upload the binary.
I keep getting this message when I refresh under Xcode organizer when it is "Checking for pending CSR..."
No iOS Distribution Certificate Found
No iOS Distribution certificate was found. However, there is already a
certificate request pending. An Agent or Admin must approve this request
before you can download your certificate.
I'm using Xcode 4.6.1. There are no certificates in the portal and no pending ones.
Thanks!
You might need to download the certificate from the portal and add it to your keychain. If there are no certificates in the portal, then you'll need to create one and upload it. Follow the instructions in the portal for this.
Well the message says it all. The cert that you requested is pending for approval. You can wait until it gets approved and download it or let xcode sync it. Option two revoke that and create another one in case the one pending does get hanging for too long.