Hi Bill
I don't know quite at what version of iOS this started occurring but I have noticed an annoying bug that's certainly present in iOS v11.3.x (iPhone only) where, if the SCORM debugger that Moodle/Totara has is enabled, I can't – initially - get it to launch the course at all.
When happens is that Safari prompts you to allow the debugger window to open - but then if you switch back to the main window to get the other prompt (which annoyingly you have to do now since Apple changed the way the allow/block prompts appear) my iPhone just doesn't show it; my iPad, however, does!
If you then leave the debugger window open then try reloading the other page, the course window opens fine and loads no problem – presumably because with the course debugger window already open it only needs to display one allow/block prompt this time.
I've just tried a few Adapt courses on Totara and - when the SCORM debugger is switched off - I haven't had any issues and certainly haven't seen any 'could not connect to LMS' issues - though I am using a relatively old version of Totara (2.9.12)
One thing I have noticed in the past is that occasionally when you use the 'click here to launch this course manually' link (rather than the Enter button) you get a 'could not connect to LMS' error... I think the last time I investigated this it seemed that Moodle/Totara was not actually making the LMS API available at the point the course was loaded and started looking for it. Whenever this happened I noticed that Moodle/Totara would include a sort of weird countdown message in the course window prior to actually going to the course content. Typically, I can't replicate it now despite following the same steps!