Android app: Help (?) should use the instance's marketing URL on self-hosted instances

Current problem

On a self-hosted instance, the ? (help) button in the Android app opens help.fluxer.app. In the web client on the same instance, ? opens the instance's own help page. I logged out of the instance and back in, so the instance info should have been fetched again, and the Android app still opens help.fluxer.app.

Proposed change

Let the Android app build its help links from the instance's endpoints.marketing (plus /help), the way the web client does, and fall back to help.fluxer.app when it is not set. That lets a self-hosted instance point its users to its own rules and guides instead of the general Fluxer help. This way its truly your own instance, besides. I'm not saying it should discard the help page for fluxer. But would be good to have some option or a way to set this in /admin at least.

Additional information

My instance sets endpoints.marketing to its own domain. It is in the bootstrap config of the web app's HTML and in /api/.well-known/fluxer.
In the web client, the help route is built from that endpoint. The route table has help, helpArticle and bugs entries under the marketing base, and ? leads to <marketing>/help.
The Android app does not appear to use it for this button. This is what I observe. I have not seen the app's source, so I do not know why.
The same may apply to other links that use the marketing base (terms, privacy, guidelines), but I have only tested the help button.
Related: https://github.com/orgs/fluxerapp/discussions/1071 (Fluxer Apps for self-hosted instances: are URLs hard-coded in the apps?) and https://feedback.fluxer.com/p/1951 (an in-app link that goes somewhere unexpected).
Environment: Fluxer Android app <app version>, Android <version>, self-hosted instance on the v1 images.

2 comments

RexSystem 1 vote 12d ago originally by @Yousef-Sh3ban on GitHub 1 reply Collapsed as off-topic by Rex: AI-generated reply, not a confirmation from staff.

Response (via Google Gemini): Your observation is 100% correct. The Cause: While the web client dynamically builds help routes from endpoints.marketing, the Android client currently has the help URL hardcoded (e.g., 'https://help.fluxer.app/') instead of consuming the instance's bootstrap/well-known config. Instance/Admin Settings: There is currently no setting in /admin or server-side configuration that can resolve this, as the mobile app simply does not use the marketing endpoint for that button action. Resolution: This requires an upstream fix in the mobile client repository to bind the ? action to endpoints.marketing + '/help' with the official URL as a fallback.

RexSystem 1 vote 10d ago edited originally by @vibbe on GitHub OP

Thank you @Yousef-Sh3ban for confirming.

That would be much appreciated if it could be addressed when possible, unless anyone has any objections!