Hi, we had an issue connecting via SSO from the app today. App version 3.5 on android. connecting to 3.3.6 in production and 3.4.3 in our impending upgrade environment.
We get a 404 when the app opens a browser window to authenticate - url is /local/mobile/launch.php?service=local_mobile.
Trouble is we never got rid of local_mobile once we moved past 3.2 and it appears that now needs to be removed for the native auth to work. We removed local mobile in our 3.4 env at least at SSO now works ok there.
When we had a look at the local mobile repo we found branches for 3.3, 3.4 and 3.5 so assumed there was some reason to keep it active, but looking at it more closely it appears that's not the case. Just to clarify, is there no reason at all to keep local mobile in > 3.3 versions?
cheers
Mike