This is on the stone-soup instance, so is possibly related to the back-end entanglements still.
If I open profile.stone-soup.ca on my mac (using Ecosia) and login with my cosocial.ca instance, my built profile opens as expected.
If I use my phone, Safari mobile, for the same profile.stone-soup.ca profile instance and logging in with the same cosocial.ca credential, I get a new profile/empty profile.
The mobile browser has created a second profile: @johannab_cosocial_ca@profile.stone-soup.ca
My original is @johannab@profile.stone-soup.ca.
I am about to try deleting the second one as /root to see what it does ...
... after deletion: I logged out of profile.stone-soup.ca, refreshed the mobile browser, and attempted to "Login" again. The result is a "Create Your Profile" screen and the empty/second profile is re-created.
I am wondering if this is a true bug, or an as-yet-unrefined security guardrail such as not allowing an Admin/root privileged user to log in on mobile, or an artifact from testing something that allows an Admin user to duplicate themselves as a non-admin to test various things?
(Incidental finding: there is no double-check or notification when /root is about to delete a profile until AFTER the profile is deleted. It advised a Hard Delete has already happened - after. will open another issue - minor admin-tool accident potential).
This is on the stone-soup instance, so is possibly related to the back-end entanglements still.
If I open profile.stone-soup.ca on my mac (using Ecosia) and login with my cosocial.ca instance, my built profile opens as expected.
If I use my phone, Safari mobile, for the same profile.stone-soup.ca profile instance and logging in with the same cosocial.ca credential, I get a new profile/empty profile.
The mobile browser has created a second profile: @johannab_cosocial_ca@profile.stone-soup.ca
My original is @johannab@profile.stone-soup.ca.
I am about to try deleting the second one as /root to see what it does ...
... after deletion: I logged out of profile.stone-soup.ca, refreshed the mobile browser, and attempted to "Login" again. The result is a "Create Your Profile" screen and the empty/second profile is re-created.
I am wondering if this is a true bug, or an as-yet-unrefined security guardrail such as not allowing an Admin/root privileged user to log in on mobile, or an artifact from testing something that allows an Admin user to duplicate themselves as a non-admin to test various things?
(Incidental finding: there is no double-check or notification when /root is about to delete a profile until AFTER the profile is deleted. It advised a Hard Delete has already happened - after. will open another issue - minor admin-tool accident potential).