I want to pre-populate and hide the Moodle site URL, so that users in my institution do not need to type in the URL themselves. I use the method that Moodle developer recommended in another post (https://moodle.org/mod/forum/discuss.php?d=318362). Then I make the changes to the original code of Moodle mobile from Github (https://github.com/moodlehq/moodlemobile-phonegapbuild/tree/master).
The methods I use is the following:
However, after adding the changes, some of the functions are lost until cleaning the cache in the mobile app. For example, “Chat”, “Choice”, and LTI activities (Pearson activity and webPA activity) are not integrated with the mobile app before cleaning the cache. As can be seen in the screen shots, users still need to go to Moodle site to access these activities. In addition, the new feature of course searching function released in Moodle mobile 2.4 is not shown either.
However, after cleaning the cache by clicking into “App settings” —> “Space Usage” and delete cache, and then synchronize the content again, all the features are shown. I tried both the simple and the complex way recommended in the post. And they all behave the same.
After clean the cache, the new features are shown.
I believe for most of the institutions who use Moodle mobile app, they only have one Moodle site. As a result, predefining and hiding the Moodle URL for their users is an essential function for many institutions. However, when they have done this, the mobile app gets a bug that the new features of the app cannot be shown unless users frequently clean the cache. In my understanding, developing new features seems not that important until this bug is fixed, otherwise many mobile app users cannot see the new features easily. Also this bug makes the app looks quite unstable since some functions often disappear.
As Juan mentioned in the post (https://moodle.org/mod/forum/discuss.php?d=318362), making a pre-populating function is in the short plan. I wondered when this bug can be fixed. Since I am going to release the mobile app in my institution, I wondered when this bug can be fixed so that I can decided whether I should wait it to be fixed.