GitLab releases are no longer found

[OIRNOIR]

Prerequisites

Describe the bug

After updating to the latest version of obtainium (1.3.1), some of my gitlab apps have started failing to find releases.

To Reproduce

Please complete the following information:

• Device: Pixel 8a
• OS: GrapheneOS
• Obtainium Version: 1.3.1

Additional context

This was working perfectly immediately before I updated to 1.3.1.

[ImranR98]

Could you provide examples? This is definitely due to a change in 1.3.1 that fixes another issue (I thought it might break some other use cases but wasn't sure, guess it did).

[OIRNOIR]

Could you provide examples? This is definitely due to a change in 1.3.1 that fixes another issue (I thought it might break some other use cases but wasn't sure, guess it did).

Sorry, I wrote this on my phone, where I didn't see that the "to reproduce" section I wrote was completely commented out.

Here's the example I meant to use in the original post: https://gitlab.com/coolreader-ng/lxreader

If you add it to obtainium as a new source, it says "Could not find a suitable release"

[ImranR98]

https://github.com/ImranR98/Obtainium/releases/tag/v1.3.2

[TA2DF]

I believe the reason for the problem was that GitLab servers were undergoing maintenance at that time, and therefore the content was inaccessible...
Because, at that same time, when I tried to access GitLab via a web browser, I was met with a page apologizing for a temporary outage and stating that maintenance was being performed.

[OIRNOIR]

I believe the reason for the problem was that GitLab servers were undergoing maintenance at that time, and therefore the content was inaccessible... Because, at that same time, when I tried to access GitLab via a web browser, I was met with a page apologizing for a temporary outage and stating that maintenance was being performed.

But GitLab was working fine for me at the time I reported this issue.

[ImranR98]

Try again now with 1.3.2, the issue was with file filtering and should be resolved.

[OIRNOIR]

Try again now with 1.3.2, the issue was with file filtering and should be resolved.

Yeah, 1.3.2 fixed it. I tried it but forgot to mention here. Thanks!