This is fixed for me now, with https://github.com/fluxerapp/fluxer/pull/3809. My phone web browser, which "didn't actually migrate" (but whose sessions expired) now redirects to the fluxer.com origin, as expected. I can log into the feedback site again, without manually editing the URL.
based on the implementation details I would suspect that there is still a problem if the old session is not expired and you want to log into feedback.fluxer.com using a different account that has a passkey... but i don't have two accounts to test with and i don't know how to successfully construct a "legacy origin" browser state to use when reporting such an edge case, and as such i'm not actually confident it would break. at any rate, i don't feel like constructing this edge case on purpose.
despite not feeling like constructing this edge case to file a real bug report for it, i will note that the "obvious" solution to me seems to only have fluxer.com as the login domain. for some users that would mean logging them out if they didn't already migrate smoothly automatically, but that feels preferable to being unable to log in, and i feel like it might drastically simplify the code. the legacy origin should probably only host the passkey bridge and never present a full login page?
(maybe have that automagical migration dance on the login page, to prevent it from feeling like you got logged out. crucially, never allow you to enter credentials on the legacy domain unless it's specifically the passkey bridge)
Thread
Comment by sodiboo
fluxer.comorigin, as expected. I can log into the feedback site again, without manually editing the URL. based on the implementation details I would suspect that there is still a problem if the old session is not expired and you want to log intofeedback.fluxer.comusing a different account that has a passkey... but i don't have two accounts to test with and i don't know how to successfully construct a "legacy origin" browser state to use when reporting such an edge case, and as such i'm not actually confident it would break. at any rate, i don't feel like constructing this edge case on purpose.Comment by sodiboo
fluxer.comas the login domain. for some users that would mean logging them out if they didn't already migrate smoothly automatically, but that feels preferable to being unable to log in, and i feel like it might drastically simplify the code. the legacy origin should probably only host the passkey bridge and never present a full login page? (maybe have that automagical migration dance on the login page, to prevent it from feeling like you got logged out. crucially, never allow you to enter credentials on the legacy domain unless it's specifically the passkey bridge)