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?
That finding by Ralf Krause is correct here: https://tracker.moodle.org/browse/MOBILE-2441?focusedCommentId=626169&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-626169.
Remove the local_mobile plugin. Then, it works all out (and the legacy app still works, too).
Hi, it certainly doesn't look like it - we totally removed in our dev environment and it fixed it and the app seems to work fine. In prod env i just disabled the moodle mobile additional features service in the settings, then connection was fine with 3.5 app via SSO. We can't see anything obvious that would be needed, it was just that the repo branch of local_mobile being updated for 3.3, 3.4 and 3.5 seemed odd if it's not needed past 3.2.
this is indeed a bug in the app, I just sent a fix to PR. We'll fix several issues we've found in the new version and release a new version during this week ASAP.
As Ralf said in the issue, right now the only workaround is to disable local_mobile, and that means you could miss some features in the app. You could try to copy the file local/mobile/launch.php from local_mobile 3.1 to your installation, but I'm not sure if it will work.
ok so you have local custom dev in your local_mobile plugin. What course format do you use on the app? sounds interesting.
I suppose my question should be - if all you have is the default local_mobile plugin with no customisations, is there any reason to keep it post 3.2? If you do have customisations can you just switch off the SSO part of it safely?
gotcha, thanks for the info.
will grab a cuppa and have a watch sometime - interesting development.