search

microsoft / google-play-vsts-extension

Visual Studio Team Services (VSTS) extension for performing continuous delivery to the Google Play store from your automated CI builds
Other
84 stars 57 forks source link

Error trying to find file main.js when the file is typescript #452

Open jymmyboi opened 4 months ago

jymmyboi commented 4 months ago

When running the Google Play - Release module we get the following error:

[error]File not found: 'C:\Agents_work_tasks\GooglePlayRelease_8cf7cac0-620b-11e5-b4cf-8565e60f4d27\4.241.0\main.js'

When doing a quick look through the code base, main.js is references in a multitude of locations but when I look for main.ts it just leads me to the file Tasks/GooglePlayReleaseV4/main.ts

We are unsure of if we configured it incorrectly on our side or whether there is an oversight into how this was setup?

ivanduplenskikh commented 4 months ago

@jymmyboi, could you please share more details about your issue. Did you install the extension on your organization? You can also double-check the completed steps to install the extension https://learn.microsoft.com/en-us/azure/devops/pipelines/ecosystems/android?view=azure-devops#install-google-play

jymmyboi commented 4 months ago

@ivanduplenskikh, we had to install the extension through the following means: https://www.donovanbrown.com/post/how-do-i-upload-a-custom-task-for-build

We then had to utilise the following solution to get it to work: https://github.com/microsoft/google-play-vsts-extension/issues/362

ivanduplenskikh commented 4 months ago

@jymmyboi, the tfx build tasks upload command is used to upload Azure Pipelines Tasks but not extensions. Could you try to install by referring to the above documentation?

jymmyboi commented 4 months ago

@ivanduplenskikh The reason we had to do it this way was due to this issue https://github.com/microsoft/google-play-vsts-extension/issues/362 when installing through the marketplace. I guess this is now turning into the same ticket as the previously mentioned ticket now.

ivanduplenskikh commented 4 months ago

@jymmyboi, do you upload it to your own Azure DevOps instance?

SybizMarc commented 4 months ago

@ivanduplenskikh I work at the same place as @jymmyboi. As stated we had the issue related to #362. I'm going to include as many details as I'm able to. If you need more please let me know:

We host our own Azure DevOps instance running version Dev18.M170.6. We are limited to TFVC and the old style drag and drop modules due to compatibility with our testing suite.

If we try to install the extension from the marketplace we get the following error: Task definition input 'rolloutToUserFraction' and Task definition input 'isDraftRelease' must belong to same group as they are dependent inputs for Task with ID '8cf7cac0-620b-11e5-b4cf-8565e60f4d27'.

If we use the steps in #362 we get the following error message. As noted, we have discovered that there is a 'main.ts' file there instead.

[error]File not found: 'C:\Agents_work_tasks\GooglePlayRelease_8cf7cac0-620b-11e5-b4cf-8565e60f4d27\4.241.0\main.js'

The agent doing the operations is on version 3.241.0

We HAVE to use a JSON Auth File for authorizing the upload because no service connection was added for 'Google'

image

Also attached is the release pipeline module for reference. Should be nothing out of the ordinary in there.

image

ivanduplenskikh commented 1 month ago

@SybizMarc, @jymmyboi, apologies for the delay in my reply. As I mentioned earlier, this approach is effective for tasks because uploading an extension as a task may result in the extension being only partially functional. The absence of a service connection you're experiencing is directly related to this. To proceed with uploading this extension as a task, you must first build the extension following the contributing instructions. Once built, you can upload it using tfx.