AllBugsFeaturesChangelogSearchNew post
Sign in with Fluxer
Bugs

Switching to a self-hosted instance fails with a well-known response parsing error

(#1812) Bug Fixed mobile self-hosting
by Alek B | TekkNodes edited by moderator

Observed behaviour

Failed to connect with 
[error] | 13:26:33 485ms | [AccountManager] Switch failed: CheckedFromJsonException
Could not create `WellKnownFluxerResponseFeatures`.
There is a problem with "emails_enabled".
type 'Null' is not a subtype of type 'bool' in type cast

Reproduction steps

  1. update apk (Galaxy A15 5G) with app-betafcm-release.apk
  2. Try to switch accounts

Build information

Version 1.0.0, Beta 26, Channel Beta, Build 97, Android 16 (arm64), Device samsung SM-A156M, Locale en-CA, Push fcm, Flutter 3.44.4, Dart 3.12.2

Platform

Android

Details

Expected behaviour connect to self host
  1. Rex changed the status from Needs triage to Fixed

8 comments

Sign in with Fluxer to comment and vote.
Comment by @SkippTekk
RexSystem 1 vote originally by @SkippTekk on GitHub
Also would like to note. going to /.well-known/fluxer gives me a 404 on the latest self host
Permalink
Comment by @SkippTekk
RexSystem 1 vote originally by @SkippTekk on GitHub
Can confirm I am also experiencing this issue
is your self host updated
Permalink
Comment by @snappyapple632
RexSystem 1 vote originally by @snappyapple632 on GitHub
> Can confirm I am also experiencing this issue is your self host updated
Not that I know of, will it fix the issue?
Permalink
Comment by @SkippTekk
RexSystem 1 vote originally by @SkippTekk on GitHub
> > Can confirm I am also experiencing this issue > > > is your self host updated Not that I know of, will it fix the issue?
Possibly, please run 
docker compose pull
docker compose up -d
to update it IN your fluxer root directory
Permalink
Comment by @AruMoon
RexSystem 1 vote originally by @AruMoon on GitHub
Also would like to note. going to /.well-known/fluxer gives me a 404 on the latest self host
I had the same issue with my self-hosted instance and even if .well-known path served (I have added it to Caddyfile and pointed to api) issue still appears. Resetting app data fixes it
Permalink