-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error Status 403 #63
Comments
Set release variable System.Debug to true and redeploy, it would help with getting more detailed task log. |
I read the prerequisites and I think I did all. I already had created the app in the dev center. Before I created the bundle local on my machine and uploaded it to the dev center. I have 4 submissions so for. The app is already available through the store. The only special setting is maybe to make it only available via promo code but this should not be related to the submission process I guess. Then I started using this extension. Note: As the build does not create appxbundle I refer to msixupload in the extension now but same error. Good idea about debug, I did this now. See output:
|
Hi @pulla2908 , I have requested the help of the Store team to get more information on why you are getting a 403, since the error returned by the API doesn't provide a lot of information. While they look into this, can you help me verifying that your Azure AD application is associated with your partner center account? The logs show you are able to get an access token with the azure AD application, that means your azure AD application does exist; but the fact that the store is returning 403 when trying to create a submission makes me believe that the application is not correctly associated to the partner center account. Also make sure you assign the Azure AD Application the Manager role under the partner center account. |
H Hi @pulla2908 , I just got the information from the Store team, and they pointed out the following piece in your log:
It looks like there is a white space in the App ID, which is causing some confusion on this function. To unblock yourself, you can clean up this field in the task UI and try again, or you can use the App ID instead of the App Name. You can see your app's Id in the dev center page. EDIT Adding an example of the dev center URL overview page with the app id: |
Hi @elendil326 , thank you for your feedback. It was helpful! I changed now from App Name to App Id. App Id is in my opinion the prefered way anyway because it never changes where as a display name can change over time. By changing from App Name to App Id I could now create a new submission sucessfully. This is the good news. The bad news is that I got a timeout from the task. See output here:
If I take a look into the dev center I can see the new submission. The status is right now in verfication. Looks good in my opinion. Regarding the timeout) I thought it just creates the submission and the task ends. Further steps like verfication are not awaited from the task itself but it seems it waits for it. Regarding App Name with spaces) The 403 error does not make it clear what is the problem. Can you provide a more meaningful message here? Update: After a while the status in dev center is now publishing. It seems everything is fine so far with the submission. Update 04 March: I enabled now skip polling and the task finish succesfull. However, now I don't get feedback if any post processing steps fail or not. It would be very helpful to increase the timeout. |
Hi @pulla2908 , Thanks for your feedback and happy things are working now. The timeout you are hitting is configured by VSTS and you can control it through the task UI. Go under the Control Options section, you will see an input text for Timeout. Judging by the logs I would say the current value is 30 minutes. You can increase that value and see how it plays out. |
Hi @elendil326 I am getting 403 error any thoughts? 021-10-14T01:27:45.2237428Z Obtaining app information... |
I recently added this extension from the marketplace and try to use it now in my release pipeline. When running the task I get following error:
Any ideas how to start troubleshooting? I was not able to get it working at least once. Right now I can not distinguish if this is a bug or wrong configuration somewhere.
The text was updated successfully, but these errors were encountered: