Moodle Mobile
  1. Moodle Mobile
  2. MOBILE-141

"Moodle version must be 2.1 or greater" error message when using 2.2

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Duplicate
    • Affects Version/s: 1.1
    • Fix Version/s: 1.2
    • Component/s: Web
    • Labels:
      None
    • Affected Branches:
      MOODLE_11_STABLE
    • Fixed Branches:
      MOODLE_12_STABLE
    • Rank:
      37809

      Description

      See : http://moodle.org/mod/forum/discuss.php?d=189261

      ... The challenge is that the error message the Moodle for iPhone app is giving me states that "Moodle version must be 2.1 or greater".

      However, I'm on 2.2 latest. So the error message isn't valid.

      Can you help me to troubleshoot the problem a little more? Like is there a "debug" option I can turn on to get more information?

      I could give you a temporary login on our site if that would help.

        Activity

        Hide
        Thom Rawson added a comment -

        Also should point out that this error might be related to having a self-created certificate for the website. Most browsers give a warning before accepting these certificates and then let you proceed. I'm guessing the mobile app has no such mechanism.

        Show
        Thom Rawson added a comment - Also should point out that this error might be related to having a self-created certificate for the website. Most browsers give a warning before accepting these certificates and then let you proceed. I'm guessing the mobile app has no such mechanism.
        Hide
        Tony Barry added a comment -

        I also have this error and would like to know if a new version of the App has just been released. I have found that people who loaded the App onto their iphones several/many weeks ago where able to connect without any problems but if you download and install the app now it fails to connect to the server and tells you to upgrade your server. We are actually running 2.2. In testing we had an iphone that had an earlier installation of the app running which worked perfectly. We then deleted the App from the iphone and then re-installed it from the App store. The iphone now returns the error and does not connect. I have tried to read about this error, but logic suggests that this error may be with the App rather than server configuration in our situation. I hope this information proofs helpful as my students are eager to use the App.

        Show
        Tony Barry added a comment - I also have this error and would like to know if a new version of the App has just been released. I have found that people who loaded the App onto their iphones several/many weeks ago where able to connect without any problems but if you download and install the app now it fails to connect to the server and tells you to upgrade your server. We are actually running 2.2. In testing we had an iphone that had an earlier installation of the app running which worked perfectly. We then deleted the App from the iphone and then re-installed it from the App store. The iphone now returns the error and does not connect. I have tried to read about this error, but logic suggests that this error may be with the App rather than server configuration in our situation. I hope this information proofs helpful as my students are eager to use the App.
        Hide
        Jérôme Mouneyrac added a comment -

        This issue starts to have a lot of votes. I increase the priority.

        I think it is most of the time a Moodle/Apache settings issue. But there also could be something else.

        As suggestion, in a first step looking at resolving this issue, on this error, My Moodle should open Safari on a Moodledocs page. This page should list all the known Moodle/Apache misconfiguration, with the way to resolve it. Even thought it is an admin problem, the app user could alert the admin. I'll come back with this Moodledocs page listing later if nobody start it before me

        We could also look at displaying the debug info into the app. Should we offer (if not already possible) to the app user to see the debug info from all xmlrpc web services?

        Show
        Jérôme Mouneyrac added a comment - This issue starts to have a lot of votes. I increase the priority. I think it is most of the time a Moodle/Apache settings issue. But there also could be something else. As suggestion, in a first step looking at resolving this issue, on this error, My Moodle should open Safari on a Moodledocs page. This page should list all the known Moodle/Apache misconfiguration, with the way to resolve it. Even thought it is an admin problem, the app user could alert the admin. I'll come back with this Moodledocs page listing later if nobody start it before me We could also look at displaying the debug info into the app. Should we offer (if not already possible) to the app user to see the debug info from all xmlrpc web services?
        Hide
        Tony Barry added a comment -

        Hi Jerome,
        I am not sure if any changes have been made to the app, but our issue appears to have been resolved. I ran the tests as prescribed in the forums in relation to locating the token.php file etc and both tests returned the correct responses. Although we have not altered our server, downloading a new copy of the App now works. A point to note was that the error message regarding upgrading to the latest version of the server appeared with an incorrect site address so I am unsure how accurate the error messages may be.

        Kind Regards
        Tony

        Show
        Tony Barry added a comment - Hi Jerome, I am not sure if any changes have been made to the app, but our issue appears to have been resolved. I ran the tests as prescribed in the forums in relation to locating the token.php file etc and both tests returned the correct responses. Although we have not altered our server, downloading a new copy of the App now works. A point to note was that the error message regarding upgrading to the latest version of the server appeared with an incorrect site address so I am unsure how accurate the error messages may be. Kind Regards Tony
        Hide
        Jérôme Mouneyrac added a comment -

        Thanks Tony, it's good to know that the app is running well for you now.

        I think the best way it to add a third "Help" button to the alert error message. (button opens Safari on the Moodledocs).

        Show
        Jérôme Mouneyrac added a comment - Thanks Tony, it's good to know that the app is running well for you now. I think the best way it to add a third "Help" button to the alert error message. (button opens Safari on the Moodledocs).
        Hide
        Chris O'Kelly added a comment -

        Hey, just thought I would clock in to say we are also experiencing this issue. We have 2.2.2 (Build: 20120312), authenticated by ldap and using a self signed SSL Cert while we are in development. All connections are made locally (eg https://ourdomain.local/moodle/). I see a few people refer to a fix with a token.php file, but the forum post linked doesn't seem to mention it, unless I am missing something. Is anyone able to clue me in on this and I'll give it a swing?

        Show
        Chris O'Kelly added a comment - Hey, just thought I would clock in to say we are also experiencing this issue. We have 2.2.2 (Build: 20120312), authenticated by ldap and using a self signed SSL Cert while we are in development. All connections are made locally (eg https://ourdomain.local/moodle/ ). I see a few people refer to a fix with a token.php file, but the forum post linked doesn't seem to mention it, unless I am missing something. Is anyone able to clue me in on this and I'll give it a swing?
        Hide
        Jérôme Mouneyrac added a comment - - edited

        Hi,
        this error could happen for multiple reasons. I think we should do the following:
        a) the app should get the errorcode from the returned moodle_exception and display a specific error message to the user following the exception errorcode. We need to check if the define('AJAX_SCRIPT', true); which transform the exception in JSON do keep the errorcode information.
        b) when an information is too private, the moodle_exception from token.php should send detail information in the debuginfo. And in this case we should add some debug mode on the app to display debuginfo coming from token.php, and even from web service exception. I don't think it really concerns this issue as no debug info seem to be returned, but it would be really good to implement this!
        c) finally it's more likely that CAS auth doesn't work yet (I think there is another issue about that).
        d) we could change the current string to: "The Moodle site is not reachable or it's version is lower than 2.1".
        e) the app could offer a button Help when displaying the warning. This Help button would open a Moodledocs page that explain what are the steps to do to resolve the issue. This Moodledocs page must be exhaustive and must completed everytime we find a new cause of failure.
        f) check about unvalid certificate as mentioned in a previous comment.

        I increase the priority to blocker, it should be one of the first issue that should be fixed. Causing a lot of bad ratings.

        Show
        Jérôme Mouneyrac added a comment - - edited Hi, this error could happen for multiple reasons. I think we should do the following: a) the app should get the errorcode from the returned moodle_exception and display a specific error message to the user following the exception errorcode. We need to check if the define('AJAX_SCRIPT', true); which transform the exception in JSON do keep the errorcode information. b) when an information is too private, the moodle_exception from token.php should send detail information in the debuginfo. And in this case we should add some debug mode on the app to display debuginfo coming from token.php, and even from web service exception. I don't think it really concerns this issue as no debug info seem to be returned, but it would be really good to implement this! c) finally it's more likely that CAS auth doesn't work yet (I think there is another issue about that). d) we could change the current string to: "The Moodle site is not reachable or it's version is lower than 2.1". e) the app could offer a button Help when displaying the warning. This Help button would open a Moodledocs page that explain what are the steps to do to resolve the issue. This Moodledocs page must be exhaustive and must completed everytime we find a new cause of failure. f) check about unvalid certificate as mentioned in a previous comment. I increase the priority to blocker, it should be one of the first issue that should be fixed. Causing a lot of bad ratings.
        Hide
        Jérôme Mouneyrac added a comment - - edited

        I re-read my last comment. Since "My moodle" got obsolete, I think here is the situation for "Moodle Mobile":

        a) is related to http://tracker.moodle.org/browse/MDL-29805. You can ignore it.
        b) not related. You can ignore it .
        c) CAS auth need to be tested. New issue: MOBILE-113
        d) may be good to be updated. See MOBILE-193
        e) may be good to implement. New issue: MOBILE-193
        f) worth to test what's happen when ssl certificate is invalid. New issue: MOBILE-194

        Juan I assign this issue to you, you can decide what's the best for Moodle Mobile. Cheers.

        Show
        Jérôme Mouneyrac added a comment - - edited I re-read my last comment. Since "My moodle" got obsolete, I think here is the situation for "Moodle Mobile": a) is related to http://tracker.moodle.org/browse/MDL-29805 . You can ignore it. b) not related. You can ignore it . c) CAS auth need to be tested. New issue: MOBILE-113 d) may be good to be updated. See MOBILE-193 e) may be good to implement. New issue: MOBILE-193 f) worth to test what's happen when ssl certificate is invalid. New issue: MOBILE-194 Juan I assign this issue to you, you can decide what's the best for Moodle Mobile. Cheers.
        Hide
        Jérôme Mouneyrac added a comment -

        I created multiple issues from the last comment. I'm closing this one.

        Show
        Jérôme Mouneyrac added a comment - I created multiple issues from the last comment. I'm closing this one.

          People

          • Votes:
            18 Vote for this issue
            Watchers:
            13 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development