Gitlab Credential Error

[sid]

Hi.
Have been working on a project for over 3 months now, with regular Git commits.
Today it started throwing error: undefined suddenly.
Tried removing the project and cloning it again, but it won’t clone and show the same message.
When tried running with Logging, it collected below log:

[2022-05-17 17:37:30.607]  START projectsDataProvider
[2022-05-17 17:37:35.911] online version: 4.9.1
[2022-05-17 17:37:47.505] gitUrl=https://gitlab.com/xxx/xxx.git
[2022-05-17 17:37:47.507] clone repo
[2022-05-17 17:37:47.509] START getCredentials...tries=3
[2022-05-17 17:37:47.992] Trying to get credentials for https://gitlab.com/xxx/xxx.git using 
[2022-05-17 17:37:47.992] tries: 3
[2022-05-17 17:37:47.992] gitProviderName=gitlab
[2022-05-17 17:37:47.992] found access token - use it: xxxxxxxxxxxxxxxxxxxxxx
[2022-05-17 17:37:47.992] gitlab login...
[2022-05-17 17:37:48.346] Trying to get credentials for https://gitlab.com/xxx/xxx.git using 
[2022-05-17 17:37:48.346] tries: 2
[2022-05-17 17:37:48.346] gitProviderName=gitlab
[2022-05-17 17:37:48.346] found access token - use it: xxxxxxxxxxxxxxxxxxxxxxxx
[2022-05-17 17:37:48.346] gitlab login...
[2022-05-17 17:37:48.668] Trying to get credentials for https://gitlab.com/xxx/xxx.git using 
[2022-05-17 17:37:48.669] tries: 1
[2022-05-17 17:37:48.669] gitProviderName=gitlab
[2022-05-17 17:37:48.669] found access token - use it: xxxxxxxxxxxxxxxxxxxxx
[2022-05-17 17:37:48.669] gitlab login...
[2022-05-17 17:37:49.002] Trying to get credentials for https://gitlab.com/xxx/xxx.git using 
[2022-05-17 17:37:49.002] tries: 0
[2022-05-17 17:37:49.002] gitProviderName=gitlab
[2022-05-17 17:37:49.419] Invalid response 400
[2022-05-17 17:37:52.656] GOT appWindow close...

Please help. Have also tried removing Gitlab from settings & removing the Wappler app from Gitlab itself, but no luck.

[George]

Well it seems your credentials aren’t working any more.

Try to connect again to gitlab in the Wappler global options.

[sid]

Did that as well.
Removed the app from Gitlab. Then enabled the option in Wappler Global settings.
It redirected to the Gitlab URL, asked for permission.
Redirected to Wappler after approval, but then gave the same error when trying to clone the repository.

[sid]

@George Any idea how I can clear that token from Wappler? Still unable to use Git panel.

[webmaster]

I also have same problem with Git Manager, it suddenly started throwing this error: error: undefined. Not sure what is causing it as there has been no change on the project set up in Gitlab

[George]

Do you have any targets defined for your project? You should have at least one target like Development.

I just tested a gitlab project of my own and was able to fully authorize it in Wappler as well push and pull to it as much as I want without any errors.

[sid]

Yes.
Just one target actually in this particular project.

I have other projects using Gitlab as well. Some are working, some are throwing the same error.
I don’t think this has anything to do with the project configuration or anything on my end.
Becuase it just stopped working for @webmaster as well, out of the blue - same as me.

Something is broken either on Wappler’s end or the Gitlab integration or on Gitlab itself.
Gitlab works fine on SourceTree - so have been using that - but I prefer Wappler’s Git panel for regular use.

Also, this is now not allowing me to switch projects. When I move from a working project to this one, I just get the undefined error.
I have to close Wappler window and reopen to actually see the changed project.

[sid]

@George Still awaiting a resolution on this. Making it really difficult to work.
Even if my credentials are not working… how do I reset them in Wappler?
I am not seeing any issue with working on the same repository in SourceTree.

[George]

You can just toggle the gitlab setting in the Wappler’s global options and then enable it again to trigger a oath2 gitlab authorization.

No credentials are needed.

[sid]

Have done that twice. No luck.

[George]

Please restart Wappler with logging, reproduce the problem and attach the debug log. See:

How to report bugs together with the Wappler debug log

Updated for Wappler Version 5.0 and higher We have a built-in bug reporting in Wappler that auto post a topic in this forum together with the debug log. Starting from version 1.1.0 the logging isn’t available per default, so you need to restart Wappler with logging. You can do that by clicking on the Wappler’s tray icon (Windows right click) and then choose “Restart with Logging” Then reproduce your problem and choose to submit a bug report from the Wappler menu File / Submit error report … o…

After that you can try a clean install of Wappler as stated in

Reinstall Wappler from scratch

Sometimes you need to do a completely clean install of Wappler. You won’t be losing anything as Wappler is fully self containing and also your project preferences are stored in the project folders. You will only loose your projects list but you can recreate it easily later on with the “Open Existing Folder” option in the Wappler Project Manager. Here is how to do a full clean reinstall: On Windows Close Wappler and its launcher by right clicking on the tray icon and choosing Quit on Window…

[sid]

I already shared the logs in the original post.
But here is a more detailed one attached.
It shows the sequence of steps as below:

1. Open project and got to Git
2. Get undefined error after a few seconds.
3. Go to settings, disable Gitlab and apply & save.
4. Open settings again, enable Gitlab, allow Wappler in browser.
5. Return to Wappler, apply & save settings.
6. Go to Git panel and hit refresh.
7. Get undefined error again.

I would like to know if you can figure out the issue from the logs, before I do a clean install - because that should be a last resort when you can’t figure out whats wrong.

[George]

are you using gitlab with credentials in Wappler or oauth authorization from the global settings?

It seems gitlab is just returning error 400 which means some kind of authorization mixture error. Maybe you have some old credential cached?

That is why I suggested clean Wappler install to remove all older cached logins that are probably invalid.

[sid]

@George

are you using gitlab with credentials in Wappler or oauth authorization from the global settings?

Global settings.
How to use with credentials - no idea. Have always just used the Global option which does oauth.

Its weird that two different system with no connection - both have the same issue.
On checking further, I see that this problem is on repositories which have been shared by clients.
In my own repo, it works fine - I have two such repos from two different clients.
It most definitely looks like an issue from Wappler's end.

Will report back after a clean install.

[sid]

Restarting Wappler fixed it for me.

@webmaster You could try it as well.