[JIRA] (JENKINS-61337) Debug Symbols uploads > 256meg refused.
Title: Message Title
Terry Wallace edited a comment on JENKINS-61337
Re: Debug Symbols uploads > 256meg refused.
[https://github.com/microsoft/appcenter-cli/blob/master/src/commands/crashes/lib/azure-blob-upload-helper.ts]I think that's the relevant call where its calling the azure blob storage upload under the hood.Line 20: blobService.createBlockBlobFromLocalFile(container, blob, file, { Almost looks like they are directly uploading to azure storage and sidestepping anything else.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204924.1583357801000.5954.1583362560092%40Atlassian.JIRA.
[JIRA] (JENKINS-61337) Debug Symbols uploads > 256meg refused.
Title: Message Title
Terry Wallace commented on JENKINS-61337
Re: Debug Symbols uploads > 256meg refused.
https://github.com/microsoft/appcenter-cli/blob/master/src/commands/crashes/lib/azure-blob-upload-helper.ts I think that's the relevant call where its calling the azure blob storage upload under the hood. Line 20: blobService.createBlockBlobFromLocalFile(container, blob, file, {
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204924.1583357801000.5952.1583362500160%40Atlassian.JIRA.
[JIRA] (JENKINS-61337) Debug Symbols uploads > 256meg refused.
Title: Message Title Terry Wallace created an issue Jenkins / JENKINS-61337 Debug Symbols uploads > 256meg refused. Issue Type: Bug Assignee: Mez Pahlan Components: appcenter-plugin Created: 2020-03-04 21:36 Environment: Latest Jenkins & .81 version of appcenter plugin Priority: Major Reporter: Terry Wallace So it turns out the at API endpoint exposed by Microsoft will only except dbug symbol files upto 256meg using the appcenter plugin. Ours iOS app.dSYM file recently grew to 257meg and was rejected with an error message of io.jenkins.plugins.appcenter.AppCenterException: Upload symbols to resource unsuccessful: : HTTP 413 The request body is too large and exceeds the maximum permissible limit.: RequestBodyTooLargeThe request body is too large and exceeds the maximum permissible limit. RequestId:92c2b0f6-601e-0057-308e-edc32e00 Time:2020-02-27T16:56:23.4809866Z268435456 When I inquired with MS about this they said its a limitation of the api and you would need to use the chunk upload approach to upload files larger than 256meg. I don;t know if this was known before as I can find no mention of upload size limits anywhere in their documentation and it also does not seem to affect the .app uploads just the debug symbols upload. The current work around is to stop uploading with plugin and after each build hand upload the .dSYM file through the website. (Which strangely enough does not exhibit the same problem) If you need any further info please let me know. Thanks Terry
[JIRA] (JENKINS-60171) HTTP 422 uploading Android APK artifact
Title: Message Title
Terry Wallace commented on JENKINS-60171
Re: HTTP 422 uploading Android APK artifact
Yes that fixed it. I think throwing a not into the usage instructions would be a good idea. Just something that calls out the fact when you are looking for the {owner_name}/{app_name} on appcenter that Microsoft will append a '-1' to the app_name for another app with the same name on a different platform. Probably more an issue for those of us that were migrating from HockeyApp where each app/platform had its own API key for uploading. The fact that the "-1" name addition only appears in the URL field and not on the actual site anywhere is very misleading on Microsoft's part. Thanks for all your hard work on the plugin !! In case anyone forgot to tell you how much the hundreds of people who are using it appreciate the work.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203126.1573734069000.1150.1580825160455%40Atlassian.JIRA.
[JIRA] (JENKINS-60171) HTTP 422 uploading Android APK artifact
Title: Message Title
Terry Wallace edited a comment on JENKINS-60171
Re: HTTP 422 uploading Android APK artifact
Yes that fixed it. I think throwing a not note into the usage instructions would be a good idea. Just something that calls out the fact when you are looking for the \{owner_name}/\{app_name} on appcenter that Microsoft will append a '-1' to the app_name for another app with the same name on a different platform. Probably more an issue for those of us that were migrating from HockeyApp where each app/platform had its own API key for uploading.The fact that the "-1" name addition only appears in the URL field and not on the actual site anywhere is very misleading on Microsoft's part.Thanks for all your hard work on the plugin !! In case anyone forgot to tell you how much the hundreds of people who are using it appreciate the work.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203126.1573734069000.1153.1580825160626%40Atlassian.JIRA.
[JIRA] (JENKINS-60171) HTTP 422 uploading Android APK artifact
Title: Message Title
Terry Wallace edited a comment on JENKINS-60171
Re: HTTP 422 uploading Android APK artifact
no I'm sure its not the case. Here is the jenkins script EDIT:(On reading the second link you sent..I'm not so sure.. that could indeed be the case.. Thats a terrible design on there part to use a single endpoint and change the name of the app behind the scenes on you. I'll try appending the -1 to the android uploads... makes me wonder if you made a windows universal app first would your ios be -1 and your android -2 ? ) def uploadBundleToAppCenter(bundle, appenv) { def pipeline = new com.company.jenkins.PipelineUtils(); withCredentials([string(credentialsId: 'appcenter_token_default', variable: 'APPCENTER_API_TOKEN')]) { p1 = bundle.outputPath; p2 = WORKSPACE; p3 = p1[p1.indexOf(p2)+p2.length()+1..-1]; p4 = 'client/Assets/Appconfigs/../../../' appPath = p3[p3.indexOf(p4)+p4.length()+1..-1]; dbgPath = null if (appPath.indexOf('.ipa')>0) { { dbgPath = appPath.replaceAll(/\.ipa$/, '.dSYM.zip') } //Add other tests here if need to add other debug symbols.appCenter apiToken: APPCENTER_API_TOKEN, appName: 'name_'+appenv, //currently hardcoded. UNtil rewrite. distributionGroups: bundle.hockeyapp.teams, ownerName: '*Actual owner name removed', notifyTesters: false, pathToApp: appPath, pathToDebugSymbols: dbgPath, releaseNotes: bundle.hockeyapp.releaseNotes;} } and the only thing built and passed to this is the name of the .ipa or the .apkas you can see from my earlier post it says "File found matching pattern: build/client/Dingo_google_universal_enterprise.apk"and I can browse to that file and upload to appcenter directly and it works.The P1-P4 strings are just to trim the extra long workspace paths to direct /subdirectory paths below the client.appPath is build/client/Dingo_google_universal_enterprise.apk"dbgPath = null.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60171) HTTP 422 uploading Android APK artifact
Title: Message Title
Terry Wallace commented on JENKINS-60171
Re: HTTP 422 uploading Android APK artifact
no I'm sure its not the case. Here is the jenkins script def uploadBundleToAppCenter(bundle, appenv) { def pipeline = new com.company.jenkins.PipelineUtils(); withCredentials([string(credentialsId: 'appcenter_token_default', variable: 'APPCENTER_API_TOKEN')]) { p1 = bundle.outputPath; p2 = WORKSPACE; p3 = p1[p1.indexOf(p2)+p2.length()+1..-1]; p4 = 'client/Assets/Appconfigs/../../../' appPath = p3[p3.indexOf(p4)+p4.length()+1..-1]; dbgPath = null if (appPath.indexOf('.ipa')>0) { dbgPath = appPath.replaceAll(/\.ipa$/, '.dSYM.zip') } //Add other tests here if need to add other debug symbols. appCenter apiToken: APPCENTER_API_TOKEN, appName: 'name_'+appenv, //currently hardcoded. UNtil rewrite. distributionGroups: bundle.hockeyapp.teams, ownerName: '*Actual owner name removed', notifyTesters: false, pathToApp: appPath, pathToDebugSymbols: dbgPath, releaseNotes: bundle.hockeyapp.releaseNotes; } } and the only thing built and passed to this is the name of the .ipa or the .apk as you can see from my earlier post it says "File found matching pattern: build/client/Dingo_google_universal_enterprise.apk" and I can browse to that file and upload to appcenter directly and it works. The P1-P4 strings are just to trim the extra long workspace paths to direct /subdirectory paths below the client. appPath is build/client/Dingo_google_universal_enterprise.apk" dbgPath = null.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues"
[JIRA] (JENKINS-60171) HTTP 422 uploading Android APK artifact
Title: Message Title
Terry Wallace edited a comment on JENKINS-60171
Re: HTTP 422 uploading Android APK artifact
Mez, I installed 1.81 and now get a more informational error. It seems to be complaining about the Platform. Which as far as I can see should be automatic depending on the file we upload. And these are definately .apk files. This would also explain why the iOS builds are working just fine. If you are setting a platform type in the background, how are you ascertaining the type ?Terry.SCRIPT STEPS:[Pipeline] withCredentialsMasking supported pattern matches of $APPCENTER_API_TOKEN[Pipeline] {[Pipeline] stepFile found matching pattern: build/client/Dingo_google_universal_enterprise.apkCreating an upload resource for app.Create upload resource for app successful.RESULT:io.jenkins.plugins.appcenter.AppCenterException: Upload app to resource unsuccessful: HTTP 422 Unprocessable Entity: {"status":"error","message":"Platform does not match. Expected value: iOS. Actual value: Android."} at io.jenkins.plugins.appcenter.AppCenterLogger.logFailure(AppCenterLogger.java:23) at io.jenkins.plugins.appcenter.AppCenterLogger.logFailure(AppCenterLogger.java:37) at io.jenkins.plugins.appcenter.task.internal.UploadAppToResourceTask.lambda$uploadApp$0(UploadAppToResourceTask.java:71)Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to BS MAC - VMAC-02 0872 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356) at hudson.remoting.Channel.call(Channel.java:955) at hudson.FilePath.act(FilePath.java:1159) at io.jenkins.plugins.appcenter.AppCenterRecorder.uploadToAppCenter(AppCenterRecorder.java:165) at io.jenkins.plugins.appcenter.AppCenterRecorder.perform(AppCenterRecorder.java:152) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266)Caused: java.util.concurrent.CompletionException at java.util.concurrent.CompletableFuture.encodeRelay(CompletableFuture.java:326) at java.util.concurrent.CompletableFuture.completeRelay(CompletableFuture.java:338) at java.util.concurrent.CompletableFuture.uniRelay(CompletableFuture.java:911) at java.util.concurrent.CompletableFuture$UniRelay.tryFire(CompletableFuture.java:899) at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474) at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1977) at io.jenkins.plugins.appcenter.task.internal.UploadAppToResourceTask.lambda$uploadApp$0(UploadAppToResourceTask.java:72) at java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:760) at java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:736) at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474) at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1977) at retrofit2.CompletableFutureCallAdapterFactory$BodyCallAdapter$2.onResponse(CompletableFutureCallAdapterFactory.java:81) at retrofit2.OkHttpCall$1.onResponse(OkHttpCall.java:129) at okhttp3.RealCall$AsyncCall.execute(RealCall.java:174) at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.co
[JIRA] (JENKINS-60171) HTTP 422 uploading Android APK artifact
Title: Message Title
Terry Wallace commented on JENKINS-60171
Re: HTTP 422 uploading Android APK artifact
Mez, I installed 1.81 and now get a more informational error. It seems to be complaining about the Platform. Which as far as I can see should be automatic depending on the file we upload. And these are definately .apk files. This would also explain why the iOS builds are working just fine. If you are setting a platform type in the background, how are you ascertaining the type ? Terry. SCRIPT STEPS: [Pipeline] withCredentials Masking supported pattern matches of $APPCENTER_API_TOKEN [Pipeline] { [Pipeline] step File found matching pattern: build/client/Dingo_google_universal_enterprise.apk Creating an upload resource for app. Create upload resource for app successful. RESULT: io.jenkins.plugins.appcenter.AppCenterException: Upload app to resource unsuccessful: HTTP 422 Unprocessable Entity: {"status":"error","message":"Platform does not match. Expected value: iOS. Actual value: Android."} at io.jenkins.plugins.appcenter.AppCenterLogger.logFailure(AppCenterLogger.java:23) at io.jenkins.plugins.appcenter.AppCenterLogger.logFailure(AppCenterLogger.java:37) at io.jenkins.plugins.appcenter.task.internal.UploadAppToResourceTask.lambda$uploadApp$0(UploadAppToResourceTask.java:71) Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to BS-VMAC-02 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356) at hudson.remoting.Channel.call(Channel.java:955) at hudson.FilePath.act(FilePath.java:1159) at io.jenkins.plugins.appcenter.AppCenterRecorder.uploadToAppCenter(AppCenterRecorder.java:165) at io.jenkins.plugins.appcenter.AppCenterRecorder.perform(AppCenterRecorder.java:152) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) Caused: java.util.concurrent.CompletionException at java.util.concurrent.CompletableFuture.encodeRelay(CompletableFuture.java:326) at java.util.concurrent.CompletableFuture.completeRelay(CompletableFuture.java:338) at java.util.concurrent.CompletableFuture.uniRelay(CompletableFuture.java:911) at java.util.concurrent.CompletableFuture$UniRelay.tryFire(CompletableFuture.java:899) at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474) at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1977) at io.jenkins.plugins.appcenter.task.internal.UploadAppToResourceTask.lambda$uploadApp$0(UploadAppToResourceTask.java:72) at java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:760) at java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:736) at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474) at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1977) at retrofit2.CompletableFutureCallAdapterFactory$BodyCallAdapter$2.onResponse(CompletableFutureCallAdapterFactory.java:81) at retrofit2.OkHttpCall$1.onResponse(OkHttpCall.java:129) at okhttp3.RealCall$AsyncCall.execute(RealCall.java:174) at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecut
[JIRA] (JENKINS-60171) HTTP 422 uploading Android APK artifact
Title: Message Title Terry Wallace commented on JENKINS-60171 Re: HTTP 422 uploading Android APK artifact Thanks for responding, I'll be available whenever you have time to look at it, should you need any more data point. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203126.1573734069000.9509.1580480820187%40Atlassian.JIRA.
[JIRA] (JENKINS-60171) HTTP 422 uploading Android APK artifact
Title: Message Title Terry Wallace updated an issue Jenkins / JENKINS-60171 HTTP 422 uploading Android APK artifact Change By: Terry Wallace Priority: Major Critical Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203126.1573734069000.8260.1580305380415%40Atlassian.JIRA.
[JIRA] (JENKINS-60171) HTTP 422 uploading Android APK artifact
Title: Message Title
Terry Wallace commented on JENKINS-60171
Re: HTTP 422 uploading Android APK artifact
same function is used to upload both .ipa's and .apk def uploadBundleToAppCenter(bundle, appenv) { def pipeline = new com.companyu.jenkins.PipelineUtils(); withCredentials([string(credentialsId: 'appcenter_token_default', variable: 'APPCENTER_API_TOKEN')]) { .(p3-p4 are just some string manipulation to provide a single path to file) appPath = p3[p3.indexOf(p4)+p4.length()+1..-1]; dbgPath = null if (appPath.indexOf('.ipa')>0) { dbgPath = appPath.replaceAll(/\.ipa$/, '.dSYM.zip') } appCenter apiToken: APPCENTER_API_TOKEN, appName: 'appname_'+appenv, distributionGroups: bundle.hockeyapp.teams, ownerName: '-REAL OWNER NAME--', notifyTesters: false, pathToApp: appPath, pathToDebugSymbols: dbgPath, releaseNotes: bundle.hockeyapp.releaseNotes; } }
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203126.1573734069000.7476.1580235480268%40Atlassian.JIRA.
[JIRA] (JENKINS-60171) HTTP 422 uploading Android APK artifact
Title: Message Title Terry Wallace commented on JENKINS-60171 Re: HTTP 422 uploading Android APK artifact Let me know what further information I can provide to help with this. Thanks. Running latest stable Jenkins all updated. (2.204.1) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203126.1573734069000.7472.1580235120185%40Atlassian.JIRA.
[JIRA] (JENKINS-60171) HTTP 422 uploading Android APK artifact
Title: Message Title Terry Wallace commented on JENKINS-60171 Re: HTTP 422 uploading Android APK artifact Mez, I am running into this same issue with 0.8.0 After build completes I get the following. I can directly upload the exact .apk produced to the appcenter website and it works just fine. Note this is with .APK specifically. The .ipa upload works fine. File found matching pattern: build/client/Dingo_google_universal_enterprise.apk Creating an upload resource for app. Create upload resource for app successful. Uploading app to resource. io.jenkins.plugins.appcenter.AppCenterException: Upload to AppCenter failed. at io.jenkins.plugins.appcenter.task.UploadTask.call(UploadTask.java:56) at io.jenkins.plugins.appcenter.task.UploadTask.call(UploadTask.java:17) at hudson.remoting.UserRequest.perform(UserRequest.java:211) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to BS-MAC-10952 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356) at hudson.remoting.Channel.call(Channel.java:955) at hudson.FilePath.act(FilePath.java:1159) at io.jenkins.plugins.appcenter.AppCenterRecorder.uploadToAppCenter(AppCenterRecorder.java:165) at io.jenkins.plugins.appcenter.AppCenterRecorder.perform(AppCenterRecorder.java:152) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ... 4 more Caused by: java.util.concurrent.ExecutionException: io.jenkins.plugins.appcenter.AppCenterException: Upload app to resource unsuccessful: at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357) at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895) at io.jenkins.plugins.appcenter.task.UploadTask.call(UploadTask.java:54) ... 9 more Caused by: io.jenkins.plugins.appcenter.AppCenterException: Upload app to resource unsuccessful: at io.jenkins.plugins.appcenter.AppCenterLogger.logFailure(AppCenterLogger.java:23) at io.jenkins.plugins.appcenter.task.internal.UploadAppToResourceTask.lambda$uploadApp$0(UploadAppToResourceTask.java:75) at java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:760) at java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:736) at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474) at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1977) at retrofit2.CompletableFutureCallAdapterFactory$BodyCallAdapter$2.onResponse(CompletableFutureCallAdapterFactory.java:81) at retrofit2.OkHttpCall$1.onResponse(OkHttpCall.java:129) at okhttp3.RealCall$AsyncCall.execute(RealCall.java:174) at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) ... 3 more Caused by: retrofit2.HttpException: HTTP 422 Unprocessable Entity
