Extension fetch failed : Gitlab

If I make an extension and make a zip file in github and then fetch it in game.project it works but I push that same extension in gitlab and then fetch the zip file(made using tags) , It does not works and shows this error :

Couldn’t install following dependencies : https://gitlab.com/arun_khatri/inappupdatedefold/-/releases/new?tag_name=v1.0.0.0_1_android

Also here is my gitlab repo

and here is the working github extension repo

The dependency should be an archive (.zip, .tar) url.
https://gitlab.com/arun_khatri/inappupdatedefold/-/archive/v1.0.0.0_1_android/inappupdatedefold-v1.0.0.0_1_android.zip

2 Likes

Thanks man . It works

Hey If the repo is private what should be done . I could not fetch the libraries if the repo is private and it shows

Couldn’t install following dependencies : https://gitlab.com/arun_khatri/inappupdatedefold/-/archive/v1.0.0.0_1_android/inappupdatedefold-v1.0.0.0_1_android.zip

You need to add an authentication token to the url:

1 Like

It’s not working for gitlab .

I added both username and accesstoken like below but is not working

https://username:acces_token@gitlab.com/arun_khatri/inappupdatedefold/-/archive/v1.0.0.0_1_android/inappupdatedefold-v1.0.0.0_1_android.zip

Did you put your GitLab username into the “username” part and did you generate an access token and put that in the “accesstoken” part?

For me on GitHub it would be something like: https://britzl:MYPRIVATETOKEN@github.com/britzl/myrepo

Yes I added both username and accesstoken

For github it works(adding github username and github accesstoken in github extension repo zip file link )

but does not work for gitlab…

Try adding ?private_token=xxxxxxxxx to the url to see if it works

Does your link work in a browser, or via curl/wget ?

it worked like this . Thanks everyone for the replies

Cool. I added GitLab instructions to the documentation: Update libraries.md · defold/doc@b3bb58c · GitHub

Just looked at it. Does ?private=personal-access-token also work or it was just your typo?

It was a typo. Thanks, fixed it.