microsoft / code-push-vsts-extension

Visual Studio Team Services (VSTS) extension for performing continuous delivery to the CodePush service from your automated CI builds
https://marketplace.visualstudio.com/items/ms-vsclient.code-push
Other
18 stars 21 forks source link

Cannot deploy package from VSTS #28

Open GeorgiMateev opened 6 years ago

GeorgiMateev commented 6 years ago

Hello, I followed this tuturial https://docs.microsoft.com/en-us/appcenter/distribution/codepush/tutorials#automate-your-deployments-with-vsts- Automate your deployments with VSTS.

Everything works up until the task: "CodePush - Release, Description : Release an update to a CodePush app deployment"

The task fails with the message:

2018-01-25T14:36:27.2326118Z ##[section]Starting: Release update to Staging 2018-01-25T14:36:27.2330356Z ============================================================================== 2018-01-25T14:36:27.2330486Z Task : CodePush - Release 2018-01-25T14:36:27.2330590Z Description : Release an update to a CodePush app deployment 2018-01-25T14:36:27.2330706Z Version : 1.2.2 2018-01-25T14:36:27.2330801Z Author : Microsoft Corporation 2018-01-25T14:36:27.2330895Z Help : 2018-01-25T14:36:27.2331008Z ============================================================================== 2018-01-25T14:36:43.6546377Z 2018-01-25T14:36:43.6556294Z Successfully logged-in. Your session file was written to C:\Users\VssAdministrator\AppData\Local.code-push.config. You can run the code-push logout command at any time to delete this file and terminate your session. 2018-01-25T14:36:43.6556596Z 2018-01-25T14:36:43.6556740Z 2018-01-25T14:37:47.9328948Z 2018-01-25T14:37:47.9330313Z [Error] Cannot POST /apps/My-Company-Name/MyApp/deployments/Staging/release 2018-01-25T14:37:47.9337077Z 2018-01-25T14:37:47.9337340Z 2018-01-25T14:37:47.9344284Z [Error] Cannot POST /apps/My-Company-Name/MyApp/deployments/Staging/release 2018-01-25T14:37:47.9375956Z 2018-01-25T14:37:47.9378084Z 2018-01-25T14:37:47.9423199Z ##[section]Finishing: Release update to Staging

Locally from my computer I am able to release an update to the same app with the cli command:

appcenter codepush release-react -a "My-Company-Name/MyApp" -d Staging

My-Company-Name is the name of the organization in Visual Studio App Center.

I see that the React Native bundle is created in the Artifacts folder from the React Native bundle task.

Can you point me in the right direction? What could be wrong with the set up? Thank you.

itoys commented 6 years ago

Hi @GeorgiMateev Owner is redundant in App Name task definition field, in your case just use MyApp not My-Company-Name/MyApp

Thanks!

GeorgiMateev commented 6 years ago

Hello, Thanks for your reply. I removed the owner and now the error is: [Error] App "MyApp" does not exist.

itoys commented 6 years ago

It's possible if you use wrong Access Key

GeorgiMateev commented 6 years ago

Strange, In the documentation is stated to use the keys returned from:

appcenter codepush deployment list -a MyCompany/MyApp

But they don't work at all. I've copied and pasted the key for Staging. The key was different than the current one and now the error is: [Error] Invalid access key. I tested this with and without owner in the name of the app. I tried with the Production environment and key and I got the same error. I created a third environment but I'm not able to select it in the VSTS task.

From App Center -> Account Settings -> Access Tokens I created a new key and now again I have the App not found error, but at least it says I'm logged in, just like with the old key.: Successfully logged-in. Your session file was written to C:\Users\VssAdministrator\AppData\Local.code-push.config. You can run the code-push logout command at any time to delete this file and terminate your session.

itoys commented 6 years ago

Access Key - it's not a deployment key You should create token as mentioned here

$ appcenter tokens create -d "VSTS Integration"

And then paste it in the Access Key field in Release task configuration

GeorgiMateev commented 6 years ago

Nope, still no luck when I tried the above. I don't think the initial issue is related to log in and app name, because in the task it says I'm successfully logged in and it looks like it's able to find the /.

Do you guys have API call logs in your back end to see why the POST request fails? Could it be because I have dashes in the company name? (I don't believe it since it's url safe.)

Did you managed to reproduce it on your end with the exported build definitions that I gave you in the App Center chat?

Thanks.

itoys commented 6 years ago

We have a problem with "/" in app names, instant fix for you is the use of ~~ instead of / e.g.:

My-Company-Name~~MyApp

We are on the way to fix it.

Thanks

GeorgiMateev commented 6 years ago

Yep, that's it! It works fine with this fix. Thanks a lot!

DavidNorena commented 6 years ago

+1

buddhamangler commented 6 years ago

@iTOYS Clearly this is still an issue? I ran into this issue just now and luckily managed to come across this so i could solve it. This particular issue would affect anyone that converted to an organization.

alexandergoncharov-zz commented 6 years ago

Hi all ,

I'm working on it. I'll let you know about progress.