While trying to file a bug from a device, and being sent to a login form, any succesful login ends up on 502 Bad Gateway page.
2 Likes
I have seen this also.
It could be because Bugger! uses a long URL request to post its stuff.
Maybe that breaks the redirect from the Jolla login?
Recommendation for Bugger! is to have a browser open with logged in session to the Forum before submitting.
3 Likes
This trick helped indeed. Thank you.
1 Like
Added Posting via URL breaks Jolla login (502 Bad Gateway) · Issue #48 · sailfishos-chum/bugger · GitHub
but if this is indeed the cause there is little Bugger! can do about it, apart from implementing native auth and posting (similar to SFOS Forum Viewer).
Well, that’s why I posted it in the Sie Feedback section.
Why not just add an option in settings: import apikey from sfos forum app? If they have it installed and agree you’re one dconf call from posting the report directly to the forum, if key is not found, fallback on using browser/login and workarounds
1 Like
That’s one option, the other idea was to enable SFOS Forum Viewer with an OpenURL call, so it can be used for posting.
This would also open the possibility to open links to the Forum with the app.
I have some WIP branch of Forum Viewer somewhere which does this.