MoodleDocs - User contributions [en]

Moodle app security

2026-05-08T11:08:31Z

Jleyva: /* Warnings typically raised by static code or AI analysis tools */

{{Mobile}}

The Moodle app is a hybrid app (uses web-technologies) developed on top of a well-tested widely used framework called "Cordova" that provides a robust container for HTML apps.

Security is very important to us, this is why we follow the OWASP principles, Cordova and Moodle security recommendations, we also run AI-driven security reviews with customised prompts for our particular context.
* Cordova: https://cordova.apache.org/docs/en/latest/guide/appdev/security/
* Moodle: https://docs.moodle.org/dev/Security (when developing Web Services)

== How we approach security ==

* Login and authorisation
** Authorisation is done via temporary access tokens. The duration of the access tokens can be configured via Moodle settings.
** Single Sign-On (or auto-login) from the app to the site is done using a special private token (that is obtained and stored when the user log-in with the app)
** Single Sign-On (or auto-login) from the app to the site has several additional restrictions (like limiting it in only several times per hour)
** QR-Login is done using temporary tokens that require the user to be in the same network (IP address) and it is limited to 10 minutes time
** For retrieving files from the server (images or other assets), a different non-authentication token is used.

* Permissions
** The app only has access to a subset of Moodle functionalities (available through the Moodle App Service)
** Privileges escalation is not possible via the Web Services layer since all the operations are done in a non-privileged way, permissions are checked based on the currently authenticated user.
** Even if a temporary access token for an admin (or privileged user) was hijacked, it wouldn't be possible for the attacker to access to site administration functionality via the Moodle site.

Because the app is a Webservices client we recommend to enable it only under https and use the following settings to enforce security like:
* Enable only certain roles to be able to access via the app via system capabilities (avoid site administrators)
* Use Moodle security settings to reduce the expiration time of WebService access tokens (so the user has to authenticate again)
* Apart from that, the Cordova framework enforces security adding restrictions like avoiding connecting to sites running non-trusted certificates.

== What is the Moodle app security issues process? ==

* We follow the standard Moodle security process: https://docs.moodle.org/dev/Moodle_security_procedures
* There is only one relevant difference: security patches are applied immediately in the next app release or in an emergency release (depending the risks attached to the issue)

== Shared responsibility ==

* The organisation hosting the Moodle site is also responsible for providing secure access to the Moodle site, the site should be configured to use HTTPS (secure connection) so the connection is app-to-site encrypted.
* Apart from the previous, the Moodle site administrator can enable additional security measures such as enforcing end-to-end encryption for Push notifications via the site administration notification settings.

== Do you run security/penetration/pentest or static code analysis tests? ==

We periodically run AI-driven security reviews with different models and prompts.

We also receive automated vulnerability reports of this nature. The issue with automated tools is that they usually output generic results that indicate where an exploit may be possible, which means the results often contain many false positives.

As mentioned above our app is built on top of Cordova, we rely on the Cordova framework developers to detect any native code issue.

You can do a search in the Cordova project tracker to see that several runs with the Static Code Analysis Veracode tool created issues that have been already solved, see: https://issues.apache.org/jira/issues/?jql=project%20%3D%20CB%20AND%20text%20~%20%22veracode%22%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC

Unfortunately, those Veracode runs are not publicly available because most of the time are run by external parties using the framework.

Please, note also that there are CVE codes for Cordova security issues: https://www.cvedetails.com/product/27153/Apache-Cordova.html?vendor_id=4

== Warnings typically raised by static code or AI analysis tools ==

* '''Lack of Jailbreak Detection''' The Moodle app does not include jailbreak or root detection. This is due to the lack of official APIs from Google or Apple, and our testing of existing non-official plugins to support it showed a high rate of false positives, particularly on Android with budget devices or recent iOS updates. Notably, the app securely stores authentication tokens in the keystore/keychain, not in the session. The session token is used only for temporary content retrieval and has limited validity, ensuring that even on compromised devices, attackers cannot extract sensitive data to perform impersonation attacks.
* '''No Certificate Pinning''' The Moodle app does not support certificate pinning because it is designed to connect to any Moodle site globally (there are hundreds of thousands of sites, each one with its own URL, using Moodle), whether hosted on HTTPS, HTTP, or local networks. Additionally, the Cordova framework we rely on does not natively support certificate pinning.
* '''Lack of Encryption for Manifest Files''' The app does not include sensitive keys or certificates in publicly accessible files, eliminating the need for encryption of manifest files. The Firebase certificates available in the app’s GitHub repository are bound to the app’s fingerprint, ensuring they cannot be exploited.
* '''Static Web Service Authentication Tokens (Session Fixation)''' Web service tokens are not regenerated with each login by design. This aligns with how the Moodle Web Services API operates, allowing users to connect across multiple devices (e.g., phone and tablet) without invalidating tokens. Regenerating tokens would restrict multi-device access.
* '''Lack of Code Obfuscation''' The Moodle app code is open source. Since no keys or private data are generated during compilation, code obfuscation is not necessary.
* '''cleartextTrafficPermitted set to true''' The Moodle app allows connecting to any Moodle site, no matter if it uses SSL or not. This setting is required to allow connecting to http sites (for example in local networks).
* '''Content-Security-Policy is very permissive''' The Moodle app allows connecting to any Moodle site, so the CSP cannot be pinned to a list of URLs. unsafe-eval is required to allow running the Javascript code of Moodle plugins adapted to the app. unsafe-inline is needed because user generated content can include inline styles.
* '''Use of eval''' The app uses ''eval'' to dynamically run Javascript code from plugins that have been adapted to the app. In the future this will probably be replaced by "new Function()" to improve scope isolation, but it will still be dynamic code execution. eval is used only for running trusted code (plugins installed by site administrators on the Moodle site).
* '''Use of Math.random or MD5 for SSO passports:''' The app this functions for generating one-use temporary ids just to identify the device from a SSO was launched from, but it does not have any security implication, tampering or capturing those temporary ids don't have any security implications.
* '''Improper Session Timeout & Logout Function''' The Moodle app follows a common approach used by most mobile apps on Android and iOS, where users are not prompted to log in repeatedly after short periods of inactivity. Mobile devices provide adequate protection through features such as automatic locking when inactive. However, Moodle site administrators have full control over how the app handles session timeouts and logout behavior. They can:
** Define how the logout function works (soft logout or complete session termination).
** Set a custom session timeout duration.
** Configure the duration of the Web Service authentication token.

These configurations can be managed through:
** '''Site administration > Mobile app authentication settings'''
** '''Site administration > Security settings'''

[[es:Seguridad de Moodle app]]

Moodle app security

2026-05-08T08:05:57Z

Jleyva:

{{Mobile}}

The Moodle app is a hybrid app (uses web-technologies) developed on top of a well-tested widely used framework called "Cordova" that provides a robust container for HTML apps.

Security is very important to us, this is why we follow the OWASP principles, Cordova and Moodle security recommendations, we also run AI-driven security reviews with customised prompts for our particular context.
* Cordova: https://cordova.apache.org/docs/en/latest/guide/appdev/security/
* Moodle: https://docs.moodle.org/dev/Security (when developing Web Services)

== How we approach security ==

* Login and authorisation
** Authorisation is done via temporary access tokens. The duration of the access tokens can be configured via Moodle settings.
** Single Sign-On (or auto-login) from the app to the site is done using a special private token (that is obtained and stored when the user log-in with the app)
** Single Sign-On (or auto-login) from the app to the site has several additional restrictions (like limiting it in only several times per hour)
** QR-Login is done using temporary tokens that require the user to be in the same network (IP address) and it is limited to 10 minutes time
** For retrieving files from the server (images or other assets), a different non-authentication token is used.

* Permissions
** The app only has access to a subset of Moodle functionalities (available through the Moodle App Service)
** Privileges escalation is not possible via the Web Services layer since all the operations are done in a non-privileged way, permissions are checked based on the currently authenticated user.
** Even if a temporary access token for an admin (or privileged user) was hijacked, it wouldn't be possible for the attacker to access to site administration functionality via the Moodle site.

Because the app is a Webservices client we recommend to enable it only under https and use the following settings to enforce security like:
* Enable only certain roles to be able to access via the app via system capabilities (avoid site administrators)
* Use Moodle security settings to reduce the expiration time of WebService access tokens (so the user has to authenticate again)
* Apart from that, the Cordova framework enforces security adding restrictions like avoiding connecting to sites running non-trusted certificates.

== What is the Moodle app security issues process? ==

* We follow the standard Moodle security process: https://docs.moodle.org/dev/Moodle_security_procedures
* There is only one relevant difference: security patches are applied immediately in the next app release or in an emergency release (depending the risks attached to the issue)

== Shared responsibility ==

* The organisation hosting the Moodle site is also responsible for providing secure access to the Moodle site, the site should be configured to use HTTPS (secure connection) so the connection is app-to-site encrypted.
* Apart from the previous, the Moodle site administrator can enable additional security measures such as enforcing end-to-end encryption for Push notifications via the site administration notification settings.

== Do you run security/penetration/pentest or static code analysis tests? ==

We periodically run AI-driven security reviews with different models and prompts.

We also receive automated vulnerability reports of this nature. The issue with automated tools is that they usually output generic results that indicate where an exploit may be possible, which means the results often contain many false positives.

As mentioned above our app is built on top of Cordova, we rely on the Cordova framework developers to detect any native code issue.

You can do a search in the Cordova project tracker to see that several runs with the Static Code Analysis Veracode tool created issues that have been already solved, see: https://issues.apache.org/jira/issues/?jql=project%20%3D%20CB%20AND%20text%20~%20%22veracode%22%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC

Unfortunately, those Veracode runs are not publicly available because most of the time are run by external parties using the framework.

Please, note also that there are CVE codes for Cordova security issues: https://www.cvedetails.com/product/27153/Apache-Cordova.html?vendor_id=4

== Warnings typically raised by static code or AI analysis tools ==

* '''Lack of Jailbreak Detection''' The Moodle app does not include jailbreak or root detection. This is due to the lack of official APIs from Google or Apple, and our testing of existing non-official plugins to support it showed a high rate of false positives, particularly on Android with budget devices or recent iOS updates. Notably, the app securely stores authentication tokens in the keystore/keychain, not in the session. The session token is used only for temporary content retrieval and has limited validity, ensuring that even on compromised devices, attackers cannot extract sensitive data to perform impersonation attacks.
* '''No Certificate Pinning''' The Moodle app does not support certificate pinning because it is designed to connect to any Moodle site globally (there are hundreds of thousands of sites, each one with its own URL, using Moodle), whether hosted on HTTPS, HTTP, or local networks. Additionally, the Cordova framework we rely on does not natively support certificate pinning.
* '''Lack of Encryption for Manifest Files''' The app does not include sensitive keys or certificates in publicly accessible files, eliminating the need for encryption of manifest files. The Firebase certificates available in the app’s GitHub repository are bound to the app’s fingerprint, ensuring they cannot be exploited.
* '''Static Web Service Authentication Tokens (Session Fixation)''' Web service tokens are not regenerated with each login by design. This aligns with how the Moodle Web Services API operates, allowing users to connect across multiple devices (e.g., phone and tablet) without invalidating tokens. Regenerating tokens would restrict multi-device access.
* '''Lack of Code Obfuscation''' The Moodle app code is open source. Since no keys or private data are generated during compilation, code obfuscation is not necessary.
* '''Improper Session Timeout & Logout Function''' The Moodle app follows a common approach used by most mobile apps on Android and iOS, where users are not prompted to log in repeatedly after short periods of inactivity. Mobile devices provide adequate protection through features such as automatic locking when inactive. However, Moodle site administrators have full control over how the app handles session timeouts and logout behavior. They can:
** Define how the logout function works (soft logout or complete session termination).
** Set a custom session timeout duration.
** Configure the duration of the Web Service authentication token.

These configurations can be managed through:
** '''Site administration > Mobile app authentication settings'''
** '''Site administration > Security settings'''

[[es:Seguridad de Moodle app]]

Moodle app offline features

2026-04-16T09:43:54Z

Jleyva: /* Moodle App Plans */

{{Mobile}}

== Introduction ==

We live in a hyper-connected 5G world and we think the Internet is everywhere, but we usually forget about:

* Underdeveloped and developing countries
* Rural areas in big countries
* Kids with restricted data plans
* Shared internet connection in schools/classrooms
* Aerial and maritime traffic

One of the most powerful features of the Moodle app is that it enables us to work offline.

Students can browse course contents offline and participate in activities, then once they are connected back to the Internet, the app will synchronise all the necessary information with their Moodle site.

== How does the app store data for offline use? ==

* While browsing the site and its contents, though note that external contents (e.g. YouTube videos) are not downloaded and embedded files (audio, video) are not always downloaded (it depends on the user connection and file size)
* When the user downloads content by the download icon
** The user can use the “cloud” icon to download specific content or a complete section or course
** The user gets alerted when downloading large files
** If a resource has been updated in the server, a refresh icon will be shown.

===Why doesn’t the app pre-fetch/cache more data?===
# Because the user may have a monthly data plan
# Because the device storage space may be limited
# Massive data download might impact on the server performance

===What does the app consider to be a large file?===
* If the user is connected to a Wi-Fi network: large file >= 20MB
*If the user is connected to a data network: large file >= 2MB

== Course features offline support ==

* All course resources can be downloaded for offline (except URL)
* All course activities are supported (except Chat and External tool)
* Additional (non-standard) plugins usually don’t work offline
* Some functionality for certain activity modules does not work offline, see below for more information.

=== Assessment ===

The offline mode is disabled by default in Quiz and Lesson, however, the teacher can decide if they want to enable it.
* A quiz may be attempted offline only if:
** There is no time limit set
** The question behavior is deferred feedback (with or without CBM) only
** New in '''Moodle 4.3.1''' - the Quiz uses sequential navigation.
** There is no network address requirement

For detailed information about Quiz and how it works offline please see [[Moodle Mobile quiz offline attempts]].

=== Other activities ===
* SCORM and H5P packages are downloaded to the user’s device by default, there are settings to control this behaviour in order to prevent the packages from being downloaded (check this support pages for more information, [[Moodle app SCORM player]] and [[Moodle app H5P support]]).
* Wiki editing is not supported offline
* Glossaries entries can’t be deleted/updated offline
* Text assignment submissions can’t be edited offline
* Activities configured with availability conditions cannot be/are not downloaded for offline (the user will have to reconnect to be able to see activities unlocked by conditions recently met)

== What other features work offline?==

Apart from resources and activities certain course and site functionality are also available offline.

The offline support for completion is only for marking courses or activities completed (when viewed).

Conditioned activities are not downloaded for offline.

* Participants
* Grades
* Completion
* Notes
* Messaging
* Notifications
* Calendar events
* Private files
* Badges
* Blogs
* Rating
* Comments

== Synchronisation ==

Synchronisation works differently depending on the device
* Android: The app must be opened but it can be in the background (you can be using a different app).
* iOS (iPhone, iPad): The app must be opened and in the foreground (it has to be the device active app).
* Desktop: The app must be opened but it can be in the background (minimised).

🔋The battery is the key factor, mobile OS limits its usage

There are two ways of synchronising data:

* Automatic
** Runs regularly, every 10 minutes
* Manual
** The user will see a message indicating there is data pending synchronisation

===What happens with the student activity after synchronisation?===
Actions performed offline are logged and stored into the system with the synchronisation time, not with the time when they happened.
We are exploring ways to improve reporting via Moodle’s xAPI support.

For more information about how synchronisation works see [[Moodle app synchronization]].

== Configuration options ==

Site administrators can decide if they want:
* Disable completely the offline mode
* Disable all courses downloading
* Disable individual courses downloading

For disabling the previous features, please see [[Moodle app guide for admins]].

Users can decide if they want to allow synchronisation only when connected to a Wi-Fi network or also when using a data network.

==Moodle App Plans ==

When using the Moodle App, site admins can choose to subscribe to a paid plan or use the free version.

Plans limit the download of complete courses in one click.

Students can still download individual contents or sections.

We recommend a [https://apps.moodle.com/local/apps/signup_site.php?plan=premium&origin=moodledocs Premium plan subscription].

== See also ==
* [[Moodle app SCORM player]]
* [[Moodle app H5P support]]
* [[Moodle Mobile quiz]]
* [[Moodle app synchronization]]
* [https://www.youtube.com/watch?v=LqwG2XfSSiQ Use case: Scaling school leadership training through app-based Moodle learning]
* [https://www.youtube.com/watch?v=nk3SJuDduNs Use case: Reaching every learner; Scalable offline-first Moodle for African education]

[[es:Características de Moodle app sin conexión]]

Moodle app notifications

2026-04-16T09:35:26Z

Jleyva: /* For administrators */

{{Mobile}}

==For students and teachers==
[[File:12Notifications.png|thumb|Forum post notification]]
The Moodle mobile app lets you keep up to date with all that's happening in your courses and on the site. Every time you open the app, events are synchronised with the website.

You will receive [[Calendar|Moodle calendar]] event notifications automatically. If you don't want to get them, you can turn them all off individually (or globally) in the Calendar events options in the main menu.

You will also receive notifications of messages, forum posts, submitted assignments etc. (known as 'push notifications') if your site administrator has enabled these. To receive these notifications you need to enable them EITHER via the app OR via the website.

To enable mobile notifications via the app:

# Go to the app settings then Notification preferences
# Move the slider so that disable notifications is off
# Move the slider to turn on notifications for assignment, feedback, forum etc. as required

To enable mobile notifications via the website:

# Go to your user menu (top right of each page) and select Preferences
# Click the link 'Notification preferences'
# Click to turn on notifications for assignment, feedback, forum etc. as required

{|
|-
| [[File:notification preferences app.png|thumb|Notification preferences in the app]]
| [[File:notification preferences web.png|thumb|Notification preferences on website]]
|}

==For administrators==

Push notifications can be enabled by an administrator by connecting their Moodle site to a messaging server such https://messages.moodle.net (available for [[Site registration|registered Moodle sites]] only). An access key can be obtained via ''Site administration > General > Messaging > Notification settings''; be sure the 'Mobile' is enabled and then click the link to settings, on the next page select ''Request access key''. (For Moodle site versions 3.5 and 3.6 an access key can be obtained via ''Site administration > Plugins > Message outputs > Manage message outputs''. Then by clicking the link to the Mobile settings, on the next page select ''Request access key''.)

Note that from 2 April 2020, there will be certain limitations when using push notifications. Depending on the size of your site and the number of user devices receiving notifications, you may need to [https://apps.moodle.com/local/apps/signup_site.php?plan=premium&origin=moodledocs sign up to a Premium plan] in the Moodle Apps portal. For further information, see the official announcement [https://moodle.org/mod/forum/discuss.php?d=397926 Introducing our new Moodle App plans].

You can enable by default Mobile notifications for your students, please read the "Default message outputs" section in [[Messaging settings]].

If you have problems requesting the access key, please register your site on the Moodle Apps Portal https://apps.moodle.com once your site is registered there, an Airnotifier access key will be automatically generated for you.

Users then need to connect at least once with the latest version of the Moodle Mobile app in order to register their phones with the Moodle site.

=== Encrypted Push Notifications ===

Encrypted push notifications are available in Moodle LMS 4.1.4 and later, and in Moodle App 4.2 and later.

To enable encrypted push notifications, go to Site administration > Messaging > Mobile and select ‘Encrypt notifications’.

When encrypted notifications are enabled, any information or data in the notifications that could potentially identify a user is encrypted using the Curve25519/X25519 encryption algorithm. This guarantees full compliance with GDPR for organisations that want to prevent their data from being transmitted without encryption through any processing server.

The generated key pair (public and private) used to encrypt notifications is securely stored in the keystore or keychain of each device that receives notifications from your site.

'''Limitations of encrypted push notifications'''

* At least Android 8 or iOS 13 are required on devices receiving notifications. Older versions of these systems are not supported.
* Rich push notifications (notifications with media attachments) are not supported.
* Some notifications may not redirect to the appropriate page or section within the app.
* If the size of the notification content is too big, it will be replaced with the message ‘Tap to view text’.
* For iOS devices only: If the Moodle App is not in the background or foreground of devices, some notifications might not be received. This is a native iOS limitation and is based on a number of factors, such as devices’ CPU usage, notifications’ priority level (data-only messages are considered ‘low priority’ by iOS), battery level, etc. You can read additional technical information in this discussion: https://github.com/firebase/flutterfire/issues/9300.

'''Troubleshooting'''

* After upgrading your Moodle site to a version that supports encrypted push notifications (Moodle LMS 4.1.4 or later), it’s important to note that your users will only start receiving encrypted notifications once they access your upgraded site through their Moodle App for the first time.
* To verify if a device supports encrypted push notifications, follow these steps:
# Open the Moodle App and access the 'More' menu (represented by three dots).
# Select 'App settings' and then choose 'About'.
# On the 'About' page, tap on the App version (Moodle Mobile X.X) at the bottom.
# A new page titled 'Device info' will appear.
# Scroll to the bottom of the 'Device info' page to locate the section ‘Encrypted push notifications supported.’
Please note that this indicates whether a device can support encrypted push notifications, but it doesn’t necessarily mean that they have been enabled on a specific Moodle site.

=== Event Reminders plugin===

Push notifications can also include calendar event notifications, however this requires the [https://moodle.org/plugins/view/local_reminders Event Reminders plugin] to be installed on the Moodle site.

The Event Reminders plugin will automatically send reminders for Moodle calendar events in a timely manner via Moodle message interface. It also allows users to control how they receive messages for each type of event in the Moodle calendar.

=== Installing your own notifications infrastructure ===

If you have a customized version of the Moodle Mobile app, or you want to use your own notifications infrastructure, you will have to install a private [http://airnotifier.github.io AirNotifier] (backend server for notifications).

Please notice that Moodle HQ does not maintain or offer any support for any Airnotifier-related issues. Moodle HQ has funded and contributed with some fixes to this software but it is not officially maintaining or supporting it.

Moodle offers a branded app service including a private notifications infrastructure, for more information visit https://moodle.com/mobileapp/

== Troubleshooting ==

If your users are not receiving push notifications please check:

* You have not exceeded the maximum number of active devices according to your Moodle App Plan. You can register for free on https://apps.moodle.com to check your current active user devices to check if you need to upgrade to a [https://apps.moodle.com/local/apps/signup_site.php?plan=premium&origin=moodledocs Premium plan].
* You have entered an Airnotifier access key in the Mobile settings in the Site administration
* Mobile is enabled in Messaging > Notification settings in the Site administration
* In your config.php, $CFG->noemailever is not set to true (or it does not exist)
* Any user not receiving notifications has enabled mobile notifications in the mobile app in App settings > Notification preferences then check that "Disable notifications" is not selected
* Any user not receiving notifications has enabled the type of notifications they want to receive in App settings > Notification preferences
* Any user not receiving notifications hasn't disabled his current device in App settings > Notification preferences > 3 dots menu > Configure devices
* Mobile notifications are not disallowed by an administrator in 'Default message outputs' in the Site administration
* Mobile notifications are enabled in the user's Android phone (Settings > Apps > Moodle Mobile > Show notifications ticked) or iOS phone (in iOS in Settings -> Moodle Mobile > Notifications)
* The server where your Moodle site is installed is able to connect to messages.moodle.net (port 443) via telnet
* You are using the Moodle Mobile official app. If you are using a custom/branded app for your institution, please contact your institution since custom apps need their own notifications infrastructure (see above).
* Your Moodle installation cron jobs are not locked. You can check it executing the CRON manually and reading the output, more info [https://moodle.org/mod/forum/discuss.php?d=361595 here]

=== Testing push notifications ===

To test push notifications:

# Ensure that mobile notifications are enabled (as described above).
# Go to a course and create a forum with forced subscription.
# Log in as a student and create a new discussion in the forum.
# As the same student, log in on the mobile app, go to App settings > Notification preferences > Forum and enable all the notifications.
# In the same page, check that at the top of the page you see "You are configuring Mobile notifications". If it says "You are configuring notifications for web (or email)", switch to mobile via the three dots menu at the top right.
# In the same page, tap the three dots menu (top right), go to Configure devices and check that your current device is enabled.
# Now, put the Moodle Mobile app in background (switching to a different app or going to your device home).
# Log in to the site (on the web) and post a reply to the discussion started by the student., ticking the option "Send forum post notifications with no editing-time delay".
# Verify that the student receives a push notification on their mobile device.

== See also ==
* [https://docs.moodle.org/en/Moodle_app_FAQ#I_don.27t_receive_calendar_notifications_.28reminders.29_when_using_Android_12_or_above I don't receive calendar notifications (reminders) when using Android 12 or above]
* [https://docs.moodle.org/en/Moodle_app_FAQ#How_notifications_icon_badges_are_updated How notifications icon badges are updated]

[[de:Moodle App - Systemnachrichten]]
[[ca:Notificacions de la app Mobile]]
[[es:Mobile app Notificaciones Push]]
[[fr:Notifications de l'app mobile]]

Moodle app guide for admins

2026-04-16T09:34:13Z

Jleyva: /* Register your site on the Moodle Apps Portal */

{{Mobile}}
==Enable mobile services on your site==
Your site needs to have mobile access enabled so users can use the mobile app.

For sites using https, mobile access is enabled by default in new installations of Moodle 3.0 onwards.

For http sites, mobile access can be enabled by an administrator as follows:
# In ''Site administration > Mobile app > Mobile settings'' tick the 'Enable web services for mobile devices' checkbox. (For 4.0 version: In ''Site administration > Advanced features'' tick the 'Enable web services for mobile devices' checkbox
# Click the button to save changes.
If your site uses a [https://en.wikipedia.org/wiki/Transport_Layer_Security SSL certificate], it must be a trusted certificate. For security reasons the app doesn't work with self-signed certificates.

Please, verify that your certificate is valid via: https://www.geocerts.com/ssl_checker (you shouldn't see any warning).

If your site has the /login directory protected (frequently done when using the Shibboleth authentication method), you must enable access to the login/token.php script.
===Frame embedding===
If your sites uses [https://en.wikipedia.org/wiki/ReCAPTCHA reCaptcha], Vimeo videos or custom menu items (as described bellow) you must enable the admin setting "Allow frame embedding" (allowframembedding). Please, note this is not necessary since Moodle 3.7
===Is your site behind a proxy, or load balancer or complex network infrastructure?===
In that case, you may need to configure the "Ignore reserver proxies" settings in Site administration > Administration > Server > HTTP
==Register your site on the Moodle Apps Portal==
We strongly recommend you to register your site for free on the Moodle Apps portal: https://apps.moodle.com

You will be able to retrieve statistics like the number of active user devices receiving Push Notifications and [https://apps.moodle.com/local/apps/signup_site.php?plan=premium&origin=moodledocs upgrade to a Premium plan] for enjoying exclusive features.

==Simplify user onboarding==
Upon opening the Moodle app, first-time users encounter a "Your site" field, where they have to input the URL of their Moodle site to access their courses. To ensure a smooth onboarding experience for new users, follow these steps:
# Enable the '''Site finder''' feature that allows users to find their Moodle site by name, eliminating the need to manually enter the site URL. To enable this feature, view [[Moodle app guide for admins#Have your site listed in the Moodle app site finder|Have your site listed in the Moodle app site finder]] below.
# Enable the '''QR login''' feature (view [[Moodle app guide for admins#QR Login|instructions]] below). This feature allows users to scan a QR code available on their Moodle profile to access their Moodle site directly from the app.
# For Android users and Moodle LMS 4.3 and later: Encourage users to install the Moodle app by following the '''Get the mobile app''' link at the bottom of any Moodle page (located within the "'''?'''" icon on the desktop version). When users install the app through this link, they will be automatically redirected to their site login screen, eliminating the need to manually enter the site URL.
# Alternatively, you can create a dedicated help page for the Moodle app. This help page should include a link to the Google Play version of the app and clearly indicate the site URL referrer. For example, if your Moodle site is mymoodlesite.com the link will be https://play.google.com/store/apps/details?id=com.moodle.moodlemobile&referrer=siteurl%3Dhttps%3A%2F%2Fmymoodlesite.com
Please note that options 3&4 are not compatible with Google Workspace accounts (the installation referrer will be ignored in that case).
==Have your site listed in the Moodle app site finder==
The Moodle apps site finder enables a user to easily find their Moodle site by entering the name (no need to enter the site URL)
===How can I have my site listed in the Moodle app site finder?===
Your site will be automatically listed in the site finder if:
* either your site is registered and listed with a link on [https://stats.moodle.org/sites/ Registered sites] and has over five hundred mobile users and you have been using the Moodle app for over a year
* or you have purchased a [https://moodle.com/app/ Pro or Premium Moodle app subscription].
You can arrange for your site to be listed in the site finder as follows:
* If your site is hosted by a Moodle Partner, please contact them to request for your site to be listed.
* If you have a MoodleCloud site, please log in to the Moodle Apps Portal where you will find an option to have your site listed.
Otherwise, to have your site listed in the site finder, you need to purchase a [https://moodle.com/app/ Pro or Premium Moodle app subscription] from the Moodle Apps Portal.
===I don’t want my site listed in the Moodle app site finder. How can I remove it?===
You can remove your site from the site finder as follows:
# Log in to the [https://apps.moodle.com/ Moodle Apps Portal]. (If you don't yet have an account, you can create one for free.)
# Go to ‘App customisation’ -> ‘Site Listing’ and uncheck the option ‘Visible’ then save changes.
Your site will then be immediately removed from the site finder.

Alternatively, you can remove your site from the site finder by updating your site registration:
# Log in to your Moodle site as admin and go to ‘Site administration’ -> Registration.
# Change ‘Site listing’ to either ‘Do not list my site’ or ‘Only display my site name’.
Your site will then be removed from the site finder within 24 hours.
==Mobile authentication==

===MFA===
The Moodle mobile app does not support MFA natively yet, however, you can redirect users to a browser to force the authentication process to behave exactly as Moodle LMS. You can do the previous via Site administration > Mobile authentication > Type of login and then select any of the options that mention browser.

===SSO authentication method===
If your site uses a SSO authentication method (Shibboleth, LDAP SSO, OAuth...), then select via a browser window or via an embedded browser for 'Type of login' (typeoflogin) in 'Mobile authentication' in the Site administration. (This setting is provided for older pre-Moodle 3.2 sites via the [[Moodle Mobile additional features]] plugin.)

The options 'browser window' and 'embedded browser' are very similar; the only difference is when redirecting the user to enter their credentials in the site, the site will be opened in the device's default browser (for browser window) or the site will be opened "embedded" in the mobile app (for embedded browser). The user experience is better in embedded browser, but not all the authentication plugins will work in embedded browser (for example, if JavaScript popups are required they must use the 'browser window'). The admin should check whether both options work, and if so, choose 'embedded browser'.

If you are using Google OAuth you will have to use the 'browser window' method because Google recently blocked authentication via 'embedded browsers'.

If your organisation uses a custom branded app and 'Type of login' is set to 'Via a browser window' or 'Via embedded browser', then a URL scheme (forcedurlscheme) may be set. This will result in only the custom branded app working for the site: the official Moodle Mobile app will not work.

===QR Login===
Please note that this feature requires Moodle 3.9 and is only available if you are enjoying a [https://moodle.com/app/ Pro/Premium plan].

As a site administrator, you can enable login via QR. Please go to Site administration > Mobile app > Mobile authentication and select "QR code with automatic login" in the "QR code access" setting

Once enabled, your students will be able to login in the app by scanning a QR code available on their Moodle site profile.
===Biometric Login===
This feature is only available to Pro, [https://apps.moodle.com Premium plan customers] and in Branded Moodle Apps developed by Moodle HQ.

Biometric login allows your users to log in to your site via the Moodle App on Android and iOS devices using their fingerprint, face recognition or any other biometric option available on their mobile device. This makes the login process simpler, faster and more secure, and is specially useful if Autologout is enabled on your site.

'''Enabling biometric login for your site'''

You can enable Biometric login as an authentication method through the Moodle Apps Portal, going to App customisation > Authentication > Biometric login, and then selecting “Enable biometric login”. Your users will then be able to choose whether they want to use Biometric login or not.

For security reasons, users may be prompted to re-enter their credentials periodically. This interval is determined by the 'User created token duration' (tokenduration) security setting, which is set to a default duration of three months.

'''Setting up biometric login as a user'''

To use biometric login in the Moodle App, users must have biometric authentication enabled in their own device's settings (e.g. FaceID or TouchID for iOs users, or Fingerprints for Android users).

The first three times users log in to the app after you enable Biometric login, they will see a notification telling them that they can activate this new authentication method to access the app (provided that they have biometric authentication enabled in their device's settings).

Users can activate and deactivate their biometric login any time in the Moodle App in User account > Preferences.

===Auto logout===
From Moodle LMS 4.3 onwards, you can enhance security by enforcing automatic logout for your users when they leave or close the app, or it goes to the background.

You can even set your own custom re-authentication time, to suit your organisation's security requirements.

To activate auto logout, go to Site administration > Mobile app > Mobile authentication.

This feature is particularly effective when paired with Biometric login, since that streamlines the login process for your users.

== Customise your app theme ==
The app can also retrieve your custom styles from your Moodle site. Since the app is a HTML5 app, you can safely apply any CSS, CSS2 and CSS3 style.

Go to ''Administration > Site administration > Mobile app > Mobile appearance'' and enter in the mobilecssurl field a valid URL pointing to a CSS file containing your custom styles.

The CSS should be placed inside your Moodle installation (in your custom theme or inside a local plugin).

'''For example:''' ''https://mymoodlesite.com/theme/mytheme/style/mymobileapp.css''

Once the user is logged in the app, remote CSS files for applying your custom styles are regularly retrieved.

Notice that on the first time a user opens the app, he will see the default "orange" style. Your custom styles will be applied once the user has added a site in the app.

For further information, see the dev docs [https://docs.moodle.org/dev/Moodle%20Mobile%20Themes Moodle Mobile Themes].

If you want your own custom branding for your organization, Moodle offers the The [https://moodle.com/branded-app Branded Moodle Mobile app] service, please visit https://moodle.com/app/ for more information.
== Moodle Mobile additional features plugin for old Moodle sites ==
For old Moodle sites it is recommended to install the [[Moodle Mobile additional features]] plugin.
== Notifications ==
You might find them annoying but push notifications keeps you and your users informed and updated on everything about the app. Moodle only send useful and important notifications such as new features or service disruptions.

Enabling push notifications is easy! An administrator can enable it by connecting their Moodle site/s to our free Notifications server available (only) for registered Moodle sites.

An access key can be obtained via ''Site administration > General > Messaging > Notification settings''. Be sure the 'Mobile' is enabled and then click the link to settings, on the next page select ''Request access key''. (For Moodle site versions 3.5 and 3.6 an access key can be obtained via ''Site administration > Plugins > Message outputs > Manage message outputs''. Then by clicking the link to the Mobile settings, on the next page select ''Request access key''.)

The full guide on enabling push notifications can be found here: [[Mobile app notifications]]
== App banners ==
[[File:app banner.png|thumb|Moodle Mobile app banner]]
App banners let your users know a mobile app is available for the site. App banners are only displayed when accessing the site using a mobile browser.

App banners are disabled by default. They can be enabled in 'Mobile appearance' in the Site administration.

If you are using a custom mobile app, you must provide the unique identifier for the iOS and Android app; if you use the Moodle Mobile app, the settings may be left as default.

Please, notice the following:
* App banners for iOS devices (iPhone, iPad or iPod) are only shown when accessing the site using the Safari browser and the mobile app is not installed on the device yet. App banners are not displayed when using private browsing either.
* App banners for Android devices are only shown in very recent Chrome browser versions and when the app is not installed. Note also that Chrome uses an engagement heuristic that will display the banner only under certain conditions, like interactions with the site, the last time you interacted with it, etc. You can remove the engagement restriction check by disabling this special chrome flag: chrome://flags/#bypass-app-banner-engagement-checks. Please note also that certain custom Android versions (such as Samsung and Huawei ones) do not always support this feature

=='Get the mobile app' link==
In Moodle 3.4 onwards, the link 'Get the mobile app' in the footer of each page on the site encourages users to make use of the mobile app.

By default, the link is https://download.moodle.org/mobile however the setting 'App download page' can be changed e.g. for sites using a branded mobile app.

If mobile services are not enabled for the site, then the 'Get the mobile app' link is not displayed.

To prevent the 'Get the mobile app' link being displayed, simply remove the URL from the 'App download page' setting and save changes.
== Configuring the app from your site ==
'''IMPORTANT''': Please notice that the type and number of features that you can customise depend on your Moodle Apps plan, you can register for free on https://apps.moodle.com to check the different plans.

In Moodle 3.3 onwards, or with the [[Moodle Mobile additional features]] plugin, settings in the Site administration enable admins to configure the app.
* In Moodle 3.3 onwards go to ''Site administration > Mobile features''
* In sites with the Moodle Mobile additional features plugin installed, go to ''Site administration > Plugins > Local plugins > Mobile additional features''
===Force log out===
Replace the Change site option to "Log out" so that users must enter their credentials on their next access. This is useful for custom mobile apps, as there is no reason for users wanting to switch to a different site.
===Disabled features===
The mobile app may be simplified by removing unwanted features. Some items may already be not available in the app because they are not enabled on your site.

Options to remove include:

* Offline use
* Blocks (Note that from '''Moodle 4.3.1''' the Global search and Search forums blocks can be removed.)
* Comments
* Ratings
* Tags
* Create new account
* Responsive menu items
* Main menu
** Site home
** My courses
** Dashboard
** Calendar
** Notifications
** Messages
** Grades
** My learning plans
** Blog
** Files
** Web page
** Help
* Course
** Blocks
** Blog
** Search
** Competencies
** Participants
** Grades
** Course completion
** Notes
** Download course (new in 3.5)
** Download courses (new in 3.5)
* User
** Blog
** Badges
** Competencies
** Course completion
** Grades
** Send message
** Add contact
** Block contact
** Add a new note
** User picture
* Files
** Private files
** Ste files
** Upload
* Modules (Each module can be disabled separately)
* Blocks (Each block available in the app can be disabled separately)

===Custom menu items===
Additional items can be added to the app main menu (the more menu), such as a link to a different grade book.

In order to do so go to "Site administration > Mobile features > Custom menu items"

Each custom menu item should have the format: item text, link URL, link-opening method and language code (optional, for displaying the item to users of the specified language only), icon (optional, the name of the icon from https://ionicons.com) separated by pipe characters.

Possible link-opening methods are:
* app - for linking to an activity supported by the app i.e. almost all activity types, as listed in [[Moodle Mobile features]].
* inappbrowser - for linking to external URLs or site functionalities not supported by the app. The link will open in a browser inside the app overlaying the complete screen.
* browser - as for inappbrowser except that the link will instead open in the device default browser outside the app.
* embedded - as for inappbrowser except that the link will instead open in an iframe in a new page in the app. (For this option you may need to enable the admin setting "Allow frame embedding" (allowframembedding)
Tip: If you add a custom menu item and save changes, then it doesn't appear in the app main menu, double check that the item is correctly formatted.

Please, note that if custom menu items have the same URL, same link-opening method, and same language only the first custom menu item will be shown.

Please, note that if the app is using a language not indicated in the previous list, the first language in the list will be used. (So if you have a custom menu item in English (en) and French (fr), and the app is using Spanish the user will still see that custom menu item in English)

If you want options tied to a language, you can append _only to the language code, for example:
en_only
es_only, will display the custom menu item only when the app language is English or Spanish.

Example of a menu item (it will display a home icon followed by Academy information linking to the URL indicated):
Academy information|https://yoursite.com/mod/page/view.php?id=X |app|en|home

===Responsive menu items===
From 3.7 onwards menu items on bottom tabs are moved to the side of the screen on big screens. Also the number of items displayed on the menu may vary:
* On small screens (usually phones) from 2 to 5 items will be displayed depending on the size of the screen.
* On big screens (usually tablets an desktop version) more than 2 items will be displayed without limit.
If '''Responsive menu items''' is selected in Disabled features items will be displayed in side of bottom anyway but 5 items will be displayed in all cases without depending on the size of the screen.
===Custom language strings ===
Words and phrases displayed in the app can be customised via the "Site administration > Mobile app features > Custom language strings" (customlangstrings) setting.

Enter each custom language string on a new line with format: string identifier, custom language string and language code, separated by pipe characters. For example:
core.user.student|Learner|en
core.user.student|Aprendiz|es
The complete list of string identifiers is listed in https://latest.apps.moodledemo.net/assets/lang/en.json

The string identifier is before the colon.

For example:

"core.user.student": "Student",

means that the string "Student" has string identifier "core.user.student".
==Analytics and stats==

===Usage statistics from your Moodle site===

To retrieve information about the Moodle app usage, site administrators and teachers can check the site, course or activity logs.

* Site logs are available via "Site administration > Reports > Logs"
* Course logs are available via the course options (on top of the course page) "Reports > Logs"
* Activity logs are available via the activity page, on top you will find "Reports > Logs"

Among the log filters, there is a field called "All sources" with an option "Web Service/ws" that can be used to filter the entry logs generated by the mobile application.

You can compare the number of log entries generated by the "Web" versus "Web Service" (mobile app) to have an overall idea about how your users use the platform.

Please, notice that if you have custom "Web Services" or an installed plugin that uses Web Services, you will also see entries for them under the same filter.

If you have access to the site database, the table "external_tokens" has a "lastaccess" timestamp field that could be used to obtain active users of the app every day.

===Integration with Matomo analytics===
Note: This feature is available for [https://apps.moodle.com Premium app plans and Branded Moodle Apps]. To use this integration, you will need to have your own instance of Matomo.

Matomo is an open source web analytics tool that helps you monitor traffic to your Moodle site, including app activity.

'''Connecting to your Matomo instance in the Apps portal'''
[[File:Captura de pantalla 2023-11-14 a las 12.03.36.png|thumb|Moodle App Matomo Integration set up]]
To use Matomo to track app activity on your Moodle site, you will need to have your own instance of Matomo analytics, and to add your Moodle site as one of your measurable websites (see instructions on [https://matomo.org/faq/how-to/create-and-manage-websites/ Matomo’s website]). Then, follow these steps:
# Log in to the [https://apps.moodle.com Apps portal].
# Go to '''App customisation''' > '''Analytics''' > '''Matomo analytics'''.
# Check '''Track app activity'''.
# Add your '''Matomo URL''' - that's the URL of your Matomo instance, for example https://yoursite.matomo.cloud.
# Add the '''Website ID''' associated with your Moodle site in Matomo. To obtain this ID:
## Log in to your Matomo account.
## Go to '''Administration''' using the gear icon on the right side of the top navigation bar.
## On the left-hand panel, select '''Websites''' > '''Manage'''.
## In your list of measurables, find the Moodle site in which you want to track app activity. The '''ID''' of the measurable is the '''Website ID''' you need to enter in the apps portal.
# Click '''Save changes''' to establish the connection and start tracking app activity.
# If you'd like to stop tracking at any time, uncheck '''Track app activity''' and then save changes.

To filter Matomo data to isolate mobile app usage from Moodle site interactions, follow these steps:
[[File:Captura de pantalla 2023-11-14 a las 12.05.05.png|thumb|Moodle App Matomo referrer set-up]]
# Log in to your Matomo account.
# Click '''All visits''' at the top of the page
# Create a custom segment by applying this configuration: “Referrer URL” “is” “https://moodlemobile”
# To only see Moodle site interactions, do the following: “Referrer URL” “is not” “https://moodlemobile”

Please notice that the integration with Matomo does not work offline.

===Google Analytics for Firebase===
Only available when purchasing a [https://moodle.com/branded-app/ Branded Moodle App].

Google Analytics for Firebase is a free tool that provides valuable insights and data about how users interact with mobile apps.

Please notice that the integration with Google Analytics for Firebase does not work offline.

===Google Play and Apple App Store statistics===

If you have a custom mobile application, you can access statistics about app downloads and user engagement such as weekly active users and devices.

Google play:
# Go to Google Play console: https://play.google.com/console
# Select your app from the list.
# Navigate to specific tabs, such as "Statistics"

Apple App Store:
# Log in to App Store Connect: https://appstoreconnect.apple.com/
# Go to "App Analytics" from the dashboard.

==Web services token duration==
From Moodle 3.4 onwards, an admin can set how long a web services token created by a user (for example via the mobile app) is valid. (In previous versions of Moodle a token was valid for 3 months.)

The setting that dictates the previous 'User created token duration' (tokenduration) can be found under the Security section.
==App's cache==
The app caches WebService requests to decrease data usage and increase the app's speed. When the app needs to get some data from Moodle, it will use a cached request as long as it isn't expired.

This cache was improved in Moodle App 3.7.0, now there are several cache times depending on the WS being called. This means that some requests will expire more often than others. Also, if the user isn't using a WiFi connection, the expiration time will also be longer to decrease the data usage. These cache times cannot be configured using a Moodle setting.
==See also==
*[https://moodle.academy/enrol/index.php?id=100 Moodle App Configuration] - An intermediate-level Moodle Academy course for administrators who want to configure their Moodle site settings to optimise the Moodle App experience for users.
* [[Moodle Mobile FAQ]] for other administration-related mobile app questions.
* [[Moodle app security]]
* [https://docs.moodle.org/dev/Moodle%20Mobile%20debugging%20WS%20requests dev:Moodle Mobile debugging WS requests] - a guide to helping you find and report problems with the Moodle Mobile app on your site
* [https://docs.moodle.org/dev/%20Moodle%20Mobile%20Roadmap dev: Moodle Mobile Roadmap]
* [https://docs.moodle.org/dev/Moodle%20Mobile%20release%20notes dev:Moodle Mobile release notes]
* [https://docs.moodle.org/dev/Moodle%20Mobile Moodle Mobile developer docs]
* [[Moodle Mobile availability plugin]]
* [[Mobile web services]]
[https://docs.moodle.org/fr/ Guide mobile pour administrateurs]
[https://docs.moodle.org/es/Moodle app guía para administradores]
[https://docs.moodle.org/de/Moodle App - Anleitung für Administrator/innen]

Moodle app FAQ

2026-01-14T15:52:13Z

Jleyva: /* Why the site is asking for my username and password when an activity is opened in the browser? */

{{Mobile}}
==Students==
===How can I log in?===
To log in to your Moodle site with the Moodle App, you need the URL (web address) of the Moodle site that you’re trying to access. If your organisation has Search enabled, you can try searching by the name of your organisation or eLearning site.

If your organisation allows you to log in via QR code, you’ll find the QR code at the bottom of your user profile on your Moodle site. You just need to press “Scan QR code” on the app, scan the QR code on your profile and you’ll be logged in automatically.

If your organisation allows you to log in using face recognition or fingerprint, you can activate this in the App, going to User account > Preferences. You’ll need to have biometric authentication enabled in your own device’s settings.
===Who can I contact for help with the app?===
If you’re a student and need help with issues related to logging in, registering to a Moodle site or trouble connecting to the app, you should contact your school or learning organisation. For example, one of your teachers, or the person who takes care of Moodle.
Moodle HQ make the Moodle software and the Moodle app, but they don’t manage nor have access to your Moodle site or your user data.
===How can I get the Moodle app?===
You can download the Moodle App for free from [https://play.google.com/store/apps/details?id=com.moodle.moodlemobile Google Play] and the Apple [https://itunes.apple.com/app/moodle-mobile/id633359593?mt=8 App Store]. You will find it by searching “Moodle”, and the author/owner is “Moodle Pty Ltd”.
If you are unable to download the app from Google play, please visit [https://download.moodle.org/mobile/ Moodle app downloads]
===I can't get the app to work. ===
To ensure that the Moodle app functions properly, please double-check that you have correctly entered the URL address of the Moodle site you are using (please visit [https://docs.moodle.org/en/Moodle_app_FAQ#I_can%E2%80%99t_find_my_Moodle_site_in_the_app. I can’t find my Moodle site in the app]). If you are experiencing difficulties connecting to your site, please contact the person or team who takes care of Moodle in your school or learning organisation. Please note the app only works with Moodle sites that have been set up to allow it, and that are running on at least Moodle 3.5.

===I can’t find my Moodle site in the app. ===
To find your Moodle site on the app login screen, try searching for the name of your school or learning organisation.

If your school or organisation doesn’t appear in the search, you can try searching by your Moodle site URL address instead. If you don’t know the address of your Moodle site, here’s how you can find it:
# Open a web browser (like Chrome or Safari) and go to your school’s Moodle site login page.
# At the top of the page in the address bar, you'll see the URL address of your Moodle site, e.g. “campus.example.edu”. [[File:FAQ I cant find my site 1.png|alt=URL|thumb|none|''campus.example.edu'']]
# Copy the URL (don’t copy the /login nor what comes after), paste it into Your site in the app, then select Connect to your site. [[File:FAQ I cant find my site 2.png|alt=Adding an URL to the app|thumb|none|Adding an URL to the app]]
# Now you can log in to your site with your username and password.

If you tried searching by URL address and still can’t find your Moodle site, please get in touch with the person who takes care of Moodle in your school or learning organisation.
===I can’t log in with the app===
To log in to your Moodle site using the app, you first need to connect to your school’s Moodle site (view [[I can’t find my Moodle site in the app]] if you can’t find your site).

Once you’ve connected to your Moodle site, you should be able to log in with your usual username and password.

If you forgot your username or password, select the option '''Forgotten your username or password?'''. If you still have trouble logging in or can’t see any options for retrieving your username or password, please get in touch with the person who takes care of Moodle in your school or learning organisation.
===I see an error message when I try to use the app===
If you see an error message that prevents you from using the app, please get in touch with the person who takes care of Moodle in your school or learning organisation.

Some of the most common errors that your school or learning organisation will be able to fix are:
* Your token is expired or not valid.
* An error mentioning the parameter “includestealthmodules”.
* The web service function is not available.
* A message about site maintenance.

If you’re experiencing any of these errors, contact your school or learning organisation for help.
===What permissions does the app require?===
The app requires the following permissions:
* Record audio - for uploading to your Moodle site
* Read and modify the contents of your SD card - for content to be downloaded to your SD Card for offline access.
* Network access - to be able to connect with your Moodle site and check if you are connected, and if not to switch to offline mode.
* Run at startup - to receive local notifications even when the app is running in the background.
* Prevent phone from sleeping - to receive push notifications anytime.
===What are the minimum device requirements to use the Moodle app?===
Android devices: Require Android 7.0 or later. (Users with Android 5 and 6 can still use version 4.3, but they will not receive any new updates.)

iOS devices (iPhones/iPads): Require iOS 13 or later. (Please note the app was only tested on versions iOS 14 and onward.)

===I can't see my course on the app. What do I do?===
Check with your course tutor that you are correctly enrolled.
=== Why can't I upload my assignment on the app?===
If you’re experiencing any issue uploading assignment, please contact your school or learning organisation for help.
===Why can't I sometimes access the app or submit anything to it?===
This could be because of interruptions in your internet connection. Wait a while and try again. If you continue to have problems, contact your school or learning organisation for help.
===Is there a space limit on my files?===
Assignments will have a size limit which you can see, those are set by your teachers. For other space limit questions, check with your your school or learning organisation .
===When are activities completed offline synchronized?===
See [[Moodle app synchronization]].
===Why the site is asking for my username and password when an activity is opened in the browser or embedded via an iframe on the app?===
For security reasons, between auto-logins you must wait 6 minutes (this should not be a problem because most of the browsers will keep your Moodle session open). Auto-login between the Mobile app and the Moodle site (for example, for displaying embedded content from the Moodle site) is not permitted for site administrations for security reasons. If you are experiencing issues, please try first with a non-privileged user account.

In recent Moodle versions, the previous value can be configured in Site Administration > Mobile app authentication > Minimum time between auto-login requests

=== The Moodle app might seem slow (especially on Android devices) ===
If the app feels slow, it might be due to things outside the app itself. This can include:
* Slow internet connection
* Network problems
* The server responding slowly
* Content or settings not made for mobile
* Using the app on an old or slow device

We test the app carefully on many sites before each release, and we’re confident it usually works as well as or better than the website.

To make sure your site works well on mobile, please check [[Creating mobile-friendly courses]]

Finally, to troubleshoot this problem, we recommend trying the application with our demo site: https://school.moodledemo.net. Simply use the username "student" and the relevant password to access the site. If you find that the navigation and overall experience with the app are improved, then the issue may be at the server level. In this case, we suggest contacting your school or learning organisation for further assistance.

=== The Moodle app restarts/ closes / reopenes itself ===
This is likely because there are too many apps opened on your mobile device. Mobile devices have a finite amount of memory, and the device's memory manager is responsible for determining which applications to keep open and which to close.
To optimise your device's performance, we recommend closing all applications that are not currently in use. This will free up valuable memory and ensure that your device runs smoothly.
===I use LineageOS and I'm having problems using the app===
LineageOS uses a different WebView implementation not compatible vith the app. You need to install "Android System WebView" from Google Play (or via a trusted apk) and enabling it via Settings > Developer options > WebView implementation.
===H5P packages and external content embedded via iframes are not working on iOS ===
This is caused by a new feature of iOS 14 called ITP that blocks cookies for external sites embedded in the app (the H5P content is played embedded in an iframe pointing to the Moodle website) unless the user enables a setting in the app to allow those cookies.

The quick workaround is to enable the setting "Allow Cross-Website Tracking" available via the Settings app (look for the Moodle app, at the bottom) on your iPhone/iPad with iOS 14.
===I cannot reproduce audio that was recorded on browser on iOS devices (iPhones and iPads)===
This behaviour is related to this Moodle LMS bug: https://tracker.moodle.org/browse/MDL-80114

=== I don't receive calendar notifications (reminders) when using Android 12 or above ===

In order to receive calendar notifications you need to allow alarms and reminders for the Moodle app. To do this:
* Open Android Settings and go to the Moodle app settings. Another way to reach these settings is by long-clicking the Moodle app icon and pressing "App info".
* Make sure that Notifications are enabled.
* If you see a section called "Alarms & reminders", make sure it is Allowed (this setting is disabled by default in Android 14+).

==Teachers==
===How can I enable videos in my course to be downloaded?===
See the section 'Media download for offline usage' in [[Creating Moodle-app-friendly courses]].
===Which course format is it best to use?===
Topics or weekly course format is best suited to mobile devices.
===How do I make YouTube links open automatically in the app?===
Add YouTube links as a [[URL resource]].
===Why can't my students see their courses?===
If you or an administrator have correctly enrolled them in a course, they can see it in their mobile app. If they are correctly enrolled but can still not see their course, ask them to check with your Moodle site administrator.
=== I can't mark assignments in the app===
If you are experiencing problems when grading, please review that you are using the correct decimal separators (if the app interface is in English, you must use a period).
===What communications tools can I use in the app to engage with my learners?===
See [[Mobile app notifications]]. Chat, forums and messaging are all supported by the app.
===My Vimeo videos are not playing in the app===
In older versions of Moodle (pre-Moodle 3.7), it may be necessary to activate the "Allow frame embedding" admin setting. However, for those using Moodle version 3.7 or later, it is important to check whether a Proxy/Firewall/Web Server security module is setting the X-Frame-Options header in your HTTP request responses. If this is the case, it is recommended to deactivate this feature as it may cause conflicts, as Moodle already sets this header by default.

This setting is typically found in any of these configuration files .htaccess, httpd.conf or VirtualHost. To disable it, you can just use: Header always unset X-Frame-Options

You may also use Bootstrap responsive classes: https://getbootstrap.com/docs/4.0/utilities/embed/, for example, <div class="embed-responsive">
For older versions, see this forum discussion with a workaround: https://moodle.org/mod/forum/discuss.php?d=327342

If the issue is with vimeo videos on Moodle sites 3.10 or 3.11, please update the Moodle site to the latest version possible (at least 3.10.10 or 3.11.6). (See https://tracker.moodle.org/browse/MDL-74042)
===ReCaptcha doesn't work on my site===
In older versions of Moodle (pre-Moodle 3.7), it may be necessary to activate the "Allow frame embedding" admin setting. However, for those using Moodle version 3.7 or later, it is important to check whether a Proxy/Firewall/Web Server security module is setting the X-Frame-Options header in your HTTP request responses. If this is the case, it is recommended to deactivate this feature as it may cause conflicts, as Moodle already sets this header by default.
===H5P packages don't work on my site===
In older versions of Moodle (pre-Moodle 3.7), it may be necessary to activate the "Allow frame embedding" admin setting. However, for those using Moodle version 3.7 or later, it is important to check whether a Proxy/Firewall/Web Server security module is setting the X-Frame-Options header in your HTTP request responses. If this is the case, it is recommended to deactivate this feature as it may cause conflicts, as Moodle already sets this header by default.

This setting is typically found in any of these configuration files .htaccess, httpd.conf or VirtualHost. To disable it, you can just use: Header always unset X-Frame-Options

This can also happen when you are using the non-official H5P plugin (mod_hvp), in that case you will see the following message: This site is not configured properly for displaying mobile H5P content. Please contact a site administrator so they can apply the above suggested configuration changes.

If you are using the non-official H5P plugin (mod_hvp) you can also try changing the plugin settings "Mobile rendering handler" and try the different options until you find the one that works for you. You might need to restart the app everytime you change the settings.

'''Cookies issues'''

If your site uses HTTPS please ensure that the "Secure cookies only" (cookiesecure) setting under Site administration > HTTP security is enabled.

'''Dependency errors'''

When the following error appears "Missing dependency H5P.Editor. something X required by H5P.Editor. something Y". H5P packages need to include all the libraries (dependencies) they use so the package is self-contained. But sometimes packages might be missing at least one dependency.

In order to fix this, you could do the following:

Open Moodle’s Content Bank (from the link in the problematic H5P settings page) and upload your H5P package there, once uploaded, you will see the H5P package and an “Edit” button, click on that button so the editor opens, scroll down and click “Save”.
Now, you can replace the problematic H5P with this new one, for this, you can just include it from the Content bank by opening the activity settings page and the file picker.

=== I use a Moodle plugin but the app says it is not supported ===
You should contact the plugin developer and point him to this documentation: https://docs.moodle.org/dev/Moodle_Mobile_Remote_addons where it is explained how to add support to plugins in the Mobile app.

There is a list of Moodle plugins supported by the app here: https://moodle.org/plugins/browse.php?list=award&id=6

To learn more about how the Moodle app works and how to make your plugins compatible, check out the intermediate-level Moodle Academy course [https://moodle.academy/enrol/index.php?id=71 Make Your Plugin Moodle App Compatible].

=== I have problems playing SCORM packages ===
This might be caused because:
* The SCORM was added using an advanced option (remote imsmanifest.xml packages or file system repository unzipped SCORMS)
* The SCORM ZIP file was created using a tool that does not create standardised ZIP files (for example, zip files containing the inverted path separator "\" will not work on Android)
Please refer to [[Moodle app SCORM player]] for additional information.
=== My quizzes or lessons are not working offline ===
You need to edit the quiz or lesson activity settings and enable the "Allow lesson/quiz to be attempted offline using the mobile app" configuration option.
=== Maths notation is not displaying correctly in the app ===
If you are having issues with MathJax, please enable the [[TeX notation filter]] also.

If you have both filters enabled, please leave MathJax above TeX so it is always processed before TeX.

If the issue persists, we suggest disabling the 'Remove HTML tags from all activity names' (''formatstringstriptags'') option in ''Site Administration'' > ''Appearance'' > ''HTML settings''.

=== How can I disable text selection / copy in the app? ===
You can create a remote theme and add some custom CSS rules to disable it, see https://docs.moodle.org/dev/Moodle_Mobile_Themes
=== My images, videos or audios stop working after the first time ===
Please make sure the URL you're using on the media file doesn't have any redirect (e.g. http to https), always try to use the final URL. There's a bug in the library we use to download those files, it doesn't work when downloading files with redirects. We have plans to remove that library from the app, but since then please always try to use URLs without redirects.

=== Embedded YouTube videos are not working on iOS Moodle App (Error 153) ===
Unfortunately recent changes (October 2025) implemented by YouTube have disrupted the functionality of embedded YouTube videos in the Moodle app and other apps. This issue is beyond our control, and we have already reported this problem to all the third-parties that could provide a solution to help address this issue.

We are developing a workaround that will be included in the next version of the app, 5.1.0. Please note that the 5.1.0 app is still under development, and it will take some time to complete the quality assurance process and make it available in the app stores. If you have an iOS device (iPhone or iPad) and would like to help us test the workaround and verify it solves the problem, we strongly encourage you to [https://moodle.org/mod/forum/discuss.php?d=470888#p1890316 join our Beta programme].

Please visit https://moodle.org/mod/forum/discuss.php?d=470700#p1889793 for more information

==Administrators==
=== What plans are available for the Moodle app? ===
There are two main plans available for the Moodle app: Free, and Premium, each offering different features. In addition to the plans, there is also a Branded Moodle App (BMA) option. The BMA is a custom-built app that is branded to your organization. Learn more in [[Moodle app plans]].
=== How can I have my site listed in the Moodle app site finder? ===
Please refer to our [[Moodle app guide for admins]] for instructions.
=== How can I debug errors in the app? ===
Go to the More tab and then to Settings > General. Enable "Display debug messages". This will show an explanatory message when an error occurs, alternatively, you can do a full debugging via: https://docs.moodle.org/dev/Moodle_Mobile_debugging_WS_requests

=== How can I disable features in the app? ===
Please go to ''Site administration > Mobile features > Disabled features'' and select all the features you want to disable.

To select multiple features you will have to use Ctrl (Cmd in Mac) + Click

=== How can I add custom menu items in the app? ===
You can add custom additional menu items in the "more" menu of the app, the one represented by three consecutive dots.

Please go to ''Site administration > Mobile features > Custom menu items'' and follow the instructions in [[Moodle_app_guide_for_admins#Custom_menu_items|Moodle app guide for admins]] for the correct format to use.

As a quick example:
Academy information|https://yoursite.com/mod/page/view.php?id=X |app|en|home

=== How can I customise the language strings in the app? ===

Please go to ''Site administration > Mobile features > Custom language strings'' and follow the instructions in [[Moodle_app_guide_for_admins#Custom_language_strings|Moodle app guide for admins]] for the format to use.

As a quick example:
core.user.student|Learner|en
core.user.student|Aprendiz|es

=== I can connect with my iPhone (or iPad) but not with my Android phone ===
This usually happens when the site is using https and the certificate is not correctly configured or it is using an old protocol, please use these pages to check this certificate: https://www.sslshopper.com/ssl-checker.html, https://www.geocerts.com/ssl_checker, and https://www.ssllabs.com/ssltest/analyze.html

'''The certificate of this site cannot be trusted by your device: TLS connection could not be established: javax.net.ssl.SSLHandshakeException'''

This error could be caused because in any of the certification paths there is a certificate using SHA-1. Starting Android 10 this is not allowed, more information here: https://developer.android.com/privacy-and-security/security-ssl

You could easily check the previous using https://www.ssllabs.com/ssltest/analyze.html and going to the Certification Paths -> Android section, if there is any mention to SHA-1 this could be the cause. You will need to upgrade your certificates to avoid using SHA-1.

=== My certificate is fine but I still can't connect ===
This is usually a server configuration problem caused by any of the following server configuration issues:

'''"Access to XMLHttpRequest at 'https://yoursite/webservice/rest/server.php?moodlewsrestformat=json<nowiki/>...' from origin '<nowiki>http://localhost'</nowiki> has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.'''

This is because a Proxy/Firewall/Web Server security module is removing automatically the Access-Control-Allow-Origin: * header that Moodle sets to allow Web Service requests.

It is totally secure to remove that Proxy/Firewall/Web Server rule/configuration because that header is only set by Moodle when needed.

'''"access-control-allow-origin cannot contain more than one origin".'''

iOS and Android apps do not allow the following header to contain more than one item: "Access-Control-Allow-Origin". For example, a header like this: Access-Control-Allow-Origin: *, https://mydomain.com will cause problems.

This HTTP header is not valid, according to the specification you can only specify a domain or a "*":
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin

Please, review if you have a Proxy/Firewall/Web Server adding automatically values to that HTTP header.

'''Security rules are blocking requests using the Accept-Charset header'''

Some security rules, such as OWASP ModSecurity, are blocking requests with this header that is sent by the Moodle App. In future releases of the app, this problem will be fixed. But in the meantime, you should disable it. Find more about this in MOBILE-4342.
=== My certificate is fine but the Moodle app is detecting http instead of https ===
If the Moodle app is detecting http instead of https, please revise config.php (check "wwwroot" as well as "httpswwwroot")
===After updating Moodle LMS to a recent version my users cannot login===
This only applies to sites that are configured to use log in via an embedded browser pointing to their Moodle site.
This behaviour could be related to this Moodle LMS issue: https://tracker.moodle.org/browse/MDL-81897.
There are several ways to fix this issue:
# Upgrade their Moodle site to any of the indicated version in the issue that will solve the problem
# Manually apply the patch here: https://github.com/jleyva/moodle/compare/462d5f04a8...MDL-81897-master
# Immediate workaround: Change the app authentication so it will launch in a separate browser, by going to Site admin > Mobile app authentication > Type of login (and select the option that mentions external/system browser), remember to Save Changes
We’d recommend doing 3) that will immediately address the issue that is affecting new logins.
===I can't get the app to work. What can I do?===
Assuming you have enabled mobile services on your site (please visit [[Moodle app guide for admins]]), please check:
# If your site uses an SSL certificate, it must be a trusted certificate, not self-signed. Please use these tools or a similar one to check that your certificate is valid: [https://www.sslshopper.com/ssl-checker.html SSL Checker], [https://www.geocerts.com/ssl_checker SSL Checker], and [https://www.ssllabs.com/ssltest/analyze.html SSL Server Test]. All the checks must be ok, including the "Certificate Chain Complete". Otherwise the app might work on iOS but not on Android.
# Make sure that the "Access-Control-Allow-Origin" header only contains one item. For example, a header like this: Access-Control-Allow-Origin: *, <nowiki>https://mydomain.com</nowiki> will cause problems.
# [[Debugging]] is disabled (in ''Site administration > Development > Debugging'')
# The ADOdb debug option is disabled if you are using the external database auth or enrolment plugin (in ''Plugins > Authentication > External database'' and in ''Plugins > Enrolment > External database'').
# SHA-1 https certificates are not supported anymore in Chrome, this means that the Android version of the app won't work for your site. If your site doesn't work in desktop Chrome or Chromium it won't work in the Android app. See https://blog.chromium.org/2014/09/gradually-sunsetting-sha-1.html for more information
# If you are using IIS check that Anonymous access is not disabled for the /webservice directory.
# If you are using a web application firewall like AWS WAF, StackPath, Barracuda, Cloudflare, Juniper, etc... try to temporary disable it to check if that's the cause. If so, you'll have to whitelist these endpoints: login/token.php, webservice/*, lib/ajax/*, media/player/vimeo/wsplayer.php and /tokenpluginfile.php
You can also add WAF rules to allow traffic by detecting the app user agent such as: (http.user_agent contains "MoodleMobile")
If you still have a problem, please post in the [https://moodle.org/mod/forum/view.php?id=7798 Moodle for mobile forum].

If the issue started after updating Moodle LMS please visit [https://docs.moodle.org/en/Moodle_app_FAQ#After_updating_Moodle_LMS_to_a_recent_version_my_users_cannot_login After updating Moodle LMS to a recent version my users cannot login].

=== I cannot access with old users, but I can with recently created ones! ===
Please, do a "Purge all caches" via the Moodle administration settings, this will solve the problem.
===I can't view the courses tab as an administrator===
The Moodle app only displays courses you are enrolled in. If you want to view a course as an admin, you need to enrol in it.
===My Moodle site uses a SSO auth method (Shibboleth, Google OAuth, etc) and the app is not working===
See the section 'Mobile authentication' in the [[Moodle app guide for admins]] for details of how to configure it.

If configured the app is still not connecting: If your site uses an SSL certificate, it must be a trusted certificate, not self-signed. Please use this tool or a similar one to check that your certificate is fine: [https://www.geocerts.com/ssl_checker SSL Checker]. All the checks must be OK, including the "Certificate Chain Complete".

If your SSO method is unable to authenticate when using an "embedded browser" (it gives an authentication error), please check if it works with a "browser window". If it does work with the browser window then it means your SSO is performing an HTTP redirect, and these kind of redirects aren't supported by the app (the request is redirected by the browser not passing the POST parameters). Unfortunately, this is something we cannot control in the Mobile app (it can't be handled via JavaScript). For further information, see http://stackoverflow.com/questions/228225/prevent-redirection-of-xmlhttprequest and http://stackoverflow.com/questions/4168784/ajax-redirection-handling

There are only 2 possible solutions: set the authentication via a "browser window" instead of an embedded one (please notice this won't work in the Linux desktop app), or remove the redirect from the SSO auth method.

===SSO is not working with my custom auth plugin===
SSO should work in any plugin if the plugin handles correctly the $SESSION->wantsurl, this is the way SSO works when it is launched via the app:
* It launchs this URL https://yourmoodle/admin/tool/mobile/launch.php?service=local_mobile&passport=abc in the device browser
* If the user is not logged in, the browser will redirect the user to the login page
* If the auth plugin used implements correctly the handling of the wantsurl session var, once the user has logged in, the browser should redirect back to the https://yourmoodle/admin/tool/mobile/launch.php?service=local_mobile&passport=abc URL that will launch the mobile app via the custom URL protocol
Custom auth plugins may be failing in the last step,not redirecting back to tool/mobile, this will happen only if the plugin does not support correctly the $SESSION->wantsurl.

The SAML plugin works correctly but some modifications of that plugin may not work if important lines are changed.
===I am having problems requesting an airnotifier access key===
If you have registered your site but are still unable to request an access key, please register your site on the Moodle Apps Portal https://apps.moodle.com once your site is registered there, an Airnotifier access key will be automatically generated for you.
=== Push notifications are not working ===
Please check [[Mobile app notifications#Troubleshooting]]
=== How notifications icon badges are updated ===
'''Android''': Not all Android devices support icon badges so in some cases badges will never display numbers, also, depending on the device only a badge indicating that there are new notifications will be displayed when receiving a Push notification when the app is not in the foreground.

'''iOS''': The icon badge counter is only updated when the app is open and it will reflect the number of notifications pending reading or the number of message senders that sent you a message you have not read yet

In general, for iOS the icon badge displayed number should match the one displayed at the bottom of the app (or it should be the sum of the notifications and messages badges) and is not an indicator of the number of Push notifications the user has received, it acts as a reminder of pending notifications to be read that only gets updated when the user open the apps

There is an open issue to improve the behaviour on iOS, please watch MDL-73707
=== I configured 'QR code access' to automatic login, but the app still asks for credentials ===
Automatic authentication only works for Premium sites. You can see the app plans [https://moodle.com/app/ in this site].

If you're getting an error saying that the device you're using to connect isn't in the same network as the device that displays the QR code but both devices are connected to the same network, please check the section: [[#ipmismatch:_.27Client_IP_address_mismatch.27|ipmissmatch: 'Client IP address mismatch']].

=== I can log in on my Moodle site but I see a blank page or the app styles broken ===
This is usually because your Moodle site has a customised CSS.

Please try leaving empty CSS (''mobilecssurl'') on Site administration > Mobile app > Mobile appearance. If that works, please read [https://docs.moodle.org/dev/Moodle_App_Remote_Themes Moodle App Remote Themes] and create a new CSS file using the variables mentioned there

===The Moodle app does not connect to MoodleBox (or other internal self-hosted systems)===
You will need to disable SSL to make the app works, please see this forum discussion for more information: https://moodle.org/mod/forum/discuss.php?d=424353#p1739474
===I think I found a bug with the app. Where can I report it?===
# Log in to the [https://tracker.moodle.org/browse/MOBILE Moodle Mobile tracker] (you'll need to [http://tracker.moodle.org/secure/Signup%21default.jspa create a tracker account] if you've not done so previously)
# Check whether the issue has already been reported by doing a [https://tracker.moodle.org/issues/?jql=project%20%3D%20MOBILE search]
# If not, report the bug by clicking the 'Create Issue' link at the top right of the page, selecting 'Moodle app' as the project
# Add a detailed description providing as much information as possible (Moodle version, app version, device model and operating system, etc...), then click the Create button
===How can I get the app in my language?===
[[File:setting the app lang.png|thumb|100px|Setting your language]]
The Moodle app automatically detects your mobile's language and displays in the same language (if the translation exists). Otherwise, you can set the app language in App settings > General.

See also a post explaining how multi-lang works in the Moodle app: [https://moodle.org/mod/forum/discuss.php?d=453445#p1825637 Re: Language selector missing in Moodle app]

If the Moodle app is not yet available in your language, please contribute a translation! See [https://docs.moodle.org/dev/Translating%20Moodle%20Mobile Translating Moodle Mobile] for details of what to do.

=== Changes made to a Moodle site URL can cause logged-in users’ data to fail when synchronising. ===
We recommend that administrators manually log out all users after a site rename. If your site URL changes and have site users that are using the mobile Moodle App we suggest the following:
* For users that have not yet logged in - we recommend sending them the new URL
* For users already using the mobile Moodle App and potentially logged in request them to:
** log out of the mobile Moodle App,
** delete the old site, and
** log in using the new URL
Logged in Moodle users can continue working with the previous URL (with cached information) but they will not be able to synchronise the new information (therefore not receiving new information from their teachers, and teachers not receiving data or submissions from those students).
* To avoid the risk of data not synchronising, we recommend the site administrator logs out all app users, by manually deleting their tokens:
** Go to Site administration
** Click Server
** Click Web services
** Click Manage tokens
** Delete the tokens
Take into account that you still need to request your users to log in using the new URL.

=== Embedded content is not working ===

This could be caused because your site is using a Content-Security-Policy that is preventing the app from embedding content.

You can easily detect this when an error like this is displayed (javascript console): Refused to load URL because it does not appear in the frame-ancestors directive of the Content Security Policy.

If that's the case, you'd need to add the following elements: http://localhost moodleappfs://localhost at the end of the "Content-Security-Policy" HTTP header:

An example of a CSP allowing embedding Vimeo videos in the site and content in the app:
Content-Security-Policy: frame-ancestors 'self' https://*.vimeocdn.com https://*.vimeows.com https://*.vimeo.com http://localhost moodleappfs://localhost ;

Other type of embedded content that does not work is content hosted by Microsoft tools that require session or any type of authentication, such as SharePoint content.

=== Some activities are displayed incorrectly (blank, just a vertical line, ..) on the app ===
Please visit the forum post [[https://moodle.org/mod/forum/discuss.php?d=461909#p1854918| Some lesson activities do not display at all]].

=== Does the mobile app work on HarmonyOS devices such as Huawei? ===

The Moodle mobile app only officially supports Android and iOS operating systems; we cannot guarantee it will work on derived distributions.

What we can guarantee is that Push Notifications won't work as they depend on Google Play services (Firebase Cloud Messaging)

==Error messages==
=== 'Coding error: version.php file is missing for the component' ===
This error message indicates that that plugin is not correctly installed (or uninstalled) on the Moodle site you use (see [[Installing plugins]]). Please review the mod/certificate folder to check if the version.php file is missing (or has incorrect permissions) as well as purge cache too.
=== 'Can not find data record in database table external_functions' ===
This error usually happens due to a bad configuration or setting value in your Moodle site, please check:
# The user quota global setting should be an integer. For more details, see the discussion [https://moodle.org/mod/forum/discuss.php?d=320873 How to enable Moodle Mobile App for all accounts].
# The ''usermaxuploadfilesize'' should be an integer, please try to decrease the size. It can be configured in ''Site Administration > Security > Site Policies > Maximum uploaded file size''. The default value (Site upload limit) depends on the PHP configuration, you might have to change the value of ''upload_max_filesize'' and ''post_max_size'' in your ''php.ini'' file.
# The user "lang" field in the database is set to a correct value and existing language installed in the site. Some times the lang field is set via external systems to incorrect values or pointing to a language pack that was uninstalled. Please, note that to fix this you need direct access to the database and your 'user' and 'course' table.
==='Cannot connect: Verify that you have typed correctly the URL and that your site uses Moodle 3.5 or later'===
Take into account that the app will only connect to Moodle LMS sites version 3.5 onward.
Please also check:
# Mobile services are enabled for the site.
# The user is entering the correct URL for the site (see FAQ above)
# For https sites, the certificate is valid (see FAQ above)
==='Invalid Moodle site version. The Moodle app only supports Moodle systems 3.5 onwards'===
The app will only connect to Moodle LMS sites version 3.5 onward (see [https://docs.moodle.org/35/en/Upgrading Upgrade to 3.5] as well as [[Upgrade overview]]).
==='We lost connection; you need to reconnect. Your token is now invalid.' on my custom version of the Moodle app ===
Please check:
# You have followed all the steps listed in [https://docs.moodle.org/dev/Moodle%20Mobile%20Developing%20a%20plugin%20tutorial Moodle Mobile Developing a plugin tutorial]
# You have enabled the [[Capabilities/moodle/webservice:createtoken|moodle/webservice:createtoken]] for the authenticated user
==='No permission to create web service token for the service local_mobile' when attempting to log in (any user that it is not an admin)===
Please check you have enabled the moodle/webservice:createtoken for the authenticated user or any global role you want to allow to use the mobile app
==='No permission to create web service token for the service local_mobile' when attempting to log in as an admin===
You need to create a token for the admin account (only) as follows:
# Go to ''Site administration > Plugins > Web services > Manage tokens''
# Click Add
# Enter the admin username and select 'Moodle app additional features service' (i.e. do NOT leave it as 'Moodle app web service')
# Click the 'Save changes' button.
==='Invalid response value detected' when accessing the site ===
The user quota global setting should be an integer. For more details, see the discussion [https://moodle.org/mod/forum/discuss.php?d=320873 How to enable Moodle Mobile App for all accounts].
=== ' Invalid response value detected: Invalid external api response: the value is "", the server was expecting "raw" type" ===
This usually happens when there is a field with value NULL in a table in the database that should not be there. This may happen if your Moodle has been upgraded over many years and the database schema is broken.

To fix it, you can do the following:
* Detect the field that is causing the problem (it should be indicated before the error message)
* Fix the field, for example, for the password field in the lesson table: UPDATE mdl_lesson SET password = '' WHERE password IS NULL (remember that your table prefix can be different than mdl_)
==='Invalid response value detected' when accessing My Courses or Course Overview ===
This usually happens when a course uses a language that isn't installed in the site. Please make sure that all courses use valid languages. This can be easily checked in the database, table "course", there is a column named "lang".
==='A required parameter (username) was missing'===
This may happen if your site implements HTTP redirects; the request is redirected by the browser not passing the POST parameters.

Unfortunately, this is something we cannot control in the Mobile app (it can't be handled via JavaScript). For further information, see http://stackoverflow.com/questions/228225/prevent-redirection-of-xmlhttprequest and http://stackoverflow.com/questions/4168784/ajax-redirection-handling

The solution is to change the HTTP redirect and use an HTML page with a meta tag or JavaScript redirect.
==='Cannot get course contents'===
This usually happens when the course is using a course format plugin that was uninstalled from the server or that was not properly installed.

Please, reinstall again the course format plugin.
==='Access control exception' or 'Your authentication token is invalid or has expired'===
Please double-check that 'Enable web services for mobile devices' (''enablemobilewebservice'') is actually enabled. (It might be unabled if for example you have reseted some roles.)

If this error appears as soon as you enter the username and password for a new site, then it probably means that the token expiration time is badly configured. This is how to fix it:
# Go to ''Site administration > Security > Site security settings''.
# Find the setting named ''User created token duration''.
# If the value is set to 0 or it's too low, please set it back to a valid value (the default value is 12 weeks).
# Click the 'Save changes' button.

===ipmismatch: 'Client IP address mismatch'===
This error can appear when a user opens your site in a browser while using the app. This happens if your site is behind a proxy and you're using one of these Moodle versions o higher: 3.5.11, 3.6.9, 3.7.5, 3.8.2, 3.9.0.

To fix it:
# Go to ''Site administration > Administration > Server > HTTP''.
# Find the setting named ''Ignore reverse proxies'' (reverseproxyignore).
# Enter the IP of your proxy (or range of IPs).
# Click the 'Save changes' button.
If you are still experiencing issues please try to change this setting "getremoteaddrconf" (Logged IP address source) to the different existing values.

Finally, it is possible to disable the IP restriction checks for functionality such as the QR login, to do that, go to Site administration > Mobile app > Mobile app authentication, and disable the "QR authentication same IP check" setting.
=== 'The param "includestealthmodules" is invalid' ===
Please contact your learning organisation so they upgrade to at least Moodle 3.5.3 (see [https://docs.moodle.org/35/en/Upgrading Upgrade to 3.5] as well as [[Upgrade overview]]) or they manually apply the patch listed here [[MDL-63542]].

==Older versions of the Moodle app==
We always recommend using the last version of the Moodle App but some times users are still using older versions this is the reason we are keeping this list:

=== Some users are asked to reauthenticate too often when they browse the site (Moodle App <3.9.3) ===
This can happen if the app is sending too many variables to a WebService, e.g. because a course has a large number of sections and/or activities. This error was fixed in the 3.9.3 version of the app, but if you are using an older version of the app you can increase the value of ''max_input_vars'' in ''php.ini'' to fix it in your server.

=== After upgrading to 3.9.5 some of my plugins have stopped working ===
The Moodle App 3.9.5 version came with some breaking changes for plugins, most of the existing plugins have been updated to support the new changes.
Please check the following list of plugins that should work for 3.9.5 once you have upgraded to the latest version indicated in the document: https://docs.google.com/spreadsheets/d/1E9PqcUBpp9SAfQc_zJtX5tf9GeS3UN76A85IrrB4UDw/edit#gid=0

==Any further questions?==
Please post in the [http://moodle.org/mod/forum/view.php?id=7798 Moodle for mobile forum] on moodle.org.

[[Category:FAQ]]

[[de:Moodle Mobile - FAQ]]
[[ca:Moodle Mobile FAQ]]
[[es:Moodle app FAQ]]
[[fr:Moodle pour les mobiles]]
[[ja:バイルMoodle FAQ]]

Creating mobile-friendly courses

2026-01-12T11:45:42Z

Jleyva: /* Display alternative content in the Moodle app */

{{Mobile}}
As more and more students access courses from their smartphones, tablets or other mobile devices, it is increasingly important to ensure your courses are mobile-friendly.

Encouraging students to install the [https://download.moodle.org/mobile/ official Moodle mobile app] is one way to improve their learning experience. Below are some suggestions for optimising your course materials for students both using the app and accessing Moodle from mobile devices.
==Setting up your course==
*Custom sections or weekly course format is best suited to mobile devices. In topics format, the first section or the highlighted section is shown by default in the app. In weekly format, the current week is shown.
*Don't use stealth activities or direct links to activities (the links will work but is not the best experience for mobile).
*Blocks are collapsed by default and can be expanded by clicking the arrow-like tab on the right.
*If you have a mix of students accessing the course on mobile and desktop, consider asking your admin to install the [[Moodle Mobile availability plugin]] which restricts items to desktop or mobile users.

==Course content==
*Use responsive HTML in pages.
*Use a [[Page]] or [[Book]] instead of downloadable documents where possible.
*Use a [[Page]] or [[Book]] for videos instead of adding them in [[Text and media area|Text and media area resources]], avoid embedding more than one video in the same page.
*Avoid uploading many documents or having numerous, text heavy pages. Think more in terms of short "information-bytes".
*If you include YouTube videos, keep them short and consider providing them for download and offline viewing in a [[Folder resource|folder]]. Not all video formats are supported so add them in different formats. (MP4 is probably the most widely accepted format.)
* For YouTube or Vimeo videos, you may use Bootstrap responsive classes: https://getbootstrap.com/docs/4.0/utilities/embed/, for example:
<pre><div class="embed-responsive"><video...</pre>
*Note that drag and drop questions behave differently in the app. You can't drag images, you need to tap to select and tap to drop.
*Note that if you add YouTube video links or map links as URL resources, they will open automatically in the app.
{|
| [[File:moodlemobile_short_text_intro.png|thumb|Short text for label]]
| [[File:moodlemobile_responsive_html.png|thumb|Responsive HTML]]
| [[File:moodlemobile_youtube_maps_links.png|thumb|Map link]]
|}
* Use only plugins with mobile app support so they can be accessed via the mobile app - see [https://moodle.org/plugins/browse.php?list=award&id=6 Moodle plugins directory: Award: mobile app support].
* Avoid relative URLs such as ../mod/page/views.php?id=X as the app won't be able to guess the proper URL, if it is necessary to use URLs without domain, please use absolute URLs such as /mod/page/views.php?id=X

===Using Bootstrap components===

The mobile app supports all '''[https://getbootstrap.com/docs/5.3/getting-started/introduction/ Bootstrap 5] CSS components'''; however, please refer to the list below for specific '''JavaScript (JS) component''' compatibility. To ensure backward compatibility, a subset of [https://getbootstrap.com/docs/4.6/getting-started/introduction/ '''Bootstrap 4'''] components will remain supported for a limited time.

"'''Supported Bootstrap 5 JS components''' ''Note: These components have been adapted to align with the app's framework and visual styles, so their behavior or appearance may differ slightly from the original Bootstrap implementation:''

* [https://getbootstrap.com/docs/5.3/components/collapse/ Collapse]
* [https://getbootstrap.com/docs/5.3/components/carousel/ Carousel]
* [https://getbootstrap.com/docs/5.3/components/accordion/ Accordion]
* [https://getbootstrap.com/docs/5.3/components/modal/ Modal]
* [https://getbootstrap.com/docs/5.3/components/popovers/ Popovers]
* [https://getbootstrap.com/docs/5.3/components/tooltips/ Tooltips]
* [https://getbootstrap.com/docs/5.3/components/navs-tabs/ Tabs]
* Dismiss / close button on:
** [https://getbootstrap.com/docs/5.3/components/close-button/ Alerts]
** [https://getbootstrap.com/docs/5.3/components/offcanvas/ Offcanvas]
** [https://getbootstrap.com/docs/5.3/components/toasts/ Toasts]
** [https://getbootstrap.com/docs/5.3/components/modal/ Modal]

Please note that not all component properties are supported. We recommend testing your content within the app to verify its functionality and appearance.

=== Display mode utility classes for the app ===
Moodle App has introduced specific CSS classes that allow content creators to toggle the visibility and display behavior of elements specifically within the '''Moodle App'''. This provides a way to override standard Bootstrap classes (like <code>d-none</code>) to create a tailored mobile experience.

==== General display classes ====
These classes are used to control how elements behave in the mobile app regardless of the operating system (iOS or Android).
{| class="wikitable"
|CSS Class
|Effect in the Mobile App
|Use Case
|-
|<code>mobileapp-d-none</code>
|'''Hides''' the element.
|Content that should only be visible on desktop.
|-
|<code>mobileapp-d-block</code>
|Displays as '''block'''.
|Making a hidden element (<code>d-none</code>) visible in the app.
|-
|<code>mobileapp-d-inline</code>
|Displays as '''inline'''.
|Inline text or icons specific to mobile users.
|-
|<code>mobileapp-d-inline-block</code>
|Displays as '''inline-block'''.
|Inline block text or icons specific to mobile users.
|-
|<code>mobileapp-d-flex</code>
|Displays as '''flex'''.
|Flexible layouts optimized for mobile screens.
|}

==== Platform-Specific Classes (OS) ====
You can target users based on their specific mobile device. This is useful for providing specific instructions for Android or iOS users (e.g., store links or system settings).

* '''Android:''' <code>mobileapp-android-d-block</code>, <code>mobileapp-android-d-none</code>, <code>mobileapp-android-d-inline</code>, etc.
* '''iOS:''' <code>mobileapp-ios-d-block</code>, <code>mobileapp-ios-d-none</code>, <code>mobileapp-ios-d-inline</code>, etc.

==== Examples ====

===== Show content ONLY in the Mobile App =====
Use the Bootstrap <code>d-none</code> class to hide it everywhere, then use the mobile class to reveal it in the app.
<nowiki><div class="d-none mobileapp-d-block"></nowiki>
This message is only visible to users inside the Mobile App.
<nowiki></div></nowiki>

===== Hide content in the Mobile App =====
Use the Bootstrap <code>d-block</code> class to show it on the web, and the mobile class to hide it in the app.
<nowiki><div class="d-block mobileapp-d-none"></nowiki>
This section is hidden in the app to save data or screen space.
<nowiki></div></nowiki>

===== Targeted OS Messaging =====
Messages won't be shown on the web and will be different on iOS and Android.
<nowiki><div class="mobileapp-ios-d-block d-none"></nowiki>
Instructions specifically for iPhone/iPad users.
<nowiki></div></nowiki>
<nowiki><div class="mobileapp-android-d-block d-none"></nowiki>
Instructions specifically for Android users.
<nowiki></div></nowiki>

===Media download for offline usage===
To enable media files, such as video, to be automatically downloaded when viewed.
* The file must be uploaded to the course, rather than being linked to (from YouTube, Vimeo etc.)
* The file must be small - less than 2MB for 3G users or less than 20MB for WiFi users
When a page containing the video is viewed (without playing the video), the file will then be downloaded.

When using Moodle Mobile 3.1 or later with a WiFi connection, when the video is played, the file will be downloaded in the background. The next time the video is played, the downloaded file will be used.

Please note that if the user did a full download of the courses, the files will be downloaded regardless its size.

===Activities===

'''Quizzes'''

Quizzes with lots of questions do not perform very well on the website or the app as the backend server will have to do heavy preparatory work, especially if random questions are used.

In general, our recommendation is to avoid having just a quiz with lots of questions, it is better to split it into different quizzes.

Another recommendation is to limit the number of questions per page to avoid having more than 5 questions displayed on a single page on a very narrow screen.

===Offline activities===
All the supported activities work offline, although some require specific settings like the lesson and quiz module, you can find bellow additional information:
* [[Moodle Mobile quiz offline attempts]]
* [[Moodle app H5P support#Working offline|Moodle H5P]]
* [[Moodle app SCORM player]]

=== Things to avoid===
Some activities are not yet fully supported by the mobile app, so find alternatives. See [[Moodle Mobile SCORM player]] for things to avoid in SCORM packages.

You can find the list of activities supported by the app in the [[Moodle Mobile features]] page.

==Use the latest stable version of Moodle==
As indicated in [[Moodle Mobile features]] some features are only available in recent Moodle versions.

It is recommended to use the [https://moodledev.io/general/releases latest stable version].

==Notifications and messages==
Encourage your students to enable mobile notifications so they are alerted about calendar events, forum posts, messages, assignment submissions and so on. Find out more in [[Mobile app notifications]].

You can also enable mobile notifications for all the users by default via the [[Messaging settings]] default message outputs. Students can disable Mobile notifications within the app.
==Mobile device considerations==
The app works better on devices running modern devices.

In old devices you may find problems related to:
* User interface
* Connection problems (specifically when connecting to sites using https certificates)
* Slowness

==Links to open the Moodle app==
If required, links which open the Moodle app may be provided in the course (for users browsing the site using a mobile device with the app installed).

Links are of the form <code>moodlemobile://https://username@domain.com?token=TOKEN&privatetoken=PRIVATETOKEN&redirect=http://domain.com/course/view.php?id=2</code>.<br />
Please notice that this kind of links are only supported in Moodle app 3.7.0 onwards. If your app has an older version you'll have to use the old format: <code>moodlemobile://link=https://yourmoodlesite.org/mod/...</code>.

For more information about this, please read [https://docs.moodle.org/dev/Open_the_Moodle_app_from_another_app Open the Moodle app from another app].

==Display alternative content in the Moodle app==
In some cases, content that works perfectly in a web browser (Moodle LMS) might not work as intended within the Moodle app, for example, certain iframes or complex embeds. Since the Moodle app version 5.1, you can now provide alternative text or links specifically for app users using two HTML attributes.

To do this, you need to edit the source code of your content (the HTML) and add the following attributes to an element to replace its contents:

* '''data-app-alt-msg''': The text to display inside the element. If not present, only ''data-app-alt-url'' will be displayed.
* '''data-app-alt-url''': A clickable URL that appears after the message text.

'''Note I''': These attributes replace the content (children) of the element they are placed on, not the element itself. Always place these attributes on a parent container (like a <code><nowiki><div></nowiki></code> or <code><nowiki><p></nowiki></code>).

'''Note II''': These attributes might be removed by your Moodle site filtering depending on the values of these settings: "Content cleaning everywhere (forceclean)" if it is enabled and "Enable trusted content (enabletrusttext)" if it is disabled.

==== Example: Replacing an incompatible iframe ====
If you have an iframe that works fine in Moodle LMS but it doesn't in the Moodle app, you can wrap it in a <code><nowiki><div></nowiki></code> to provide a fallback link for app users:
<nowiki><div data-app-alt-url="https://videourl.com" data-app-alt-msg="This video is not compatible with the app. Please click the link to open it in a browser."></nowiki>
<iframe src="https://videonotappcompatible.com"></iframe>
<nowiki></div></nowiki>
'''What the user sees:'''

* On desktop: The iframe renders normally.
* In the Moodle app: The user sees "This video is not compatible with the app. Please click the link to open it in a browser.", followed by the link specified in data-app-alt-url.

==Learn more==
* Free course on Moodle Academy [https://moodle.academy/enrol/index.php?id=100 Moodle App configuration]
* Forum post: [https://moodle.org/mod/forum/discuss.php?d=349160 Try the Moodle Mobile app with a mobile-friendly course].
* [https://docs.moodle.org/dev/Creating_mobile_question_types How to make third party question types work in Mobile] documentation for developers
[[de:Moodle Mobile - Websites optimieren]]
[[es:Crear sitios amistosos para Moodle Mobile]]
[[fr:Créer des cours pour appareils mobiles]]

Moodle app FAQ

2025-12-01T08:24:00Z

Jleyva: /* Administrators */

{{Mobile}}
==Students==
===How can I log in?===
To log in to your Moodle site with the Moodle App, you need the URL (web address) of the Moodle site that you’re trying to access. If your organisation has Search enabled, you can try searching by the name of your organisation or eLearning site.

If your organisation allows you to log in via QR code, you’ll find the QR code at the bottom of your user profile on your Moodle site. You just need to press “Scan QR code” on the app, scan the QR code on your profile and you’ll be logged in automatically.

If your organisation allows you to log in using face recognition or fingerprint, you can activate this in the App, going to User account > Preferences. You’ll need to have biometric authentication enabled in your own device’s settings.
===Who can I contact for help with the app?===
If you’re a student and need help with issues related to logging in, registering to a Moodle site or trouble connecting to the app, you should contact your school or learning organisation. For example, one of your teachers, or the person who takes care of Moodle.
Moodle HQ make the Moodle software and the Moodle app, but they don’t manage nor have access to your Moodle site or your user data.
===How can I get the Moodle app?===
You can download the Moodle App for free from [https://play.google.com/store/apps/details?id=com.moodle.moodlemobile Google Play] and the Apple [https://itunes.apple.com/app/moodle-mobile/id633359593?mt=8 App Store]. You will find it by searching “Moodle”, and the author/owner is “Moodle Pty Ltd”.
If you are unable to download the app from Google play, please visit [https://download.moodle.org/mobile/ Moodle app downloads]
===I can't get the app to work. ===
To ensure that the Moodle app functions properly, please double-check that you have correctly entered the URL address of the Moodle site you are using (please visit [https://docs.moodle.org/en/Moodle_app_FAQ#I_can%E2%80%99t_find_my_Moodle_site_in_the_app. I can’t find my Moodle site in the app]). If you are experiencing difficulties connecting to your site, please contact the person or team who takes care of Moodle in your school or learning organisation. Please note the app only works with Moodle sites that have been set up to allow it, and that are running on at least Moodle 3.5.

===I can’t find my Moodle site in the app. ===
To find your Moodle site on the app login screen, try searching for the name of your school or learning organisation.

If your school or organisation doesn’t appear in the search, you can try searching by your Moodle site URL address instead. If you don’t know the address of your Moodle site, here’s how you can find it:
# Open a web browser (like Chrome or Safari) and go to your school’s Moodle site login page.
# At the top of the page in the address bar, you'll see the URL address of your Moodle site, e.g. “campus.example.edu”. [[File:FAQ I cant find my site 1.png|alt=URL|thumb|none|''campus.example.edu'']]
# Copy the URL (don’t copy the /login nor what comes after), paste it into Your site in the app, then select Connect to your site. [[File:FAQ I cant find my site 2.png|alt=Adding an URL to the app|thumb|none|Adding an URL to the app]]
# Now you can log in to your site with your username and password.

If you tried searching by URL address and still can’t find your Moodle site, please get in touch with the person who takes care of Moodle in your school or learning organisation.
===I can’t log in with the app===
To log in to your Moodle site using the app, you first need to connect to your school’s Moodle site (view [[I can’t find my Moodle site in the app]] if you can’t find your site).

Once you’ve connected to your Moodle site, you should be able to log in with your usual username and password.

If you forgot your username or password, select the option '''Forgotten your username or password?'''. If you still have trouble logging in or can’t see any options for retrieving your username or password, please get in touch with the person who takes care of Moodle in your school or learning organisation.
===I see an error message when I try to use the app===
If you see an error message that prevents you from using the app, please get in touch with the person who takes care of Moodle in your school or learning organisation.

Some of the most common errors that your school or learning organisation will be able to fix are:
* Your token is expired or not valid.
* An error mentioning the parameter “includestealthmodules”.
* The web service function is not available.
* A message about site maintenance.

If you’re experiencing any of these errors, contact your school or learning organisation for help.
===What permissions does the app require?===
The app requires the following permissions:
* Record audio - for uploading to your Moodle site
* Read and modify the contents of your SD card - for content to be downloaded to your SD Card for offline access.
* Network access - to be able to connect with your Moodle site and check if you are connected, and if not to switch to offline mode.
* Run at startup - to receive local notifications even when the app is running in the background.
* Prevent phone from sleeping - to receive push notifications anytime.
===What are the minimum device requirements to use the Moodle app?===
Android devices: Require Android 7.0 or later. (Users with Android 5 and 6 can still use version 4.3, but they will not receive any new updates.)

iOS devices (iPhones/iPads): Require iOS 13 or later. (Please note the app was only tested on versions iOS 14 and onward.)

===I can't see my course on the app. What do I do?===
Check with your course tutor that you are correctly enrolled.
=== Why can't I upload my assignment on the app?===
If you’re experiencing any issue uploading assignment, please contact your school or learning organisation for help.
===Why can't I sometimes access the app or submit anything to it?===
This could be because of interruptions in your internet connection. Wait a while and try again. If you continue to have problems, contact your school or learning organisation for help.
===Is there a space limit on my files?===
Assignments will have a size limit which you can see, those are set by your teachers. For other space limit questions, check with your your school or learning organisation .
===When are activities completed offline synchronized?===
See [[Moodle app synchronization]].
===Why the site is asking for my username and password when an activity is opened in the browser?===
For security reasons, between auto-logins you must wait 6 minutes (this should not be a problem because most of the browsers will keep your Moodle session open).
In recent Moodle versions, the previous value can be configured in Site Administration > Mobile app authentication > Minimum time between auto-login requests

=== The Moodle app might seem slow (especially on Android devices) ===
If the app feels slow, it might be due to things outside the app itself. This can include:
* Slow internet connection
* Network problems
* The server responding slowly
* Content or settings not made for mobile
* Using the app on an old or slow device

We test the app carefully on many sites before each release, and we’re confident it usually works as well as or better than the website.

To make sure your site works well on mobile, please check [[Creating mobile-friendly courses]]

Finally, to troubleshoot this problem, we recommend trying the application with our demo site: https://school.moodledemo.net. Simply use the username "student" and the relevant password to access the site. If you find that the navigation and overall experience with the app are improved, then the issue may be at the server level. In this case, we suggest contacting your school or learning organisation for further assistance.

=== The Moodle app restarts/ closes / reopenes itself ===
This is likely because there are too many apps opened on your mobile device. Mobile devices have a finite amount of memory, and the device's memory manager is responsible for determining which applications to keep open and which to close.
To optimise your device's performance, we recommend closing all applications that are not currently in use. This will free up valuable memory and ensure that your device runs smoothly.
===I use LineageOS and I'm having problems using the app===
LineageOS uses a different WebView implementation not compatible vith the app. You need to install "Android System WebView" from Google Play (or via a trusted apk) and enabling it via Settings > Developer options > WebView implementation.
===H5P packages and external content embedded via iframes are not working on iOS ===
This is caused by a new feature of iOS 14 called ITP that blocks cookies for external sites embedded in the app (the H5P content is played embedded in an iframe pointing to the Moodle website) unless the user enables a setting in the app to allow those cookies.

The quick workaround is to enable the setting "Allow Cross-Website Tracking" available via the Settings app (look for the Moodle app, at the bottom) on your iPhone/iPad with iOS 14.
===I cannot reproduce audio that was recorded on browser on iOS devices (iPhones and iPads)===
This behaviour is related to this Moodle LMS bug: https://tracker.moodle.org/browse/MDL-80114

=== I don't receive calendar notifications (reminders) when using Android 12 or above ===

In order to receive calendar notifications you need to allow alarms and reminders for the Moodle app. To do this:
* Open Android Settings and go to the Moodle app settings. Another way to reach these settings is by long-clicking the Moodle app icon and pressing "App info".
* Make sure that Notifications are enabled.
* If you see a section called "Alarms & reminders", make sure it is Allowed (this setting is disabled by default in Android 14+).

==Teachers==
===How can I enable videos in my course to be downloaded?===
See the section 'Media download for offline usage' in [[Creating Moodle-app-friendly courses]].
===Which course format is it best to use?===
Topics or weekly course format is best suited to mobile devices.
===How do I make YouTube links open automatically in the app?===
Add YouTube links as a [[URL resource]].
===Why can't my students see their courses?===
If you or an administrator have correctly enrolled them in a course, they can see it in their mobile app. If they are correctly enrolled but can still not see their course, ask them to check with your Moodle site administrator.
=== I can't mark assignments in the app===
If you are experiencing problems when grading, please review that you are using the correct decimal separators (if the app interface is in English, you must use a period).
===What communications tools can I use in the app to engage with my learners?===
See [[Mobile app notifications]]. Chat, forums and messaging are all supported by the app.
===My Vimeo videos are not playing in the app===
In older versions of Moodle (pre-Moodle 3.7), it may be necessary to activate the "Allow frame embedding" admin setting. However, for those using Moodle version 3.7 or later, it is important to check whether a Proxy/Firewall/Web Server security module is setting the X-Frame-Options header in your HTTP request responses. If this is the case, it is recommended to deactivate this feature as it may cause conflicts, as Moodle already sets this header by default.

This setting is typically found in any of these configuration files .htaccess, httpd.conf or VirtualHost. To disable it, you can just use: Header always unset X-Frame-Options

You may also use Bootstrap responsive classes: https://getbootstrap.com/docs/4.0/utilities/embed/, for example, <div class="embed-responsive">
For older versions, see this forum discussion with a workaround: https://moodle.org/mod/forum/discuss.php?d=327342

If the issue is with vimeo videos on Moodle sites 3.10 or 3.11, please update the Moodle site to the latest version possible (at least 3.10.10 or 3.11.6). (See https://tracker.moodle.org/browse/MDL-74042)
===ReCaptcha doesn't work on my site===
In older versions of Moodle (pre-Moodle 3.7), it may be necessary to activate the "Allow frame embedding" admin setting. However, for those using Moodle version 3.7 or later, it is important to check whether a Proxy/Firewall/Web Server security module is setting the X-Frame-Options header in your HTTP request responses. If this is the case, it is recommended to deactivate this feature as it may cause conflicts, as Moodle already sets this header by default.
===H5P packages don't work on my site===
In older versions of Moodle (pre-Moodle 3.7), it may be necessary to activate the "Allow frame embedding" admin setting. However, for those using Moodle version 3.7 or later, it is important to check whether a Proxy/Firewall/Web Server security module is setting the X-Frame-Options header in your HTTP request responses. If this is the case, it is recommended to deactivate this feature as it may cause conflicts, as Moodle already sets this header by default.

This setting is typically found in any of these configuration files .htaccess, httpd.conf or VirtualHost. To disable it, you can just use: Header always unset X-Frame-Options

This can also happen when you are using the non-official H5P plugin (mod_hvp), in that case you will see the following message: This site is not configured properly for displaying mobile H5P content. Please contact a site administrator so they can apply the above suggested configuration changes.

If you are using the non-official H5P plugin (mod_hvp) you can also try changing the plugin settings "Mobile rendering handler" and try the different options until you find the one that works for you. You might need to restart the app everytime you change the settings.

'''Cookies issues'''

If your site uses HTTPS please ensure that the "Secure cookies only" (cookiesecure) setting under Site administration > HTTP security is enabled.

'''Dependency errors'''

When the following error appears "Missing dependency H5P.Editor. something X required by H5P.Editor. something Y". H5P packages need to include all the libraries (dependencies) they use so the package is self-contained. But sometimes packages might be missing at least one dependency.

In order to fix this, you could do the following:

Open Moodle’s Content Bank (from the link in the problematic H5P settings page) and upload your H5P package there, once uploaded, you will see the H5P package and an “Edit” button, click on that button so the editor opens, scroll down and click “Save”.
Now, you can replace the problematic H5P with this new one, for this, you can just include it from the Content bank by opening the activity settings page and the file picker.

=== I use a Moodle plugin but the app says it is not supported ===
You should contact the plugin developer and point him to this documentation: https://docs.moodle.org/dev/Moodle_Mobile_Remote_addons where it is explained how to add support to plugins in the Mobile app.

There is a list of Moodle plugins supported by the app here: https://moodle.org/plugins/browse.php?list=award&id=6

To learn more about how the Moodle app works and how to make your plugins compatible, check out the intermediate-level Moodle Academy course [https://moodle.academy/enrol/index.php?id=71 Make Your Plugin Moodle App Compatible].

=== I have problems playing SCORM packages ===
This might be caused because:
* The SCORM was added using an advanced option (remote imsmanifest.xml packages or file system repository unzipped SCORMS)
* The SCORM ZIP file was created using a tool that does not create standardised ZIP files (for example, zip files containing the inverted path separator "\" will not work on Android)
Please refer to [[Moodle app SCORM player]] for additional information.
=== My quizzes or lessons are not working offline ===
You need to edit the quiz or lesson activity settings and enable the "Allow lesson/quiz to be attempted offline using the mobile app" configuration option.
=== Maths notation is not displaying correctly in the app ===
If you are having issues with MathJax, please enable the [[TeX notation filter]] also.

If you have both filters enabled, please leave MathJax above TeX so it is always processed before TeX.

If the issue persists, we suggest disabling the 'Remove HTML tags from all activity names' (''formatstringstriptags'') option in ''Site Administration'' > ''Appearance'' > ''HTML settings''.

=== How can I disable text selection / copy in the app? ===
You can create a remote theme and add some custom CSS rules to disable it, see https://docs.moodle.org/dev/Moodle_Mobile_Themes
=== My images, videos or audios stop working after the first time ===
Please make sure the URL you're using on the media file doesn't have any redirect (e.g. http to https), always try to use the final URL. There's a bug in the library we use to download those files, it doesn't work when downloading files with redirects. We have plans to remove that library from the app, but since then please always try to use URLs without redirects.

=== Embedded YouTube videos are not working on iOS Moodle App (Error 153) ===
Unfortunately recent changes (October 2025) implemented by YouTube have disrupted the functionality of embedded YouTube videos in the Moodle app and other apps. This issue is beyond our control, and we have already reported this problem to all the third-parties that could provide a solution to help address this issue.

We are developing a workaround that will be included in the next version of the app, 5.1.0. Please note that the 5.1.0 app is still under development, and it will take some time to complete the quality assurance process and make it available in the app stores. If you have an iOS device (iPhone or iPad) and would like to help us test the workaround and verify it solves the problem, we strongly encourage you to [https://moodle.org/mod/forum/discuss.php?d=470888#p1890316 join our Beta programme].

Please visit https://moodle.org/mod/forum/discuss.php?d=470700#p1889793 for more information

==Administrators==
=== What plans are available for the Moodle app? ===
There are two main plans available for the Moodle app: Free, and Premium, each offering different features. In addition to the plans, there is also a Branded Moodle App (BMA) option. The BMA is a custom-built app that is branded to your organization. Learn more in [[Moodle app plans]].
=== How can I have my site listed in the Moodle app site finder? ===
Please refer to our [[Moodle app guide for admins]] for instructions.
=== How can I debug errors in the app? ===
Go to the More tab and then to Settings > General. Enable "Display debug messages". This will show an explanatory message when an error occurs, alternatively, you can do a full debugging via: https://docs.moodle.org/dev/Moodle_Mobile_debugging_WS_requests

=== How can I disable features in the app? ===
Please go to ''Site administration > Mobile features > Disabled features'' and select all the features you want to disable.

To select multiple features you will have to use Ctrl (Cmd in Mac) + Click

=== How can I add custom menu items in the app? ===
You can add custom additional menu items in the "more" menu of the app, the one represented by three consecutive dots.

Please go to ''Site administration > Mobile features > Custom menu items'' and follow the instructions in [[Moodle_app_guide_for_admins#Custom_menu_items|Moodle app guide for admins]] for the correct format to use.

As a quick example:
Academy information|https://yoursite.com/mod/page/view.php?id=X |app|en|home

=== How can I customise the language strings in the app? ===

Please go to ''Site administration > Mobile features > Custom language strings'' and follow the instructions in [[Moodle_app_guide_for_admins#Custom_language_strings|Moodle app guide for admins]] for the format to use.

As a quick example:
core.user.student|Learner|en
core.user.student|Aprendiz|es

=== I can connect with my iPhone (or iPad) but not with my Android phone ===
This usually happens when the site is using https and the certificate is not correctly configured or it is using an old protocol, please use these pages to check this certificate: https://www.sslshopper.com/ssl-checker.html, https://www.geocerts.com/ssl_checker, and https://www.ssllabs.com/ssltest/analyze.html

'''The certificate of this site cannot be trusted by your device: TLS connection could not be established: javax.net.ssl.SSLHandshakeException'''

This error could be caused because in any of the certification paths there is a certificate using SHA-1. Starting Android 10 this is not allowed, more information here: https://developer.android.com/privacy-and-security/security-ssl

You could easily check the previous using https://www.ssllabs.com/ssltest/analyze.html and going to the Certification Paths -> Android section, if there is any mention to SHA-1 this could be the cause. You will need to upgrade your certificates to avoid using SHA-1.

=== My certificate is fine but I still can't connect ===
This is usually a server configuration problem caused by any of the following server configuration issues:

'''"Access to XMLHttpRequest at 'https://yoursite/webservice/rest/server.php?moodlewsrestformat=json<nowiki/>...' from origin '<nowiki>http://localhost'</nowiki> has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.'''

This is because a Proxy/Firewall/Web Server security module is removing automatically the Access-Control-Allow-Origin: * header that Moodle sets to allow Web Service requests.

It is totally secure to remove that Proxy/Firewall/Web Server rule/configuration because that header is only set by Moodle when needed.

'''"access-control-allow-origin cannot contain more than one origin".'''

iOS and Android apps do not allow the following header to contain more than one item: "Access-Control-Allow-Origin". For example, a header like this: Access-Control-Allow-Origin: *, https://mydomain.com will cause problems.

This HTTP header is not valid, according to the specification you can only specify a domain or a "*":
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin

Please, review if you have a Proxy/Firewall/Web Server adding automatically values to that HTTP header.

'''Security rules are blocking requests using the Accept-Charset header'''

Some security rules, such as OWASP ModSecurity, are blocking requests with this header that is sent by the Moodle App. In future releases of the app, this problem will be fixed. But in the meantime, you should disable it. Find more about this in MOBILE-4342.
=== My certificate is fine but the Moodle app is detecting http instead of https ===
If the Moodle app is detecting http instead of https, please revise config.php (check "wwwroot" as well as "httpswwwroot")
===After updating Moodle LMS to a recent version my users cannot login===
This only applies to sites that are configured to use log in via an embedded browser pointing to their Moodle site.
This behaviour could be related to this Moodle LMS issue: https://tracker.moodle.org/browse/MDL-81897.
There are several ways to fix this issue:
# Upgrade their Moodle site to any of the indicated version in the issue that will solve the problem
# Manually apply the patch here: https://github.com/jleyva/moodle/compare/462d5f04a8...MDL-81897-master
# Immediate workaround: Change the app authentication so it will launch in a separate browser, by going to Site admin > Mobile app authentication > Type of login (and select the option that mentions external/system browser), remember to Save Changes
We’d recommend doing 3) that will immediately address the issue that is affecting new logins.
===I can't get the app to work. What can I do?===
Assuming you have enabled mobile services on your site (please visit [[Moodle app guide for admins]]), please check:
# If your site uses an SSL certificate, it must be a trusted certificate, not self-signed. Please use these tools or a similar one to check that your certificate is valid: [https://www.sslshopper.com/ssl-checker.html SSL Checker], [https://www.geocerts.com/ssl_checker SSL Checker], and [https://www.ssllabs.com/ssltest/analyze.html SSL Server Test]. All the checks must be ok, including the "Certificate Chain Complete". Otherwise the app might work on iOS but not on Android.
# Make sure that the "Access-Control-Allow-Origin" header only contains one item. For example, a header like this: Access-Control-Allow-Origin: *, <nowiki>https://mydomain.com</nowiki> will cause problems.
# [[Debugging]] is disabled (in ''Site administration > Development > Debugging'')
# The ADOdb debug option is disabled if you are using the external database auth or enrolment plugin (in ''Plugins > Authentication > External database'' and in ''Plugins > Enrolment > External database'').
# SHA-1 https certificates are not supported anymore in Chrome, this means that the Android version of the app won't work for your site. If your site doesn't work in desktop Chrome or Chromium it won't work in the Android app. See https://blog.chromium.org/2014/09/gradually-sunsetting-sha-1.html for more information
# If you are using IIS check that Anonymous access is not disabled for the /webservice directory.
# If you are using a web application firewall like AWS WAF, StackPath, Barracuda, Cloudflare, Juniper, etc... try to temporary disable it to check if that's the cause. If so, you'll have to whitelist these endpoints: login/token.php, webservice/*, lib/ajax/*, media/player/vimeo/wsplayer.php and /tokenpluginfile.php
You can also add WAF rules to allow traffic by detecting the app user agent such as: (http.user_agent contains "MoodleMobile")
If you still have a problem, please post in the [https://moodle.org/mod/forum/view.php?id=7798 Moodle for mobile forum].

If the issue started after updating Moodle LMS please visit [https://docs.moodle.org/en/Moodle_app_FAQ#After_updating_Moodle_LMS_to_a_recent_version_my_users_cannot_login After updating Moodle LMS to a recent version my users cannot login].

=== I cannot access with old users, but I can with recently created ones! ===
Please, do a "Purge all caches" via the Moodle administration settings, this will solve the problem.
===I can't view the courses tab as an administrator===
The Moodle app only displays courses you are enrolled in. If you want to view a course as an admin, you need to enrol in it.
===My Moodle site uses a SSO auth method (Shibboleth, Google OAuth, etc) and the app is not working===
See the section 'Mobile authentication' in the [[Moodle app guide for admins]] for details of how to configure it.

If configured the app is still not connecting: If your site uses an SSL certificate, it must be a trusted certificate, not self-signed. Please use this tool or a similar one to check that your certificate is fine: [https://www.geocerts.com/ssl_checker SSL Checker]. All the checks must be OK, including the "Certificate Chain Complete".

If your SSO method is unable to authenticate when using an "embedded browser" (it gives an authentication error), please check if it works with a "browser window". If it does work with the browser window then it means your SSO is performing an HTTP redirect, and these kind of redirects aren't supported by the app (the request is redirected by the browser not passing the POST parameters). Unfortunately, this is something we cannot control in the Mobile app (it can't be handled via JavaScript). For further information, see http://stackoverflow.com/questions/228225/prevent-redirection-of-xmlhttprequest and http://stackoverflow.com/questions/4168784/ajax-redirection-handling

There are only 2 possible solutions: set the authentication via a "browser window" instead of an embedded one (please notice this won't work in the Linux desktop app), or remove the redirect from the SSO auth method.

===SSO is not working with my custom auth plugin===
SSO should work in any plugin if the plugin handles correctly the $SESSION->wantsurl, this is the way SSO works when it is launched via the app:
* It launchs this URL https://yourmoodle/admin/tool/mobile/launch.php?service=local_mobile&passport=abc in the device browser
* If the user is not logged in, the browser will redirect the user to the login page
* If the auth plugin used implements correctly the handling of the wantsurl session var, once the user has logged in, the browser should redirect back to the https://yourmoodle/admin/tool/mobile/launch.php?service=local_mobile&passport=abc URL that will launch the mobile app via the custom URL protocol
Custom auth plugins may be failing in the last step,not redirecting back to tool/mobile, this will happen only if the plugin does not support correctly the $SESSION->wantsurl.

The SAML plugin works correctly but some modifications of that plugin may not work if important lines are changed.
===I am having problems requesting an airnotifier access key===
If you have registered your site but are still unable to request an access key, please register your site on the Moodle Apps Portal https://apps.moodle.com once your site is registered there, an Airnotifier access key will be automatically generated for you.
=== Push notifications are not working ===
Please check [[Mobile app notifications#Troubleshooting]]
=== How notifications icon badges are updated ===
'''Android''': Not all Android devices support icon badges so in some cases badges will never display numbers, also, depending on the device only a badge indicating that there are new notifications will be displayed when receiving a Push notification when the app is not in the foreground.

'''iOS''': The icon badge counter is only updated when the app is open and it will reflect the number of notifications pending reading or the number of message senders that sent you a message you have not read yet

In general, for iOS the icon badge displayed number should match the one displayed at the bottom of the app (or it should be the sum of the notifications and messages badges) and is not an indicator of the number of Push notifications the user has received, it acts as a reminder of pending notifications to be read that only gets updated when the user open the apps

There is an open issue to improve the behaviour on iOS, please watch MDL-73707
=== I configured 'QR code access' to automatic login, but the app still asks for credentials ===
Automatic authentication only works for Premium sites. You can see the app plans [https://moodle.com/app/ in this site].

If you're getting an error saying that the device you're using to connect isn't in the same network as the device that displays the QR code but both devices are connected to the same network, please check the section: [[#ipmismatch:_.27Client_IP_address_mismatch.27|ipmissmatch: 'Client IP address mismatch']].

=== I can log in on my Moodle site but I see a blank page or the app styles broken ===
This is usually because your Moodle site has a customised CSS.

Please try leaving empty CSS (''mobilecssurl'') on Site administration > Mobile app > Mobile appearance. If that works, please read [https://docs.moodle.org/dev/Moodle_App_Remote_Themes Moodle App Remote Themes] and create a new CSS file using the variables mentioned there

===The Moodle app does not connect to MoodleBox (or other internal self-hosted systems)===
You will need to disable SSL to make the app works, please see this forum discussion for more information: https://moodle.org/mod/forum/discuss.php?d=424353#p1739474
===I think I found a bug with the app. Where can I report it?===
# Log in to the [https://tracker.moodle.org/browse/MOBILE Moodle Mobile tracker] (you'll need to [http://tracker.moodle.org/secure/Signup%21default.jspa create a tracker account] if you've not done so previously)
# Check whether the issue has already been reported by doing a [https://tracker.moodle.org/issues/?jql=project%20%3D%20MOBILE search]
# If not, report the bug by clicking the 'Create Issue' link at the top right of the page, selecting 'Moodle app' as the project
# Add a detailed description providing as much information as possible (Moodle version, app version, device model and operating system, etc...), then click the Create button
===How can I get the app in my language?===
[[File:setting the app lang.png|thumb|100px|Setting your language]]
The Moodle app automatically detects your mobile's language and displays in the same language (if the translation exists). Otherwise, you can set the app language in App settings > General.

See also a post explaining how multi-lang works in the Moodle app: [https://moodle.org/mod/forum/discuss.php?d=453445#p1825637 Re: Language selector missing in Moodle app]

If the Moodle app is not yet available in your language, please contribute a translation! See [https://docs.moodle.org/dev/Translating%20Moodle%20Mobile Translating Moodle Mobile] for details of what to do.

=== Changes made to a Moodle site URL can cause logged-in users’ data to fail when synchronising. ===
We recommend that administrators manually log out all users after a site rename. If your site URL changes and have site users that are using the mobile Moodle App we suggest the following:
* For users that have not yet logged in - we recommend sending them the new URL
* For users already using the mobile Moodle App and potentially logged in request them to:
** log out of the mobile Moodle App,
** delete the old site, and
** log in using the new URL
Logged in Moodle users can continue working with the previous URL (with cached information) but they will not be able to synchronise the new information (therefore not receiving new information from their teachers, and teachers not receiving data or submissions from those students).
* To avoid the risk of data not synchronising, we recommend the site administrator logs out all app users, by manually deleting their tokens:
** Go to Site administration
** Click Server
** Click Web services
** Click Manage tokens
** Delete the tokens
Take into account that you still need to request your users to log in using the new URL.

=== Embedded content is not working ===

This could be caused because your site is using a Content-Security-Policy that is preventing the app from embedding content.

You can easily detect this when an error like this is displayed (javascript console): Refused to load URL because it does not appear in the frame-ancestors directive of the Content Security Policy.

If that's the case, you'd need to add the following elements: http://localhost moodleappfs://localhost at the end of the "Content-Security-Policy" HTTP header:

An example of a CSP allowing embedding Vimeo videos in the site and content in the app:
Content-Security-Policy: frame-ancestors 'self' https://*.vimeocdn.com https://*.vimeows.com https://*.vimeo.com http://localhost moodleappfs://localhost ;

Other type of embedded content that does not work is content hosted by Microsoft tools that require session or any type of authentication, such as SharePoint content.

=== Some activities are displayed incorrectly (blank, just a vertical line, ..) on the app ===
Please visit the forum post [[https://moodle.org/mod/forum/discuss.php?d=461909#p1854918| Some lesson activities do not display at all]].

=== Does the mobile app work on HarmonyOS devices such as Huawei? ===

The Moodle mobile app only officially supports Android and iOS operating systems; we cannot guarantee it will work on derived distributions.

What we can guarantee is that Push Notifications won't work as they depend on Google Play services (Firebase Cloud Messaging)

==Error messages==
=== 'Coding error: version.php file is missing for the component' ===
This error message indicates that that plugin is not correctly installed (or uninstalled) on the Moodle site you use (see [[Installing plugins]]). Please review the mod/certificate folder to check if the version.php file is missing (or has incorrect permissions) as well as purge cache too.
=== 'Can not find data record in database table external_functions' ===
This error usually happens due to a bad configuration or setting value in your Moodle site, please check:
# The user quota global setting should be an integer. For more details, see the discussion [https://moodle.org/mod/forum/discuss.php?d=320873 How to enable Moodle Mobile App for all accounts].
# The ''usermaxuploadfilesize'' should be an integer, please try to decrease the size. It can be configured in ''Site Administration > Security > Site Policies > Maximum uploaded file size''. The default value (Site upload limit) depends on the PHP configuration, you might have to change the value of ''upload_max_filesize'' and ''post_max_size'' in your ''php.ini'' file.
# The user "lang" field in the database is set to a correct value and existing language installed in the site. Some times the lang field is set via external systems to incorrect values or pointing to a language pack that was uninstalled. Please, note that to fix this you need direct access to the database and your 'user' and 'course' table.
==='Cannot connect: Verify that you have typed correctly the URL and that your site uses Moodle 3.5 or later'===
Take into account that the app will only connect to Moodle LMS sites version 3.5 onward.
Please also check:
# Mobile services are enabled for the site.
# The user is entering the correct URL for the site (see FAQ above)
# For https sites, the certificate is valid (see FAQ above)
==='Invalid Moodle site version. The Moodle app only supports Moodle systems 3.5 onwards'===
The app will only connect to Moodle LMS sites version 3.5 onward (see [https://docs.moodle.org/35/en/Upgrading Upgrade to 3.5] as well as [[Upgrade overview]]).
==='We lost connection; you need to reconnect. Your token is now invalid.' on my custom version of the Moodle app ===
Please check:
# You have followed all the steps listed in [https://docs.moodle.org/dev/Moodle%20Mobile%20Developing%20a%20plugin%20tutorial Moodle Mobile Developing a plugin tutorial]
# You have enabled the [[Capabilities/moodle/webservice:createtoken|moodle/webservice:createtoken]] for the authenticated user
==='No permission to create web service token for the service local_mobile' when attempting to log in (any user that it is not an admin)===
Please check you have enabled the moodle/webservice:createtoken for the authenticated user or any global role you want to allow to use the mobile app
==='No permission to create web service token for the service local_mobile' when attempting to log in as an admin===
You need to create a token for the admin account (only) as follows:
# Go to ''Site administration > Plugins > Web services > Manage tokens''
# Click Add
# Enter the admin username and select 'Moodle app additional features service' (i.e. do NOT leave it as 'Moodle app web service')
# Click the 'Save changes' button.
==='Invalid response value detected' when accessing the site ===
The user quota global setting should be an integer. For more details, see the discussion [https://moodle.org/mod/forum/discuss.php?d=320873 How to enable Moodle Mobile App for all accounts].
=== ' Invalid response value detected: Invalid external api response: the value is "", the server was expecting "raw" type" ===
This usually happens when there is a field with value NULL in a table in the database that should not be there. This may happen if your Moodle has been upgraded over many years and the database schema is broken.

To fix it, you can do the following:
* Detect the field that is causing the problem (it should be indicated before the error message)
* Fix the field, for example, for the password field in the lesson table: UPDATE mdl_lesson SET password = '' WHERE password IS NULL (remember that your table prefix can be different than mdl_)
==='Invalid response value detected' when accessing My Courses or Course Overview ===
This usually happens when a course uses a language that isn't installed in the site. Please make sure that all courses use valid languages. This can be easily checked in the database, table "course", there is a column named "lang".
==='A required parameter (username) was missing'===
This may happen if your site implements HTTP redirects; the request is redirected by the browser not passing the POST parameters.

Unfortunately, this is something we cannot control in the Mobile app (it can't be handled via JavaScript). For further information, see http://stackoverflow.com/questions/228225/prevent-redirection-of-xmlhttprequest and http://stackoverflow.com/questions/4168784/ajax-redirection-handling

The solution is to change the HTTP redirect and use an HTML page with a meta tag or JavaScript redirect.
==='Cannot get course contents'===
This usually happens when the course is using a course format plugin that was uninstalled from the server or that was not properly installed.

Please, reinstall again the course format plugin.
==='Access control exception' or 'Your authentication token is invalid or has expired'===
Please double-check that 'Enable web services for mobile devices' (''enablemobilewebservice'') is actually enabled. (It might be unabled if for example you have reseted some roles.)

If this error appears as soon as you enter the username and password for a new site, then it probably means that the token expiration time is badly configured. This is how to fix it:
# Go to ''Site administration > Security > Site security settings''.
# Find the setting named ''User created token duration''.
# If the value is set to 0 or it's too low, please set it back to a valid value (the default value is 12 weeks).
# Click the 'Save changes' button.

===ipmismatch: 'Client IP address mismatch'===
This error can appear when a user opens your site in a browser while using the app. This happens if your site is behind a proxy and you're using one of these Moodle versions o higher: 3.5.11, 3.6.9, 3.7.5, 3.8.2, 3.9.0.

To fix it:
# Go to ''Site administration > Administration > Server > HTTP''.
# Find the setting named ''Ignore reverse proxies'' (reverseproxyignore).
# Enter the IP of your proxy (or range of IPs).
# Click the 'Save changes' button.
If you are still experiencing issues please try to change this setting "getremoteaddrconf" (Logged IP address source) to the different existing values.

Finally, it is possible to disable the IP restriction checks for functionality such as the QR login, to do that, go to Site administration > Mobile app > Mobile app authentication, and disable the "QR authentication same IP check" setting.
=== 'The param "includestealthmodules" is invalid' ===
Please contact your learning organisation so they upgrade to at least Moodle 3.5.3 (see [https://docs.moodle.org/35/en/Upgrading Upgrade to 3.5] as well as [[Upgrade overview]]) or they manually apply the patch listed here [[MDL-63542]].

==Older versions of the Moodle app==
We always recommend using the last version of the Moodle App but some times users are still using older versions this is the reason we are keeping this list:

=== Some users are asked to reauthenticate too often when they browse the site (Moodle App <3.9.3) ===
This can happen if the app is sending too many variables to a WebService, e.g. because a course has a large number of sections and/or activities. This error was fixed in the 3.9.3 version of the app, but if you are using an older version of the app you can increase the value of ''max_input_vars'' in ''php.ini'' to fix it in your server.

=== After upgrading to 3.9.5 some of my plugins have stopped working ===
The Moodle App 3.9.5 version came with some breaking changes for plugins, most of the existing plugins have been updated to support the new changes.
Please check the following list of plugins that should work for 3.9.5 once you have upgraded to the latest version indicated in the document: https://docs.google.com/spreadsheets/d/1E9PqcUBpp9SAfQc_zJtX5tf9GeS3UN76A85IrrB4UDw/edit#gid=0

==Any further questions?==
Please post in the [http://moodle.org/mod/forum/view.php?id=7798 Moodle for mobile forum] on moodle.org.

[[Category:FAQ]]

[[de:Moodle Mobile - FAQ]]
[[ca:Moodle Mobile FAQ]]
[[es:Moodle app FAQ]]
[[fr:Moodle pour les mobiles]]
[[ja:バイルMoodle FAQ]]

Moodle app plans

2025-11-06T07:51:09Z

Jleyva: /* Additional features available */

{{Mobile}}
Our mobile application is absolutely free for end users, including students and teachers. They have unrestricted access to all the features they need to access courses, at no cost.

However, organisations can [https://apps.moodle.com/local/apps/signup_site.php?plan=premium&origin=moodledocs subscribe to our Premium plan, or purchase a Branded Moodle App (BMA)]. These options provide additional, exclusive features to enhance their Moodle experience.

By subscribing to a plan or purchasing a BMA, organisations also contribute to Moodle's sustainability.
== Free plan ==
The free plan is enabled by default for all Moodle Sites. It provides the most common functionality for students. Certain advanced functionalities are restricted, but organisations can enable them by upgrading to a Premium Plan.

'''What’s included in the Free plan?'''
* Compatible with most Moodle sites, except sites hosted by non-official partners or service providers.
* Access to all course content and most of the features for students available in LMS.
* 50 active devices for push notifications.
* Access to 2 offline courses per device per site.
* Customisable app features via Moodle site administration:
** 1 custom menu item.
** 1 disabled feature.
** 10 custom language strings.
== Premium plan ==
The Premium plan includes all the features of the free plan, plus basic branding customisation, Multimedia Push notifications, the possibility of finding your site by name, QR and Biometric login, Matomo analytics support options and unlimited devices for push notifications and offline courses.

'''What’s included in the Premium plan?'''

Compatible with most Moodle sites.
* [[#Basic_branding|Basic branding]].
* [[#Multimedia_Push_notifications|Multimedia Push notifications (Android only)]].
* [[#Custom_site_listing_in_search_results|Custom site listing in search results]].
* [[#QR_login|QR login]].
* [[#Biometric_login|Biometric login]].
* [[#Integration_with_Matomo_Analytics|Integration with Matomo Analytics]].
* [[#Active_devices_for_Push_notifications|Unlimited devices for push notifications]].
* [[#Offline_courses_per_device_per_site|Unlimited offline courses]].
* [[#Customisable_app_features_via_Moodle_LMS_site_administration|No limits to the app features that can be configured via Moodle LMS site administration]].

== Branded Moodle App (BMA) ==
A Branded Moodle App includes all features from Premium plans, and provides organisations with their own app on Google Play and App store. The app name, logo and branding can be customised to match the organisation's identity, creating a trusted and consistent learning experience.

=== Additional features available ===
* [[#Google_Analytics_for_Firebase_(BMA)|Your BMA can seamlessly connect with Google Analytics for Firebase]], providing you with valuable insights into user behaviour, engagement, and app usage patterns.
* [[#Custom_notifications_(BMA)|Custom notifications]]
* [[#Custom_download_page_(BMA)|Custom download page]]

For more information, see bellow a detailed description of the features and visit the [https://moodle.com/branded-app/ Branded Moodle App page at moodle.com].

For more information about the different subscription options visit the [https://apps.moodle.com Moodle Apps Portal].

== Moodle App features ==
The following features are available to organisations depending on the Moodle App plan they subscribe to.

=== Active devices for Push notifications ===
Calculated monthly, this is the number of unique user devices actively receiving push notifications from a Moodle site.

For example, for a site with 200 users enrolled and using the app with one device configured to receive push notifications, the potential number of active devices per month will be 200.

==== Multimedia Push notifications ====
For Android only, the Push notifications received by your users can include images. Similar messages will be grouped, for example, when receiving private messaging notifications. Requires activation via the Moodle Apps Portal.
=== Custom site listing in search results ===
Enable users to find your site by name when logging in to the app, removing the need to type the full URL of your site. You can configure how the results are displayed in the “Site finder” in the Moodle Apps Portal, including adding an image for your site and additional information.
=== QR login ===
Your users will be able to log in to the app by scanning a QR login, available on their Moodle site profile. Requires activation in your Moodle site's administration settings, and is compatible with Moodle LMS 3.9 and later.
=== Biometric login ===
Streamline login for your users with fingerprint or Face ID authentication. For enhanced security, your users will be prompted to perform a regular standard login at intervals determined by your Moodle site's security settings. Requires activation via the Moodle Apps Portal, and individual user setup.
=== Offline courses per device per site ===
This feature allows users to download entire courses for offline access. Depending on the app plan, there will be varying limits on the number of courses users can download.

The amount of individual activities and resources that users are allowed to download is unlimited.
=== Basic branding ===
Using an online tool in the Moodle Apps Portal, organisations can customise the colour palette of their site in the Moodle App (including the login screen). Requires activation via the Moodle Apps Portal.
=== Integration with Matomo Analytics ===
Organisations with Matomo Analytics integrated into their Moodle site can extend tracking capabilities to the app. To use this integration, you need to have your own instance of Matomo.

Requires activation via the Moodle Apps Portal. For details, see the [[Moodle app guide for admins]].
=== Customisable app features via Moodle LMS site administration ===
Certain app functionality can be configured via the Moodle site. App configuration options vary depending on your subscription plan.
* Custom menu items: you can add your own links within the Moodle app menu. Your custom links will be available via the 'more' menu (the three-dot ⋯ menu at the bottom of the app).
* Disabled features: you can select which Moodle features, such as blocks or modules, won’t be available on your app.
* Custom language strings: you can customise the app's language strings.
For more details, visit [[Moodle app guide for admins]].
=== Google Analytics for Firebase (BMA) ===
Google Analytics for Firebase is a free tool that provides valuable insights and data about how users interact with mobile apps. For compliance with GDPR, users will be able to disable it at any time.

=== Custom notifications (BMA) ===
[[File:Captura de pantalla 2023-12-01 a las 11.13.19.png|thumb|200px]]
A tool available at the "Apps portal" will allow you to send customised Push notifications to all the active users of your Branded Moodle App.

You will be able to provide a title, message and additional information in HTML format for your notifications. For Android users, it will be also possible to include a descriptive icon and image.

=== Custom download page (BMA) ===
[[File:BMA Custom Download Page.png|thumb|200px]]
A tool available at the "Apps portal" will allow you to create a custom download page for your app by just providing the "App name" you want to display, a description and a descriptive image.

[https://apps.moodle.com/local/apps/download.php?id=com.moodle.bcnacademy See the example here].

== See also ==
* [https://support.moodle.com/support/solutions/folders/80000686596 FAQ for plans]
* [https://support.moodle.com/support/solutions/folders/80000686597 FAQ for BMA]
* [[Moodle app guide for admins]]

[[es:Planes de Moodle app]]

Moodle app plans

2025-11-06T07:50:35Z

Jleyva: /* Branded Moodle App (BMA) */

{{Mobile}}
Our mobile application is absolutely free for end users, including students and teachers. They have unrestricted access to all the features they need to access courses, at no cost.

However, organisations can [https://apps.moodle.com/local/apps/signup_site.php?plan=premium&origin=moodledocs subscribe to our Premium plan, or purchase a Branded Moodle App (BMA)]. These options provide additional, exclusive features to enhance their Moodle experience.

By subscribing to a plan or purchasing a BMA, organisations also contribute to Moodle's sustainability.
== Free plan ==
The free plan is enabled by default for all Moodle Sites. It provides the most common functionality for students. Certain advanced functionalities are restricted, but organisations can enable them by upgrading to a Premium Plan.

'''What’s included in the Free plan?'''
* Compatible with most Moodle sites, except sites hosted by non-official partners or service providers.
* Access to all course content and most of the features for students available in LMS.
* 50 active devices for push notifications.
* Access to 2 offline courses per device per site.
* Customisable app features via Moodle site administration:
** 1 custom menu item.
** 1 disabled feature.
** 10 custom language strings.
== Premium plan ==
The Premium plan includes all the features of the free plan, plus basic branding customisation, Multimedia Push notifications, the possibility of finding your site by name, QR and Biometric login, Matomo analytics support options and unlimited devices for push notifications and offline courses.

'''What’s included in the Premium plan?'''

Compatible with most Moodle sites.
* [[#Basic_branding|Basic branding]].
* [[#Multimedia_Push_notifications|Multimedia Push notifications (Android only)]].
* [[#Custom_site_listing_in_search_results|Custom site listing in search results]].
* [[#QR_login|QR login]].
* [[#Biometric_login|Biometric login]].
* [[#Integration_with_Matomo_Analytics|Integration with Matomo Analytics]].
* [[#Active_devices_for_Push_notifications|Unlimited devices for push notifications]].
* [[#Offline_courses_per_device_per_site|Unlimited offline courses]].
* [[#Customisable_app_features_via_Moodle_LMS_site_administration|No limits to the app features that can be configured via Moodle LMS site administration]].

== Branded Moodle App (BMA) ==
A Branded Moodle App includes all features from Premium plans, and provides organisations with their own app on Google Play and App store. The app name, logo and branding can be customised to match the organisation's identity, creating a trusted and consistent learning experience.

=== Additional features available ===
* [[#Google_Analytics_for_Firebase_(BMA)|Your BMA can seamlessly connect with Google Analytics for Firebase, providing you with valuable insights into user behaviour, engagement, and app usage patterns.]]
* [[#Custom_notifications_(BMA)|Custom notifications]]
* [[#Custom_download_page_(BMA)|Custom download page]]

For more information, see bellow a detailed description of the features and visit the [https://moodle.com/branded-app/ Branded Moodle App page at moodle.com].

For more information about the different subscription options visit the [https://apps.moodle.com Moodle Apps Portal].

== Moodle App features ==
The following features are available to organisations depending on the Moodle App plan they subscribe to.

=== Active devices for Push notifications ===
Calculated monthly, this is the number of unique user devices actively receiving push notifications from a Moodle site.

For example, for a site with 200 users enrolled and using the app with one device configured to receive push notifications, the potential number of active devices per month will be 200.

==== Multimedia Push notifications ====
For Android only, the Push notifications received by your users can include images. Similar messages will be grouped, for example, when receiving private messaging notifications. Requires activation via the Moodle Apps Portal.
=== Custom site listing in search results ===
Enable users to find your site by name when logging in to the app, removing the need to type the full URL of your site. You can configure how the results are displayed in the “Site finder” in the Moodle Apps Portal, including adding an image for your site and additional information.
=== QR login ===
Your users will be able to log in to the app by scanning a QR login, available on their Moodle site profile. Requires activation in your Moodle site's administration settings, and is compatible with Moodle LMS 3.9 and later.
=== Biometric login ===
Streamline login for your users with fingerprint or Face ID authentication. For enhanced security, your users will be prompted to perform a regular standard login at intervals determined by your Moodle site's security settings. Requires activation via the Moodle Apps Portal, and individual user setup.
=== Offline courses per device per site ===
This feature allows users to download entire courses for offline access. Depending on the app plan, there will be varying limits on the number of courses users can download.

The amount of individual activities and resources that users are allowed to download is unlimited.
=== Basic branding ===
Using an online tool in the Moodle Apps Portal, organisations can customise the colour palette of their site in the Moodle App (including the login screen). Requires activation via the Moodle Apps Portal.
=== Integration with Matomo Analytics ===
Organisations with Matomo Analytics integrated into their Moodle site can extend tracking capabilities to the app. To use this integration, you need to have your own instance of Matomo.

Requires activation via the Moodle Apps Portal. For details, see the [[Moodle app guide for admins]].
=== Customisable app features via Moodle LMS site administration ===
Certain app functionality can be configured via the Moodle site. App configuration options vary depending on your subscription plan.
* Custom menu items: you can add your own links within the Moodle app menu. Your custom links will be available via the 'more' menu (the three-dot ⋯ menu at the bottom of the app).
* Disabled features: you can select which Moodle features, such as blocks or modules, won’t be available on your app.
* Custom language strings: you can customise the app's language strings.
For more details, visit [[Moodle app guide for admins]].
=== Google Analytics for Firebase (BMA) ===
Google Analytics for Firebase is a free tool that provides valuable insights and data about how users interact with mobile apps. For compliance with GDPR, users will be able to disable it at any time.

=== Custom notifications (BMA) ===
[[File:Captura de pantalla 2023-12-01 a las 11.13.19.png|thumb|200px]]
A tool available at the "Apps portal" will allow you to send customised Push notifications to all the active users of your Branded Moodle App.

You will be able to provide a title, message and additional information in HTML format for your notifications. For Android users, it will be also possible to include a descriptive icon and image.

=== Custom download page (BMA) ===
[[File:BMA Custom Download Page.png|thumb|200px]]
A tool available at the "Apps portal" will allow you to create a custom download page for your app by just providing the "App name" you want to display, a description and a descriptive image.

[https://apps.moodle.com/local/apps/download.php?id=com.moodle.bcnacademy See the example here].

== See also ==
* [https://support.moodle.com/support/solutions/folders/80000686596 FAQ for plans]
* [https://support.moodle.com/support/solutions/folders/80000686597 FAQ for BMA]
* [[Moodle app guide for admins]]

[[es:Planes de Moodle app]]

Moodle app plans

2025-11-06T07:48:41Z

Jleyva: /* Branded Moodle App (BMA) */

{{Mobile}}
Our mobile application is absolutely free for end users, including students and teachers. They have unrestricted access to all the features they need to access courses, at no cost.

However, organisations can [https://apps.moodle.com/local/apps/signup_site.php?plan=premium&origin=moodledocs subscribe to our Premium plan, or purchase a Branded Moodle App (BMA)]. These options provide additional, exclusive features to enhance their Moodle experience.

By subscribing to a plan or purchasing a BMA, organisations also contribute to Moodle's sustainability.
== Free plan ==
The free plan is enabled by default for all Moodle Sites. It provides the most common functionality for students. Certain advanced functionalities are restricted, but organisations can enable them by upgrading to a Premium Plan.

'''What’s included in the Free plan?'''
* Compatible with most Moodle sites, except sites hosted by non-official partners or service providers.
* Access to all course content and most of the features for students available in LMS.
* 50 active devices for push notifications.
* Access to 2 offline courses per device per site.
* Customisable app features via Moodle site administration:
** 1 custom menu item.
** 1 disabled feature.
** 10 custom language strings.
== Premium plan ==
The Premium plan includes all the features of the free plan, plus basic branding customisation, Multimedia Push notifications, the possibility of finding your site by name, QR and Biometric login, Matomo analytics support options and unlimited devices for push notifications and offline courses.

'''What’s included in the Premium plan?'''

Compatible with most Moodle sites.
* [[#Basic_branding|Basic branding]].
* [[#Multimedia_Push_notifications|Multimedia Push notifications (Android only)]].
* [[#Custom_site_listing_in_search_results|Custom site listing in search results]].
* [[#QR_login|QR login]].
* [[#Biometric_login|Biometric login]].
* [[#Integration_with_Matomo_Analytics|Integration with Matomo Analytics]].
* [[#Active_devices_for_Push_notifications|Unlimited devices for push notifications]].
* [[#Offline_courses_per_device_per_site|Unlimited offline courses]].
* [[#Customisable_app_features_via_Moodle_LMS_site_administration|No limits to the app features that can be configured via Moodle LMS site administration]].

== Branded Moodle App (BMA) ==
A Branded Moodle App includes all features from Premium plans, and provides organisations with their own app on Google Play and App store. The app name, logo and branding can be customised to match the organisation's identity, creating a trusted and consistent learning experience.

=== Additional features available ===
* Your BMA can seamlessly connect with Google Analytics for Firebase, providing you with valuable insights into user behaviour, engagement, and app usage patterns.
* Custom notifications
* Custom download page

For more information, see bellow a detailed description of the features and visit the [https://moodle.com/branded-app/ Branded Moodle App page at moodle.com].

For more information about the different subscription options visit the [https://apps.moodle.com Moodle Apps Portal].

== Moodle App features ==
The following features are available to organisations depending on the Moodle App plan they subscribe to.

=== Active devices for Push notifications ===
Calculated monthly, this is the number of unique user devices actively receiving push notifications from a Moodle site.

For example, for a site with 200 users enrolled and using the app with one device configured to receive push notifications, the potential number of active devices per month will be 200.

==== Multimedia Push notifications ====
For Android only, the Push notifications received by your users can include images. Similar messages will be grouped, for example, when receiving private messaging notifications. Requires activation via the Moodle Apps Portal.
=== Custom site listing in search results ===
Enable users to find your site by name when logging in to the app, removing the need to type the full URL of your site. You can configure how the results are displayed in the “Site finder” in the Moodle Apps Portal, including adding an image for your site and additional information.
=== QR login ===
Your users will be able to log in to the app by scanning a QR login, available on their Moodle site profile. Requires activation in your Moodle site's administration settings, and is compatible with Moodle LMS 3.9 and later.
=== Biometric login ===
Streamline login for your users with fingerprint or Face ID authentication. For enhanced security, your users will be prompted to perform a regular standard login at intervals determined by your Moodle site's security settings. Requires activation via the Moodle Apps Portal, and individual user setup.
=== Offline courses per device per site ===
This feature allows users to download entire courses for offline access. Depending on the app plan, there will be varying limits on the number of courses users can download.

The amount of individual activities and resources that users are allowed to download is unlimited.
=== Basic branding ===
Using an online tool in the Moodle Apps Portal, organisations can customise the colour palette of their site in the Moodle App (including the login screen). Requires activation via the Moodle Apps Portal.
=== Integration with Matomo Analytics ===
Organisations with Matomo Analytics integrated into their Moodle site can extend tracking capabilities to the app. To use this integration, you need to have your own instance of Matomo.

Requires activation via the Moodle Apps Portal. For details, see the [[Moodle app guide for admins]].
=== Customisable app features via Moodle LMS site administration ===
Certain app functionality can be configured via the Moodle site. App configuration options vary depending on your subscription plan.
* Custom menu items: you can add your own links within the Moodle app menu. Your custom links will be available via the 'more' menu (the three-dot ⋯ menu at the bottom of the app).
* Disabled features: you can select which Moodle features, such as blocks or modules, won’t be available on your app.
* Custom language strings: you can customise the app's language strings.
For more details, visit [[Moodle app guide for admins]].
=== Google Analytics for Firebase (BMA) ===
Google Analytics for Firebase is a free tool that provides valuable insights and data about how users interact with mobile apps. For compliance with GDPR, users will be able to disable it at any time.

=== Custom notifications (BMA) ===
[[File:Captura de pantalla 2023-12-01 a las 11.13.19.png|thumb|200px]]
A tool available at the "Apps portal" will allow you to send customised Push notifications to all the active users of your Branded Moodle App.

You will be able to provide a title, message and additional information in HTML format for your notifications. For Android users, it will be also possible to include a descriptive icon and image.

=== Custom download page (BMA) ===
[[File:BMA Custom Download Page.png|thumb|200px]]
A tool available at the "Apps portal" will allow you to create a custom download page for your app by just providing the "App name" you want to display, a description and a descriptive image.

[https://apps.moodle.com/local/apps/download.php?id=com.moodle.bcnacademy See the example here].

== See also ==
* [https://support.moodle.com/support/solutions/folders/80000686596 FAQ for plans]
* [https://support.moodle.com/support/solutions/folders/80000686597 FAQ for BMA]
* [[Moodle app guide for admins]]

[[es:Planes de Moodle app]]

Moodle app plans

2025-11-06T07:48:25Z

Jleyva: /* Premium plan */

{{Mobile}}
Our mobile application is absolutely free for end users, including students and teachers. They have unrestricted access to all the features they need to access courses, at no cost.

However, organisations can [https://apps.moodle.com/local/apps/signup_site.php?plan=premium&origin=moodledocs subscribe to our Premium plan, or purchase a Branded Moodle App (BMA)]. These options provide additional, exclusive features to enhance their Moodle experience.

By subscribing to a plan or purchasing a BMA, organisations also contribute to Moodle's sustainability.
== Free plan ==
The free plan is enabled by default for all Moodle Sites. It provides the most common functionality for students. Certain advanced functionalities are restricted, but organisations can enable them by upgrading to a Premium Plan.

'''What’s included in the Free plan?'''
* Compatible with most Moodle sites, except sites hosted by non-official partners or service providers.
* Access to all course content and most of the features for students available in LMS.
* 50 active devices for push notifications.
* Access to 2 offline courses per device per site.
* Customisable app features via Moodle site administration:
** 1 custom menu item.
** 1 disabled feature.
** 10 custom language strings.
== Premium plan ==
The Premium plan includes all the features of the free plan, plus basic branding customisation, Multimedia Push notifications, the possibility of finding your site by name, QR and Biometric login, Matomo analytics support options and unlimited devices for push notifications and offline courses.

'''What’s included in the Premium plan?'''

Compatible with most Moodle sites.
* [[#Basic_branding|Basic branding]].
* [[#Multimedia_Push_notifications|Multimedia Push notifications (Android only)]].
* [[#Custom_site_listing_in_search_results|Custom site listing in search results]].
* [[#QR_login|QR login]].
* [[#Biometric_login|Biometric login]].
* [[#Integration_with_Matomo_Analytics|Integration with Matomo Analytics]].
* [[#Active_devices_for_Push_notifications|Unlimited devices for push notifications]].
* [[#Offline_courses_per_device_per_site|Unlimited offline courses]].
* [[#Customisable_app_features_via_Moodle_LMS_site_administration|No limits to the app features that can be configured via Moodle LMS site administration]].

== Branded Moodle App (BMA) ==
A Branded Moodle App includes all features from Premium plans, and provides organisations with their own app on Google Play and App store. The app name, logo and branding can be customised to match the organisation's identity, creating a trusted and consistent learning experience.

=== Additional features available ===
* Your BMA can seamlessly connect with Google Analytics for Firebase, providing you with valuable insights into user behaviour, engagement, and app usage patterns.
* Custom notifications
* Custom download page

For more information, see bellow a detailed description of the features and visit the [https://moodle.com/branded-app/ Branded Moodle App page at moodle.com].

For more information about the different subscription options visit the [https://apps.moodle.com Moodle Apps Portal].

== Moodle App features ==
The following features are available to organisations depending on the Moodle App plan they subscribe to.

=== Active devices for Push notifications ===
Calculated monthly, this is the number of unique user devices actively receiving push notifications from a Moodle site.

For example, for a site with 200 users enrolled and using the app with one device configured to receive push notifications, the potential number of active devices per month will be 200.

==== Multimedia Push notifications ====
For Android only, the Push notifications received by your users can include images. Similar messages will be grouped, for example, when receiving private messaging notifications. Requires activation via the Moodle Apps Portal.
=== Custom site listing in search results ===
Enable users to find your site by name when logging in to the app, removing the need to type the full URL of your site. You can configure how the results are displayed in the “Site finder” in the Moodle Apps Portal, including adding an image for your site and additional information.
=== QR login ===
Your users will be able to log in to the app by scanning a QR login, available on their Moodle site profile. Requires activation in your Moodle site's administration settings, and is compatible with Moodle LMS 3.9 and later.
=== Biometric login ===
Streamline login for your users with fingerprint or Face ID authentication. For enhanced security, your users will be prompted to perform a regular standard login at intervals determined by your Moodle site's security settings. Requires activation via the Moodle Apps Portal, and individual user setup.
=== Offline courses per device per site ===
This feature allows users to download entire courses for offline access. Depending on the app plan, there will be varying limits on the number of courses users can download.

The amount of individual activities and resources that users are allowed to download is unlimited.
=== Basic branding ===
Using an online tool in the Moodle Apps Portal, organisations can customise the colour palette of their site in the Moodle App (including the login screen). Requires activation via the Moodle Apps Portal.
=== Integration with Matomo Analytics ===
Organisations with Matomo Analytics integrated into their Moodle site can extend tracking capabilities to the app. To use this integration, you need to have your own instance of Matomo.

Requires activation via the Moodle Apps Portal. For details, see the [[Moodle app guide for admins]].
=== Customisable app features via Moodle LMS site administration ===
Certain app functionality can be configured via the Moodle site. App configuration options vary depending on your subscription plan.
* Custom menu items: you can add your own links within the Moodle app menu. Your custom links will be available via the 'more' menu (the three-dot ⋯ menu at the bottom of the app).
* Disabled features: you can select which Moodle features, such as blocks or modules, won’t be available on your app.
* Custom language strings: you can customise the app's language strings.
For more details, visit [[Moodle app guide for admins]].
=== Google Analytics for Firebase (BMA) ===
Google Analytics for Firebase is a free tool that provides valuable insights and data about how users interact with mobile apps. For compliance with GDPR, users will be able to disable it at any time.

=== Custom notifications (BMA) ===
[[File:Captura de pantalla 2023-12-01 a las 11.13.19.png|thumb|200px]]
A tool available at the "Apps portal" will allow you to send customised Push notifications to all the active users of your Branded Moodle App.

You will be able to provide a title, message and additional information in HTML format for your notifications. For Android users, it will be also possible to include a descriptive icon and image.

=== Custom download page (BMA) ===
[[File:BMA Custom Download Page.png|thumb|200px]]
A tool available at the "Apps portal" will allow you to create a custom download page for your app by just providing the "App name" you want to display, a description and a descriptive image.

[https://apps.moodle.com/local/apps/download.php?id=com.moodle.bcnacademy See the example here].

== See also ==
* [https://support.moodle.com/support/solutions/folders/80000686596 FAQ for plans]
* [https://support.moodle.com/support/solutions/folders/80000686597 FAQ for BMA]
* [[Moodle app guide for admins]]

[[es:Planes de Moodle app]]

Moodle app plans

2025-11-06T07:44:42Z

Jleyva: /* Premium plan */

{{Mobile}}
Our mobile application is absolutely free for end users, including students and teachers. They have unrestricted access to all the features they need to access courses, at no cost.

However, organisations can [https://apps.moodle.com/local/apps/signup_site.php?plan=premium&origin=moodledocs subscribe to our Premium plan, or purchase a Branded Moodle App (BMA)]. These options provide additional, exclusive features to enhance their Moodle experience.

By subscribing to a plan or purchasing a BMA, organisations also contribute to Moodle's sustainability.
== Free plan ==
The free plan is enabled by default for all Moodle Sites. It provides the most common functionality for students. Certain advanced functionalities are restricted, but organisations can enable them by upgrading to a Premium Plan.

'''What’s included in the Free plan?'''
* Compatible with most Moodle sites, except sites hosted by non-official partners or service providers.
* Access to all course content and most of the features for students available in LMS.
* 50 active devices for push notifications.
* Access to 2 offline courses per device per site.
* Customisable app features via Moodle site administration:
** 1 custom menu item.
** 1 disabled feature.
** 10 custom language strings.
== Premium plan ==
The Premium plan includes all the features of the free plan, plus basic branding customisation, Multimedia Push notifications, the possibility of finding your site by name, QR and Biometric login, Matomo analytics support options and unlimited devices for push notifications and offline courses.

'''What’s included in the Premium plan?'''

Compatible with most Moodle sites.
* [[#Basic_branding|Basic branding]].
* Multimedia Push notifications (Android only).
* Custom site listing in search results.
* QR login.
* Biometric login.
* Integration with Matomo Analytics.
* Unlimited devices for push notifications.
* Unlimited offline courses.
* No limits to the app features that can be configured via Moodle LMS site administration.

== Branded Moodle App (BMA) ==
A Branded Moodle App includes all features from Premium plans, and provides organisations with their own app on Google Play and App store. The app name, logo and branding can be customised to match the organisation's identity, creating a trusted and consistent learning experience.

=== Additional features available ===
* Your BMA can seamlessly connect with Google Analytics for Firebase, providing you with valuable insights into user behaviour, engagement, and app usage patterns.
* Custom notifications
* Custom download page

For more information, see bellow a detailed description of the features and visit the [https://moodle.com/branded-app/ Branded Moodle App page at moodle.com].

For more information about the different subscription options visit the [https://apps.moodle.com Moodle Apps Portal].

== Moodle App features ==
The following features are available to organisations depending on the Moodle App plan they subscribe to.

=== Active devices for Push notifications ===
Calculated monthly, this is the number of unique user devices actively receiving push notifications from a Moodle site.

For example, for a site with 200 users enrolled and using the app with one device configured to receive push notifications, the potential number of active devices per month will be 200.

==== Multimedia Push notifications ====
For Android only, the Push notifications received by your users can include images. Similar messages will be grouped, for example, when receiving private messaging notifications. Requires activation via the Moodle Apps Portal.
=== Custom site listing in search results ===
Enable users to find your site by name when logging in to the app, removing the need to type the full URL of your site. You can configure how the results are displayed in the “Site finder” in the Moodle Apps Portal, including adding an image for your site and additional information.
=== QR login ===
Your users will be able to log in to the app by scanning a QR login, available on their Moodle site profile. Requires activation in your Moodle site's administration settings, and is compatible with Moodle LMS 3.9 and later.
=== Biometric login ===
Streamline login for your users with fingerprint or Face ID authentication. For enhanced security, your users will be prompted to perform a regular standard login at intervals determined by your Moodle site's security settings. Requires activation via the Moodle Apps Portal, and individual user setup.
=== Offline courses per device per site ===
This feature allows users to download entire courses for offline access. Depending on the app plan, there will be varying limits on the number of courses users can download.

The amount of individual activities and resources that users are allowed to download is unlimited.
=== Basic branding ===
Using an online tool in the Moodle Apps Portal, organisations can customise the colour palette of their site in the Moodle App (including the login screen). Requires activation via the Moodle Apps Portal.
=== Integration with Matomo Analytics ===
Organisations with Matomo Analytics integrated into their Moodle site can extend tracking capabilities to the app. To use this integration, you need to have your own instance of Matomo.

Requires activation via the Moodle Apps Portal. For details, see the [[Moodle app guide for admins]].
=== Customisable app features via Moodle LMS site administration ===
Certain app functionality can be configured via the Moodle site. App configuration options vary depending on your subscription plan.
* Custom menu items: you can add your own links within the Moodle app menu. Your custom links will be available via the 'more' menu (the three-dot ⋯ menu at the bottom of the app).
* Disabled features: you can select which Moodle features, such as blocks or modules, won’t be available on your app.
* Custom language strings: you can customise the app's language strings.
For more details, visit [[Moodle app guide for admins]].
=== Google Analytics for Firebase (BMA) ===
Google Analytics for Firebase is a free tool that provides valuable insights and data about how users interact with mobile apps. For compliance with GDPR, users will be able to disable it at any time.

=== Custom notifications (BMA) ===
[[File:Captura de pantalla 2023-12-01 a las 11.13.19.png|thumb|200px]]
A tool available at the "Apps portal" will allow you to send customised Push notifications to all the active users of your Branded Moodle App.

You will be able to provide a title, message and additional information in HTML format for your notifications. For Android users, it will be also possible to include a descriptive icon and image.

=== Custom download page (BMA) ===
[[File:BMA Custom Download Page.png|thumb|200px]]
A tool available at the "Apps portal" will allow you to create a custom download page for your app by just providing the "App name" you want to display, a description and a descriptive image.

[https://apps.moodle.com/local/apps/download.php?id=com.moodle.bcnacademy See the example here].

== See also ==
* [https://support.moodle.com/support/solutions/folders/80000686596 FAQ for plans]
* [https://support.moodle.com/support/solutions/folders/80000686597 FAQ for BMA]
* [[Moodle app guide for admins]]

[[es:Planes de Moodle app]]

Moodle app plans

2025-11-06T07:41:48Z

Jleyva:

{{Mobile}}
Our mobile application is absolutely free for end users, including students and teachers. They have unrestricted access to all the features they need to access courses, at no cost.

However, organisations can [https://apps.moodle.com/local/apps/signup_site.php?plan=premium&origin=moodledocs subscribe to our Premium plan, or purchase a Branded Moodle App (BMA)]. These options provide additional, exclusive features to enhance their Moodle experience.

By subscribing to a plan or purchasing a BMA, organisations also contribute to Moodle's sustainability.
== Free plan ==
The free plan is enabled by default for all Moodle Sites. It provides the most common functionality for students. Certain advanced functionalities are restricted, but organisations can enable them by upgrading to a Premium Plan.

'''What’s included in the Free plan?'''
* Compatible with most Moodle sites, except sites hosted by non-official partners or service providers.
* Access to all course content and most of the features for students available in LMS.
* 50 active devices for push notifications.
* Access to 2 offline courses per device per site.
* Customisable app features via Moodle site administration:
** 1 custom menu item.
** 1 disabled feature.
** 10 custom language strings.
== Premium plan ==
The Premium plan includes all the features of the free plan, plus basic branding customisation, Multimedia Push notifications, the possibility of finding your site by name, QR and Biometric login, Matomo analytics support options and unlimited devices for push notifications and offline courses.

'''What’s included in the Premium plan?'''

Compatible with most Moodle sites.
* Basic branding.
* Multimedia Push notifications (Android only).
* Custom site listing in search results.
* QR login.
* Biometric login.
* Integration with Matomo Analytics.
* Unlimited devices for push notifications.
* Unlimited offline courses.
* No limits to the app features that can be configured via Moodle LMS site administration.
== Branded Moodle App (BMA) ==
A Branded Moodle App includes all features from Premium plans, and provides organisations with their own app on Google Play and App store. The app name, logo and branding can be customised to match the organisation's identity, creating a trusted and consistent learning experience.

=== Additional features available ===
* Your BMA can seamlessly connect with Google Analytics for Firebase, providing you with valuable insights into user behaviour, engagement, and app usage patterns.
* Custom notifications
* Custom download page

For more information, see bellow a detailed description of the features and visit the [https://moodle.com/branded-app/ Branded Moodle App page at moodle.com].

For more information about the different subscription options visit the [https://apps.moodle.com Moodle Apps Portal].

== Moodle App features ==
The following features are available to organisations depending on the Moodle App plan they subscribe to.

=== Active devices for Push notifications ===
Calculated monthly, this is the number of unique user devices actively receiving push notifications from a Moodle site.

For example, for a site with 200 users enrolled and using the app with one device configured to receive push notifications, the potential number of active devices per month will be 200.

==== Multimedia Push notifications ====
For Android only, the Push notifications received by your users can include images. Similar messages will be grouped, for example, when receiving private messaging notifications. Requires activation via the Moodle Apps Portal.
=== Custom site listing in search results ===
Enable users to find your site by name when logging in to the app, removing the need to type the full URL of your site. You can configure how the results are displayed in the “Site finder” in the Moodle Apps Portal, including adding an image for your site and additional information.
=== QR login ===
Your users will be able to log in to the app by scanning a QR login, available on their Moodle site profile. Requires activation in your Moodle site's administration settings, and is compatible with Moodle LMS 3.9 and later.
=== Biometric login ===
Streamline login for your users with fingerprint or Face ID authentication. For enhanced security, your users will be prompted to perform a regular standard login at intervals determined by your Moodle site's security settings. Requires activation via the Moodle Apps Portal, and individual user setup.
=== Offline courses per device per site ===
This feature allows users to download entire courses for offline access. Depending on the app plan, there will be varying limits on the number of courses users can download.

The amount of individual activities and resources that users are allowed to download is unlimited.
=== Basic branding ===
Using an online tool in the Moodle Apps Portal, organisations can customise the colour palette of their site in the Moodle App (including the login screen). Requires activation via the Moodle Apps Portal.
=== Integration with Matomo Analytics ===
Organisations with Matomo Analytics integrated into their Moodle site can extend tracking capabilities to the app. To use this integration, you need to have your own instance of Matomo.

Requires activation via the Moodle Apps Portal. For details, see the [[Moodle app guide for admins]].
=== Customisable app features via Moodle LMS site administration ===
Certain app functionality can be configured via the Moodle site. App configuration options vary depending on your subscription plan.
* Custom menu items: you can add your own links within the Moodle app menu. Your custom links will be available via the 'more' menu (the three-dot ⋯ menu at the bottom of the app).
* Disabled features: you can select which Moodle features, such as blocks or modules, won’t be available on your app.
* Custom language strings: you can customise the app's language strings.
For more details, visit [[Moodle app guide for admins]].
=== Google Analytics for Firebase (BMA) ===
Google Analytics for Firebase is a free tool that provides valuable insights and data about how users interact with mobile apps. For compliance with GDPR, users will be able to disable it at any time.

=== Custom notifications (BMA) ===
[[File:Captura de pantalla 2023-12-01 a las 11.13.19.png|thumb|200px]]
A tool available at the "Apps portal" will allow you to send customised Push notifications to all the active users of your Branded Moodle App.

You will be able to provide a title, message and additional information in HTML format for your notifications. For Android users, it will be also possible to include a descriptive icon and image.

=== Custom download page (BMA) ===
[[File:BMA Custom Download Page.png|thumb|200px]]
A tool available at the "Apps portal" will allow you to create a custom download page for your app by just providing the "App name" you want to display, a description and a descriptive image.

[https://apps.moodle.com/local/apps/download.php?id=com.moodle.bcnacademy See the example here].

== See also ==
* [https://support.moodle.com/support/solutions/folders/80000686596 FAQ for plans]
* [https://support.moodle.com/support/solutions/folders/80000686597 FAQ for BMA]
* [[Moodle app guide for admins]]

[[es:Planes de Moodle app]]

Moodle app FAQ

2025-11-06T07:35:30Z

Jleyva: /* Administrators */

{{Mobile}}
==Students==
===How can I log in?===
To log in to your Moodle site with the Moodle App, you need the URL (web address) of the Moodle site that you’re trying to access. If your organisation has Search enabled, you can try searching by the name of your organisation or eLearning site.

If your organisation allows you to log in via QR code, you’ll find the QR code at the bottom of your user profile on your Moodle site. You just need to press “Scan QR code” on the app, scan the QR code on your profile and you’ll be logged in automatically.

If your organisation allows you to log in using face recognition or fingerprint, you can activate this in the App, going to User account > Preferences. You’ll need to have biometric authentication enabled in your own device’s settings.
===Who can I contact for help with the app?===
If you’re a student and need help with issues related to logging in, registering to a Moodle site or trouble connecting to the app, you should contact your school or learning organisation. For example, one of your teachers, or the person who takes care of Moodle.
Moodle HQ make the Moodle software and the Moodle app, but they don’t manage nor have access to your Moodle site or your user data.
===How can I get the Moodle app?===
You can download the Moodle App for free from [https://play.google.com/store/apps/details?id=com.moodle.moodlemobile Google Play] and the Apple [https://itunes.apple.com/app/moodle-mobile/id633359593?mt=8 App Store]. You will find it by searching “Moodle”, and the author/owner is “Moodle Pty Ltd”.
If you are unable to download the app from Google play, please visit [https://download.moodle.org/mobile/ Moodle app downloads]
===I can't get the app to work. ===
To ensure that the Moodle app functions properly, please double-check that you have correctly entered the URL address of the Moodle site you are using (please visit [https://docs.moodle.org/en/Moodle_app_FAQ#I_can%E2%80%99t_find_my_Moodle_site_in_the_app. I can’t find my Moodle site in the app]). If you are experiencing difficulties connecting to your site, please contact the person or team who takes care of Moodle in your school or learning organisation. Please note the app only works with Moodle sites that have been set up to allow it, and that are running on at least Moodle 3.5.

===I can’t find my Moodle site in the app. ===
To find your Moodle site on the app login screen, try searching for the name of your school or learning organisation.

If your school or organisation doesn’t appear in the search, you can try searching by your Moodle site URL address instead. If you don’t know the address of your Moodle site, here’s how you can find it:
# Open a web browser (like Chrome or Safari) and go to your school’s Moodle site login page.
# At the top of the page in the address bar, you'll see the URL address of your Moodle site, e.g. “campus.example.edu”. [[File:FAQ I cant find my site 1.png|alt=URL|thumb|none|''campus.example.edu'']]
# Copy the URL (don’t copy the /login nor what comes after), paste it into Your site in the app, then select Connect to your site. [[File:FAQ I cant find my site 2.png|alt=Adding an URL to the app|thumb|none|Adding an URL to the app]]
# Now you can log in to your site with your username and password.

If you tried searching by URL address and still can’t find your Moodle site, please get in touch with the person who takes care of Moodle in your school or learning organisation.
===I can’t log in with the app===
To log in to your Moodle site using the app, you first need to connect to your school’s Moodle site (view [[I can’t find my Moodle site in the app]] if you can’t find your site).

Once you’ve connected to your Moodle site, you should be able to log in with your usual username and password.

If you forgot your username or password, select the option '''Forgotten your username or password?'''. If you still have trouble logging in or can’t see any options for retrieving your username or password, please get in touch with the person who takes care of Moodle in your school or learning organisation.
===I see an error message when I try to use the app===
If you see an error message that prevents you from using the app, please get in touch with the person who takes care of Moodle in your school or learning organisation.

Some of the most common errors that your school or learning organisation will be able to fix are:
* Your token is expired or not valid.
* An error mentioning the parameter “includestealthmodules”.
* The web service function is not available.
* A message about site maintenance.

If you’re experiencing any of these errors, contact your school or learning organisation for help.
===What permissions does the app require?===
The app requires the following permissions:
* Record audio - for uploading to your Moodle site
* Read and modify the contents of your SD card - for content to be downloaded to your SD Card for offline access.
* Network access - to be able to connect with your Moodle site and check if you are connected, and if not to switch to offline mode.
* Run at startup - to receive local notifications even when the app is running in the background.
* Prevent phone from sleeping - to receive push notifications anytime.
===What are the minimum device requirements to use the Moodle app?===
Android devices: Require Android 7.0 or later. (Users with Android 5 and 6 can still use version 4.3, but they will not receive any new updates.)

iOS devices (iPhones/iPads): Require iOS 13 or later. (Please note the app was only tested on versions iOS 14 and onward.)

===I can't see my course on the app. What do I do?===
Check with your course tutor that you are correctly enrolled.
=== Why can't I upload my assignment on the app?===
If you’re experiencing any issue uploading assignment, please contact your school or learning organisation for help.
===Why can't I sometimes access the app or submit anything to it?===
This could be because of interruptions in your internet connection. Wait a while and try again. If you continue to have problems, contact your school or learning organisation for help.
===Is there a space limit on my files?===
Assignments will have a size limit which you can see, those are set by your teachers. For other space limit questions, check with your your school or learning organisation .
===When are activities completed offline synchronized?===
See [[Moodle app synchronization]].
===Why the site is asking for my username and password when an activity is opened in the browser?===
For security reasons, between auto-logins you must wait 6 minutes (this should not be a problem because most of the browsers will keep your Moodle session open).
In recent Moodle versions, the previous value can be configured in Site Administration > Mobile app authentication > Minimum time between auto-login requests

=== The Moodle app might seem slow (especially on Android devices) ===
If the app feels slow, it might be due to things outside the app itself. This can include:
* Slow internet connection
* Network problems
* The server responding slowly
* Content or settings not made for mobile
* Using the app on an old or slow device

We test the app carefully on many sites before each release, and we’re confident it usually works as well as or better than the website.

To make sure your site works well on mobile, please check [[Creating mobile-friendly courses]]

Finally, to troubleshoot this problem, we recommend trying the application with our demo site: https://school.moodledemo.net. Simply use the username "student" and the relevant password to access the site. If you find that the navigation and overall experience with the app are improved, then the issue may be at the server level. In this case, we suggest contacting your school or learning organisation for further assistance.

=== The Moodle app restarts/ closes / reopenes itself ===
This is likely because there are too many apps opened on your mobile device. Mobile devices have a finite amount of memory, and the device's memory manager is responsible for determining which applications to keep open and which to close.
To optimise your device's performance, we recommend closing all applications that are not currently in use. This will free up valuable memory and ensure that your device runs smoothly.
===I use LineageOS and I'm having problems using the app===
LineageOS uses a different WebView implementation not compatible vith the app. You need to install "Android System WebView" from Google Play (or via a trusted apk) and enabling it via Settings > Developer options > WebView implementation.
===H5P packages and external content embedded via iframes are not working on iOS ===
This is caused by a new feature of iOS 14 called ITP that blocks cookies for external sites embedded in the app (the H5P content is played embedded in an iframe pointing to the Moodle website) unless the user enables a setting in the app to allow those cookies.

The quick workaround is to enable the setting "Allow Cross-Website Tracking" available via the Settings app (look for the Moodle app, at the bottom) on your iPhone/iPad with iOS 14.
===I cannot reproduce audio that was recorded on browser on iOS devices (iPhones and iPads)===
This behaviour is related to this Moodle LMS bug: https://tracker.moodle.org/browse/MDL-80114

=== I don't receive calendar notifications (reminders) when using Android 12 or above ===

In order to receive calendar notifications you need to allow alarms and reminders for the Moodle app. To do this:
* Open Android Settings and go to the Moodle app settings. Another way to reach these settings is by long-clicking the Moodle app icon and pressing "App info".
* Make sure that Notifications are enabled.
* If you see a section called "Alarms & reminders", make sure it is Allowed (this setting is disabled by default in Android 14+).

==Teachers==
===How can I enable videos in my course to be downloaded?===
See the section 'Media download for offline usage' in [[Creating Moodle-app-friendly courses]].
===Which course format is it best to use?===
Topics or weekly course format is best suited to mobile devices.
===How do I make YouTube links open automatically in the app?===
Add YouTube links as a [[URL resource]].
===Why can't my students see their courses?===
If you or an administrator have correctly enrolled them in a course, they can see it in their mobile app. If they are correctly enrolled but can still not see their course, ask them to check with your Moodle site administrator.
=== I can't mark assignments in the app===
If you are experiencing problems when grading, please review that you are using the correct decimal separators (if the app interface is in English, you must use a period).
===What communications tools can I use in the app to engage with my learners?===
See [[Mobile app notifications]]. Chat, forums and messaging are all supported by the app.
===My Vimeo videos are not playing in the app===
In older versions of Moodle (pre-Moodle 3.7), it may be necessary to activate the "Allow frame embedding" admin setting. However, for those using Moodle version 3.7 or later, it is important to check whether a Proxy/Firewall/Web Server security module is setting the X-Frame-Options header in your HTTP request responses. If this is the case, it is recommended to deactivate this feature as it may cause conflicts, as Moodle already sets this header by default.

This setting is typically found in any of these configuration files .htaccess, httpd.conf or VirtualHost. To disable it, you can just use: Header always unset X-Frame-Options

You may also use Bootstrap responsive classes: https://getbootstrap.com/docs/4.0/utilities/embed/, for example, <div class="embed-responsive">
For older versions, see this forum discussion with a workaround: https://moodle.org/mod/forum/discuss.php?d=327342

If the issue is with vimeo videos on Moodle sites 3.10 or 3.11, please update the Moodle site to the latest version possible (at least 3.10.10 or 3.11.6). (See https://tracker.moodle.org/browse/MDL-74042)
===ReCaptcha doesn't work on my site===
In older versions of Moodle (pre-Moodle 3.7), it may be necessary to activate the "Allow frame embedding" admin setting. However, for those using Moodle version 3.7 or later, it is important to check whether a Proxy/Firewall/Web Server security module is setting the X-Frame-Options header in your HTTP request responses. If this is the case, it is recommended to deactivate this feature as it may cause conflicts, as Moodle already sets this header by default.
===H5P packages don't work on my site===
In older versions of Moodle (pre-Moodle 3.7), it may be necessary to activate the "Allow frame embedding" admin setting. However, for those using Moodle version 3.7 or later, it is important to check whether a Proxy/Firewall/Web Server security module is setting the X-Frame-Options header in your HTTP request responses. If this is the case, it is recommended to deactivate this feature as it may cause conflicts, as Moodle already sets this header by default.

This setting is typically found in any of these configuration files .htaccess, httpd.conf or VirtualHost. To disable it, you can just use: Header always unset X-Frame-Options

This can also happen when you are using the non-official H5P plugin (mod_hvp), in that case you will see the following message: This site is not configured properly for displaying mobile H5P content. Please contact a site administrator so they can apply the above suggested configuration changes.

If you are using the non-official H5P plugin (mod_hvp) you can also try changing the plugin settings "Mobile rendering handler" and try the different options until you find the one that works for you. You might need to restart the app everytime you change the settings.

'''Cookies issues'''

If your site uses HTTPS please ensure that the "Secure cookies only" (cookiesecure) setting under Site administration > HTTP security is enabled.

'''Dependency errors'''

When the following error appears "Missing dependency H5P.Editor. something X required by H5P.Editor. something Y". H5P packages need to include all the libraries (dependencies) they use so the package is self-contained. But sometimes packages might be missing at least one dependency.

In order to fix this, you could do the following:

Open Moodle’s Content Bank (from the link in the problematic H5P settings page) and upload your H5P package there, once uploaded, you will see the H5P package and an “Edit” button, click on that button so the editor opens, scroll down and click “Save”.
Now, you can replace the problematic H5P with this new one, for this, you can just include it from the Content bank by opening the activity settings page and the file picker.

=== I use a Moodle plugin but the app says it is not supported ===
You should contact the plugin developer and point him to this documentation: https://docs.moodle.org/dev/Moodle_Mobile_Remote_addons where it is explained how to add support to plugins in the Mobile app.

There is a list of Moodle plugins supported by the app here: https://moodle.org/plugins/browse.php?list=award&id=6

To learn more about how the Moodle app works and how to make your plugins compatible, check out the intermediate-level Moodle Academy course [https://moodle.academy/enrol/index.php?id=71 Make Your Plugin Moodle App Compatible].

=== I have problems playing SCORM packages ===
This might be caused because:
* The SCORM was added using an advanced option (remote imsmanifest.xml packages or file system repository unzipped SCORMS)
* The SCORM ZIP file was created using a tool that does not create standardised ZIP files (for example, zip files containing the inverted path separator "\" will not work on Android)
Please refer to [[Moodle app SCORM player]] for additional information.
=== My quizzes or lessons are not working offline ===
You need to edit the quiz or lesson activity settings and enable the "Allow lesson/quiz to be attempted offline using the mobile app" configuration option.
=== Maths notation is not displaying correctly in the app ===
If you are having issues with MathJax, please enable the [[TeX notation filter]] also.

If you have both filters enabled, please leave MathJax above TeX so it is always processed before TeX.

If the issue persists, we suggest disabling the 'Remove HTML tags from all activity names' (''formatstringstriptags'') option in ''Site Administration'' > ''Appearance'' > ''HTML settings''.

=== How can I disable text selection / copy in the app? ===
You can create a remote theme and add some custom CSS rules to disable it, see https://docs.moodle.org/dev/Moodle_Mobile_Themes
=== My images, videos or audios stop working after the first time ===
Please make sure the URL you're using on the media file doesn't have any redirect (e.g. http to https), always try to use the final URL. There's a bug in the library we use to download those files, it doesn't work when downloading files with redirects. We have plans to remove that library from the app, but since then please always try to use URLs without redirects.

=== Embedded YouTube videos are not working on iOS Moodle App (Error 153) ===
Unfortunately recent changes (October 2025) implemented by YouTube have disrupted the functionality of embedded YouTube videos in the Moodle app and other apps. This issue is beyond our control, and we have already reported this problem to all the third-parties that could provide a solution to help address this issue.

We are developing a workaround that will be included in the next version of the app, 5.1.0. Please note that the 5.1.0 app is still under development, and it will take some time to complete the quality assurance process and make it available in the app stores.

Please visit https://moodle.org/mod/forum/discuss.php?d=470700#p1889793 for more information

==Administrators==
=== What plans are available for the Moodle app? ===
There are two main plans available for the Moodle app: Free, and Premium, each offering different features. In addition to the plans, there is also a Branded Moodle App (BMA) option. The BMA is a custom-built app that is branded to your organization. Learn more in [[Moodle app plans]].
=== How can I have my site listed in the Moodle app site finder? ===
Please refer to our [[Moodle app guide for admins]] for instructions.
=== How can I debug errors in the app? ===
Go to the More tab and then to Settings > General. Enable "Display debug messages". This will show an explanatory message when an error occurs, alternatively, you can do a full debugging via: https://docs.moodle.org/dev/Moodle_Mobile_debugging_WS_requests

=== How can I disable features in the app? ===
Please go to ''Site administration > Mobile features > Disabled features'' and select all the features you want to disable.

To select multiple features you will have to use Ctrl (Cmd in Mac) + Click

=== How can I add custom menu items in the app? ===
You can add custom additional menu items in the "more" menu of the app, the one represented by three consecutive dots.

Please go to ''Site administration > Mobile features > Custom menu items'' and follow the instructions in [[Moodle_app_guide_for_admins#Custom_menu_items|Moodle app guide for admins]] for the correct format to use.

As a quick example:
Academy information|https://yoursite.com/mod/page/view.php?id=X |app|en|home

=== How can I customise the language strings in the app? ===

Please go to ''Site administration > Mobile features > Custom language strings'' and follow the instructions in [[Moodle_app_guide_for_admins#Custom_language_strings|Moodle app guide for admins]] for the format to use.

As a quick example:
core.user.student|Learner|en
core.user.student|Aprendiz|es

=== I can connect with my iPhone (or iPad) but not with my Android phone ===
This usually happens when the site is using https and the certificate is not correctly configured or it is using an old protocol, please use these pages to check this certificate: https://www.sslshopper.com/ssl-checker.html, https://www.geocerts.com/ssl_checker, and https://www.ssllabs.com/ssltest/analyze.html

'''The certificate of this site cannot be trusted by your device: TLS connection could not be established: javax.net.ssl.SSLHandshakeException'''

This error could be caused because in any of the certification paths there is a certificate using SHA-1. Starting Android 10 this is not allowed, more information here: https://developer.android.com/privacy-and-security/security-ssl

You could easily check the previous using https://www.ssllabs.com/ssltest/analyze.html and going to the Certification Paths -> Android section, if there is any mention to SHA-1 this could be the cause. You will need to upgrade your certificates to avoid using SHA-1.

=== My certificate is fine but I still can't connect ===
This is usually a server configuration problem caused by any of the following server configuration issues:

'''"Access to XMLHttpRequest at 'https://yoursite/webservice/rest/server.php?moodlewsrestformat=json<nowiki/>...' from origin '<nowiki>http://localhost'</nowiki> has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.'''

This is because a Proxy/Firewall/Web Server security module is removing automatically the Access-Control-Allow-Origin: * header that Moodle sets to allow Web Service requests.

It is totally secure to remove that Proxy/Firewall/Web Server rule/configuration because that header is only set by Moodle when needed.

'''"access-control-allow-origin cannot contain more than one origin".'''

iOS and Android apps do not allow the following header to contain more than one item: "Access-Control-Allow-Origin". For example, a header like this: Access-Control-Allow-Origin: *, https://mydomain.com will cause problems.

This HTTP header is not valid, according to the specification you can only specify a domain or a "*":
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin

Please, review if you have a Proxy/Firewall/Web Server adding automatically values to that HTTP header.

'''Security rules are blocking requests using the Accept-Charset header'''

Some security rules, such as OWASP ModSecurity, are blocking requests with this header that is sent by the Moodle App. In future releases of the app, this problem will be fixed. But in the meantime, you should disable it. Find more about this in MOBILE-4342.
=== My certificate is fine but the Moodle app is detecting http instead of https ===
If the Moodle app is detecting http instead of https, please revise config.php (check "wwwroot" as well as "httpswwwroot")
===After updating Moodle LMS to a recent version my users cannot login===
This only applies to sites that are configured to use log in via an embedded browser pointing to their Moodle site.
This behaviour could be related to this Moodle LMS issue: https://tracker.moodle.org/browse/MDL-81897.
There are several ways to fix this issue:
# Upgrade their Moodle site to any of the indicated version in the issue that will solve the problem
# Manually apply the patch here: https://github.com/jleyva/moodle/compare/462d5f04a8...MDL-81897-master
# Immediate workaround: Change the app authentication so it will launch in a separate browser, by going to Site admin > Mobile app authentication > Type of login (and select the option that mentions external/system browser), remember to Save Changes
We’d recommend doing 3) that will immediately address the issue that is affecting new logins.
===I can't get the app to work. What can I do?===
Assuming you have enabled mobile services on your site (please visit [[Moodle app guide for admins]]), please check:
# If your site uses an SSL certificate, it must be a trusted certificate, not self-signed. Please use these tools or a similar one to check that your certificate is valid: [https://www.sslshopper.com/ssl-checker.html SSL Checker], [https://www.geocerts.com/ssl_checker SSL Checker], and [https://www.ssllabs.com/ssltest/analyze.html SSL Server Test]. All the checks must be ok, including the "Certificate Chain Complete". Otherwise the app might work on iOS but not on Android.
# Make sure that the "Access-Control-Allow-Origin" header only contains one item. For example, a header like this: Access-Control-Allow-Origin: *, <nowiki>https://mydomain.com</nowiki> will cause problems.
# [[Debugging]] is disabled (in ''Site administration > Development > Debugging'')
# The ADOdb debug option is disabled if you are using the external database auth or enrolment plugin (in ''Plugins > Authentication > External database'' and in ''Plugins > Enrolment > External database'').
# SHA-1 https certificates are not supported anymore in Chrome, this means that the Android version of the app won't work for your site. If your site doesn't work in desktop Chrome or Chromium it won't work in the Android app. See https://blog.chromium.org/2014/09/gradually-sunsetting-sha-1.html for more information
# If you are using IIS check that Anonymous access is not disabled for the /webservice directory.
# If you are using a web application firewall like AWS WAF, StackPath, Barracuda, Cloudflare, Juniper, etc... try to temporary disable it to check if that's the cause. If so, you'll have to whitelist these endpoints: login/token.php, webservice/*, lib/ajax/*, media/player/vimeo/wsplayer.php and /tokenpluginfile.php
You can also add WAF rules to allow traffic by detecting the app user agent such as: (http.user_agent contains "MoodleMobile")
If you still have a problem, please post in the [https://moodle.org/mod/forum/view.php?id=7798 Moodle for mobile forum].

If the issue started after updating Moodle LMS please visit [https://docs.moodle.org/en/Moodle_app_FAQ#After_updating_Moodle_LMS_to_a_recent_version_my_users_cannot_login After updating Moodle LMS to a recent version my users cannot login].

=== I cannot access with old users, but I can with recently created ones! ===
Please, do a "Purge all caches" via the Moodle administration settings, this will solve the problem.
===I can't view the courses tab as an administrator===
The Moodle app only displays courses you are enrolled in. If you want to view a course as an admin, you need to enrol in it.
===My Moodle site uses a SSO auth method (Shibboleth, Google OAuth, etc) and the app is not working===
See the section 'Mobile authentication' in the [[Moodle app guide for admins]] for details of how to configure it.

If configured the app is still not connecting: If your site uses an SSL certificate, it must be a trusted certificate, not self-signed. Please use this tool or a similar one to check that your certificate is fine: [https://www.geocerts.com/ssl_checker SSL Checker]. All the checks must be OK, including the "Certificate Chain Complete".

If your SSO method is unable to authenticate when using an "embedded browser" (it gives an authentication error), please check if it works with a "browser window". If it does work with the browser window then it means your SSO is performing an HTTP redirect, and these kind of redirects aren't supported by the app (the request is redirected by the browser not passing the POST parameters). Unfortunately, this is something we cannot control in the Mobile app (it can't be handled via JavaScript). For further information, see http://stackoverflow.com/questions/228225/prevent-redirection-of-xmlhttprequest and http://stackoverflow.com/questions/4168784/ajax-redirection-handling

There are only 2 possible solutions: set the authentication via a "browser window" instead of an embedded one (please notice this won't work in the Linux desktop app), or remove the redirect from the SSO auth method.

===SSO is not working with my custom auth plugin===
SSO should work in any plugin if the plugin handles correctly the $SESSION->wantsurl, this is the way SSO works when it is launched via the app:
* It launchs this URL https://yourmoodle/admin/tool/mobile/launch.php?service=local_mobile&passport=abc in the device browser
* If the user is not logged in, the browser will redirect the user to the login page
* If the auth plugin used implements correctly the handling of the wantsurl session var, once the user has logged in, the browser should redirect back to the https://yourmoodle/admin/tool/mobile/launch.php?service=local_mobile&passport=abc URL that will launch the mobile app via the custom URL protocol
Custom auth plugins may be failing in the last step,not redirecting back to tool/mobile, this will happen only if the plugin does not support correctly the $SESSION->wantsurl.

The SAML plugin works correctly but some modifications of that plugin may not work if important lines are changed.
===I am having problems requesting an airnotifier access key===
If you have registered your site but are still unable to request an access key, please register your site on the Moodle Apps Portal https://apps.moodle.com once your site is registered there, an Airnotifier access key will be automatically generated for you.
=== Push notifications are not working ===
Please check [[Mobile app notifications#Troubleshooting]]
=== How notifications icon badges are updated ===
'''Android''': Not all Android devices support icon badges so in some cases badges will never display numbers, also, depending on the device only a badge indicating that there are new notifications will be displayed when receiving a Push notification when the app is not in the foreground.

'''iOS''': The icon badge counter is only updated when the app is open and it will reflect the number of notifications pending reading or the number of message senders that sent you a message you have not read yet

In general, for iOS the icon badge displayed number should match the one displayed at the bottom of the app (or it should be the sum of the notifications and messages badges) and is not an indicator of the number of Push notifications the user has received, it acts as a reminder of pending notifications to be read that only gets updated when the user open the apps

There is an open issue to improve the behaviour on iOS, please watch MDL-73707
=== I configured 'QR code access' to automatic login, but the app still asks for credentials ===
Automatic authentication only works for Premium sites. You can see the app plans [https://moodle.com/app/ in this site].

If you're getting an error saying that the device you're using to connect isn't in the same network as the device that displays the QR code but both devices are connected to the same network, please check the section: [[#ipmismatch:_.27Client_IP_address_mismatch.27|ipmissmatch: 'Client IP address mismatch']].

=== I can log in on my Moodle site but I see a blank page or the app styles broken ===
This is usually because your Moodle site has a customised CSS.

Please try leaving empty CSS (''mobilecssurl'') on Site administration > Mobile app > Mobile appearance. If that works, please read [https://docs.moodle.org/dev/Moodle_App_Remote_Themes Moodle App Remote Themes] and create a new CSS file using the variables mentioned there

===The Moodle app does not connect to MoodleBox (or other internal self-hosted systems)===
You will need to disable SSL to make the app works, please see this forum discussion for more information: https://moodle.org/mod/forum/discuss.php?d=424353#p1739474
===I think I found a bug with the app. Where can I report it?===
# Log in to the [https://tracker.moodle.org/browse/MOBILE Moodle Mobile tracker] (you'll need to [http://tracker.moodle.org/secure/Signup%21default.jspa create a tracker account] if you've not done so previously)
# Check whether the issue has already been reported by doing a [https://tracker.moodle.org/issues/?jql=project%20%3D%20MOBILE search]
# If not, report the bug by clicking the 'Create Issue' link at the top right of the page, selecting 'Moodle app' as the project
# Add a detailed description providing as much information as possible (Moodle version, app version, device model and operating system, etc...), then click the Create button
===How can I get the app in my language?===
[[File:setting the app lang.png|thumb|100px|Setting your language]]
The Moodle app automatically detects your mobile's language and displays in the same language (if the translation exists). Otherwise, you can set the app language in App settings > General.

See also a post explaining how multi-lang works in the Moodle app: [https://moodle.org/mod/forum/discuss.php?d=453445#p1825637 Re: Language selector missing in Moodle app]

If the Moodle app is not yet available in your language, please contribute a translation! See [https://docs.moodle.org/dev/Translating%20Moodle%20Mobile Translating Moodle Mobile] for details of what to do.

=== Changes made to a Moodle site URL can cause logged-in users’ data to fail when synchronising. ===
We recommend that administrators manually log out all users after a site rename. If your site URL changes and have site users that are using the mobile Moodle App we suggest the following:
* For users that have not yet logged in - we recommend sending them the new URL
* For users already using the mobile Moodle App and potentially logged in request them to:
** log out of the mobile Moodle App,
** delete the old site, and
** log in using the new URL
Logged in Moodle users can continue working with the previous URL (with cached information) but they will not be able to synchronise the new information (therefore not receiving new information from their teachers, and teachers not receiving data or submissions from those students).
* To avoid the risk of data not synchronising, we recommend the site administrator logs out all app users, by manually deleting their tokens:
** Go to Site administration
** Click Server
** Click Web services
** Click Manage tokens
** Delete the tokens
Take into account that you still need to request your users to log in using the new URL.

=== Embedded content is not working ===

This could be caused because your site is using a Content-Security-Policy that is preventing the app from embedding content.

You can easily detect this when an error like this is displayed (javascript console): Refused to load URL because it does not appear in the frame-ancestors directive of the Content Security Policy.

If that's the case, you'd need to add the following elements: http://localhost moodleappfs://localhost at the end of the "Content-Security-Policy" HTTP header:

An example of a CSP allowing embedding Vimeo videos in the site and content in the app:
Content-Security-Policy: frame-ancestors 'self' https://*.vimeocdn.com https://*.vimeows.com https://*.vimeo.com http://localhost moodleappfs://localhost ;

Other type of embedded content that does not work is content hosted by Microsoft tools that require session or any type of authentication, such as SharePoint content.

=== Some activities are displayed incorrectly (blank, just a vertical line, ..) on the app ===
Please visit the forum post [[https://moodle.org/mod/forum/discuss.php?d=461909#p1854918| Some lesson activities do not display at all]].

==Error messages==
=== 'Coding error: version.php file is missing for the component' ===
This error message indicates that that plugin is not correctly installed (or uninstalled) on the Moodle site you use (see [[Installing plugins]]). Please review the mod/certificate folder to check if the version.php file is missing (or has incorrect permissions) as well as purge cache too.
=== 'Can not find data record in database table external_functions' ===
This error usually happens due to a bad configuration or setting value in your Moodle site, please check:
# The user quota global setting should be an integer. For more details, see the discussion [https://moodle.org/mod/forum/discuss.php?d=320873 How to enable Moodle Mobile App for all accounts].
# The ''usermaxuploadfilesize'' should be an integer, please try to decrease the size. It can be configured in ''Site Administration > Security > Site Policies > Maximum uploaded file size''. The default value (Site upload limit) depends on the PHP configuration, you might have to change the value of ''upload_max_filesize'' and ''post_max_size'' in your ''php.ini'' file.
# The user "lang" field in the database is set to a correct value and existing language installed in the site. Some times the lang field is set via external systems to incorrect values or pointing to a language pack that was uninstalled. Please, note that to fix this you need direct access to the database and your 'user' and 'course' table.
==='Cannot connect: Verify that you have typed correctly the URL and that your site uses Moodle 3.5 or later'===
Take into account that the app will only connect to Moodle LMS sites version 3.5 onward.
Please also check:
# Mobile services are enabled for the site.
# The user is entering the correct URL for the site (see FAQ above)
# For https sites, the certificate is valid (see FAQ above)
==='Invalid Moodle site version. The Moodle app only supports Moodle systems 3.5 onwards'===
The app will only connect to Moodle LMS sites version 3.5 onward (see [https://docs.moodle.org/35/en/Upgrading Upgrade to 3.5] as well as [[Upgrade overview]]).
==='We lost connection; you need to reconnect. Your token is now invalid.' on my custom version of the Moodle app ===
Please check:
# You have followed all the steps listed in [https://docs.moodle.org/dev/Moodle%20Mobile%20Developing%20a%20plugin%20tutorial Moodle Mobile Developing a plugin tutorial]
# You have enabled the [[Capabilities/moodle/webservice:createtoken|moodle/webservice:createtoken]] for the authenticated user
==='No permission to create web service token for the service local_mobile' when attempting to log in (any user that it is not an admin)===
Please check you have enabled the moodle/webservice:createtoken for the authenticated user or any global role you want to allow to use the mobile app
==='No permission to create web service token for the service local_mobile' when attempting to log in as an admin===
You need to create a token for the admin account (only) as follows:
# Go to ''Site administration > Plugins > Web services > Manage tokens''
# Click Add
# Enter the admin username and select 'Moodle app additional features service' (i.e. do NOT leave it as 'Moodle app web service')
# Click the 'Save changes' button.
==='Invalid response value detected' when accessing the site ===
The user quota global setting should be an integer. For more details, see the discussion [https://moodle.org/mod/forum/discuss.php?d=320873 How to enable Moodle Mobile App for all accounts].
=== ' Invalid response value detected: Invalid external api response: the value is "", the server was expecting "raw" type" ===
This usually happens when there is a field with value NULL in a table in the database that should not be there. This may happen if your Moodle has been upgraded over many years and the database schema is broken.

To fix it, you can do the following:
* Detect the field that is causing the problem (it should be indicated before the error message)
* Fix the field, for example, for the password field in the lesson table: UPDATE mdl_lesson SET password = '' WHERE password IS NULL (remember that your table prefix can be different than mdl_)
==='Invalid response value detected' when accessing My Courses or Course Overview ===
This usually happens when a course uses a language that isn't installed in the site. Please make sure that all courses use valid languages. This can be easily checked in the database, table "course", there is a column named "lang".
==='A required parameter (username) was missing'===
This may happen if your site implements HTTP redirects; the request is redirected by the browser not passing the POST parameters.

Unfortunately, this is something we cannot control in the Mobile app (it can't be handled via JavaScript). For further information, see http://stackoverflow.com/questions/228225/prevent-redirection-of-xmlhttprequest and http://stackoverflow.com/questions/4168784/ajax-redirection-handling

The solution is to change the HTTP redirect and use an HTML page with a meta tag or JavaScript redirect.
==='Cannot get course contents'===
This usually happens when the course is using a course format plugin that was uninstalled from the server or that was not properly installed.

Please, reinstall again the course format plugin.
==='Access control exception' or 'Your authentication token is invalid or has expired'===
Please double-check that 'Enable web services for mobile devices' (''enablemobilewebservice'') is actually enabled. (It might be unabled if for example you have reseted some roles.)

If this error appears as soon as you enter the username and password for a new site, then it probably means that the token expiration time is badly configured. This is how to fix it:
# Go to ''Site administration > Security > Site security settings''.
# Find the setting named ''User created token duration''.
# If the value is set to 0 or it's too low, please set it back to a valid value (the default value is 12 weeks).
# Click the 'Save changes' button.

===ipmismatch: 'Client IP address mismatch'===
This error can appear when a user opens your site in a browser while using the app. This happens if your site is behind a proxy and you're using one of these Moodle versions o higher: 3.5.11, 3.6.9, 3.7.5, 3.8.2, 3.9.0.

To fix it:
# Go to ''Site administration > Administration > Server > HTTP''.
# Find the setting named ''Ignore reverse proxies'' (reverseproxyignore).
# Enter the IP of your proxy (or range of IPs).
# Click the 'Save changes' button.
If you are still experiencing issues please try to change this setting "getremoteaddrconf" (Logged IP address source) to the different existing values.

Finally, it is possible to disable the IP restriction checks for functionality such as the QR login, to do that, go to Site administration > Mobile app > Mobile app authentication, and disable the "QR authentication same IP check" setting.
=== 'The param "includestealthmodules" is invalid' ===
Please contact your learning organisation so they upgrade to at least Moodle 3.5.3 (see [https://docs.moodle.org/35/en/Upgrading Upgrade to 3.5] as well as [[Upgrade overview]]) or they manually apply the patch listed here [[MDL-63542]].

==Older versions of the Moodle app==
We always recommend using the last version of the Moodle App but some times users are still using older versions this is the reason we are keeping this list:

=== Some users are asked to reauthenticate too often when they browse the site (Moodle App <3.9.3) ===
This can happen if the app is sending too many variables to a WebService, e.g. because a course has a large number of sections and/or activities. This error was fixed in the 3.9.3 version of the app, but if you are using an older version of the app you can increase the value of ''max_input_vars'' in ''php.ini'' to fix it in your server.

=== After upgrading to 3.9.5 some of my plugins have stopped working ===
The Moodle App 3.9.5 version came with some breaking changes for plugins, most of the existing plugins have been updated to support the new changes.
Please check the following list of plugins that should work for 3.9.5 once you have upgraded to the latest version indicated in the document: https://docs.google.com/spreadsheets/d/1E9PqcUBpp9SAfQc_zJtX5tf9GeS3UN76A85IrrB4UDw/edit#gid=0

==Any further questions?==
Please post in the [http://moodle.org/mod/forum/view.php?id=7798 Moodle for mobile forum] on moodle.org.

[[Category:FAQ]]

[[de:Moodle Mobile - FAQ]]
[[ca:Moodle Mobile FAQ]]
[[es:Moodle app FAQ]]
[[fr:Moodle pour les mobiles]]
[[ja:バイルMoodle FAQ]]

Moodle app notifications

2025-11-06T07:34:03Z

Jleyva:

{{Mobile}}

==For students and teachers==
[[File:12Notifications.png|thumb|Forum post notification]]
The Moodle mobile app lets you keep up to date with all that's happening in your courses and on the site. Every time you open the app, events are synchronised with the website.

You will receive [[Calendar|Moodle calendar]] event notifications automatically. If you don't want to get them, you can turn them all off individually (or globally) in the Calendar events options in the main menu.

You will also receive notifications of messages, forum posts, submitted assignments etc. (known as 'push notifications') if your site administrator has enabled these. To receive these notifications you need to enable them EITHER via the app OR via the website.

To enable mobile notifications via the app:

# Go to the app settings then Notification preferences
# Move the slider so that disable notifications is off
# Move the slider to turn on notifications for assignment, feedback, forum etc. as required

To enable mobile notifications via the website:

# Go to your user menu (top right of each page) and select Preferences
# Click the link 'Notification preferences'
# Click to turn on notifications for assignment, feedback, forum etc. as required

{|
|-
| [[File:notification preferences app.png|thumb|Notification preferences in the app]]
| [[File:notification preferences web.png|thumb|Notification preferences on website]]
|}

==For administrators==

Push notifications can be enabled by an administrator by connecting their Moodle site to a messaging server such https://messages.moodle.net (available for [[Site registration|registered Moodle sites]] only). An access key can be obtained via ''Site administration > General > Messaging > Notification settings''; be sure the 'Mobile' is enabled and then click the link to settings, on the next page select ''Request access key''. (For Moodle site versions 3.5 and 3.6 an access key can be obtained via ''Site administration > Plugins > Message outputs > Manage message outputs''. Then by clicking the link to the Mobile settings, on the next page select ''Request access key''.)

Note that from 2 April 2020, there will be certain limitations when using push notifications. Depending on the size of your site and the number of user devices receiving notifications, you may need to sign up to a Premium plan in the Moodle Apps portal: https://apps.moodle.com. For further information, see the official announcement [https://moodle.org/mod/forum/discuss.php?d=397926 Introducing our new Moodle App plans].

You can enable by default Mobile notifications for your students, please read the "Default message outputs" section in [[Messaging settings]].

If you have problems requesting the access key, please register your site on the Moodle Apps Portal https://apps.moodle.com once your site is registered there, an Airnotifier access key will be automatically generated for you.

Users then need to connect at least once with the latest version of the Moodle Mobile app in order to register their phones with the Moodle site.

=== Encrypted Push Notifications ===

Encrypted push notifications are available in Moodle LMS 4.1.4 and later, and in Moodle App 4.2 and later.

To enable encrypted push notifications, go to Site administration > Messaging > Mobile and select ‘Encrypt notifications’.

When encrypted notifications are enabled, any information or data in the notifications that could potentially identify a user is encrypted using the Curve25519/X25519 encryption algorithm. This guarantees full compliance with GDPR for organisations that want to prevent their data from being transmitted without encryption through any processing server.

The generated key pair (public and private) used to encrypt notifications is securely stored in the keystore or keychain of each device that receives notifications from your site.

'''Limitations of encrypted push notifications'''

* At least Android 8 or iOS 13 are required on devices receiving notifications. Older versions of these systems are not supported.
* Rich push notifications (notifications with media attachments) are not supported.
* Some notifications may not redirect to the appropriate page or section within the app.
* If the size of the notification content is too big, it will be replaced with the message ‘Tap to view text’.
* For iOS devices only: If the Moodle App is not in the background or foreground of devices, some notifications might not be received. This is a native iOS limitation and is based on a number of factors, such as devices’ CPU usage, notifications’ priority level (data-only messages are considered ‘low priority’ by iOS), battery level, etc. You can read additional technical information in this discussion: https://github.com/firebase/flutterfire/issues/9300.

'''Troubleshooting'''

* After upgrading your Moodle site to a version that supports encrypted push notifications (Moodle LMS 4.1.4 or later), it’s important to note that your users will only start receiving encrypted notifications once they access your upgraded site through their Moodle App for the first time.
* To verify if a device supports encrypted push notifications, follow these steps:
# Open the Moodle App and access the 'More' menu (represented by three dots).
# Select 'App settings' and then choose 'About'.
# On the 'About' page, tap on the App version (Moodle Mobile X.X) at the bottom.
# A new page titled 'Device info' will appear.
# Scroll to the bottom of the 'Device info' page to locate the section ‘Encrypted push notifications supported.’
Please note that this indicates whether a device can support encrypted push notifications, but it doesn’t necessarily mean that they have been enabled on a specific Moodle site.

=== Event Reminders plugin===

Push notifications can also include calendar event notifications, however this requires the [https://moodle.org/plugins/view/local_reminders Event Reminders plugin] to be installed on the Moodle site.

The Event Reminders plugin will automatically send reminders for Moodle calendar events in a timely manner via Moodle message interface. It also allows users to control how they receive messages for each type of event in the Moodle calendar.

=== Installing your own notifications infrastructure ===

If you have a customized version of the Moodle Mobile app, or you want to use your own notifications infrastructure, you will have to install a private [http://airnotifier.github.io AirNotifier] (backend server for notifications).

Please notice that Moodle HQ does not maintain or offer any support for any Airnotifier-related issues. Moodle HQ has funded and contributed with some fixes to this software but it is not officially maintaining or supporting it.

Moodle offers a branded app service including a private notifications infrastructure, for more information visit https://moodle.com/mobileapp/

== Troubleshooting ==

If your users are not receiving push notifications please check:

* You have not exceeded the maximum number of active devices according to your Moodle App Plan. You can register for free on https://apps.moodle.com to check your current active user devices to check if you need to upgrade to a [https://apps.moodle.com/local/apps/signup_site.php?plan=premium&origin=moodledocs Premium plan].
* You have entered an Airnotifier access key in the Mobile settings in the Site administration
* Mobile is enabled in Messaging > Notification settings in the Site administration
* In your config.php, $CFG->noemailever is not set to true (or it does not exist)
* Any user not receiving notifications has enabled mobile notifications in the mobile app in App settings > Notification preferences then check that "Disable notifications" is not selected
* Any user not receiving notifications has enabled the type of notifications they want to receive in App settings > Notification preferences
* Any user not receiving notifications hasn't disabled his current device in App settings > Notification preferences > 3 dots menu > Configure devices
* Mobile notifications are not disallowed by an administrator in 'Default message outputs' in the Site administration
* Mobile notifications are enabled in the user's Android phone (Settings > Apps > Moodle Mobile > Show notifications ticked) or iOS phone (in iOS in Settings -> Moodle Mobile > Notifications)
* The server where your Moodle site is installed is able to connect to messages.moodle.net (port 443) via telnet
* You are using the Moodle Mobile official app. If you are using a custom/branded app for your institution, please contact your institution since custom apps need their own notifications infrastructure (see above).
* Your Moodle installation cron jobs are not locked. You can check it executing the CRON manually and reading the output, more info [https://moodle.org/mod/forum/discuss.php?d=361595 here]

=== Testing push notifications ===

To test push notifications:

# Ensure that mobile notifications are enabled (as described above).
# Go to a course and create a forum with forced subscription.
# Log in as a student and create a new discussion in the forum.
# As the same student, log in on the mobile app, go to App settings > Notification preferences > Forum and enable all the notifications.
# In the same page, check that at the top of the page you see "You are configuring Mobile notifications". If it says "You are configuring notifications for web (or email)", switch to mobile via the three dots menu at the top right.
# In the same page, tap the three dots menu (top right), go to Configure devices and check that your current device is enabled.
# Now, put the Moodle Mobile app in background (switching to a different app or going to your device home).
# Log in to the site (on the web) and post a reply to the discussion started by the student., ticking the option "Send forum post notifications with no editing-time delay".
# Verify that the student receives a push notification on their mobile device.

== See also ==
* [https://docs.moodle.org/en/Moodle_app_FAQ#I_don.27t_receive_calendar_notifications_.28reminders.29_when_using_Android_12_or_above I don't receive calendar notifications (reminders) when using Android 12 or above]
* [https://docs.moodle.org/en/Moodle_app_FAQ#How_notifications_icon_badges_are_updated How notifications icon badges are updated]

[[de:Moodle App - Systemnachrichten]]
[[ca:Notificacions de la app Mobile]]
[[es:Mobile app Notificaciones Push]]
[[fr:Notifications de l'app mobile]]

Moodle app FAQ

2025-10-23T09:27:16Z

Jleyva: /* H5P packages don't work on my site */

{{Mobile}}
==Students==
===How can I log in?===
To log in to your Moodle site with the Moodle App, you need the URL (web address) of the Moodle site that you’re trying to access. If your organisation has Search enabled, you can try searching by the name of your organisation or eLearning site.

If your organisation allows you to log in via QR code, you’ll find the QR code at the bottom of your user profile on your Moodle site. You just need to press “Scan QR code” on the app, scan the QR code on your profile and you’ll be logged in automatically.

If your organisation allows you to log in using face recognition or fingerprint, you can activate this in the App, going to User account > Preferences. You’ll need to have biometric authentication enabled in your own device’s settings.
===Who can I contact for help with the app?===
If you’re a student and need help with issues related to logging in, registering to a Moodle site or trouble connecting to the app, you should contact your school or learning organisation. For example, one of your teachers, or the person who takes care of Moodle.
Moodle HQ make the Moodle software and the Moodle app, but they don’t manage nor have access to your Moodle site or your user data.
===How can I get the Moodle app?===
You can download the Moodle App for free from [https://play.google.com/store/apps/details?id=com.moodle.moodlemobile Google Play] and the Apple [https://itunes.apple.com/app/moodle-mobile/id633359593?mt=8 App Store]. You will find it by searching “Moodle”, and the author/owner is “Moodle Pty Ltd”.
If you are unable to download the app from Google play, please visit [https://download.moodle.org/mobile/ Moodle app downloads]
===I can't get the app to work. ===
To ensure that the Moodle app functions properly, please double-check that you have correctly entered the URL address of the Moodle site you are using (please visit [https://docs.moodle.org/en/Moodle_app_FAQ#I_can%E2%80%99t_find_my_Moodle_site_in_the_app. I can’t find my Moodle site in the app]). If you are experiencing difficulties connecting to your site, please contact the person or team who takes care of Moodle in your school or learning organisation. Please note the app only works with Moodle sites that have been set up to allow it, and that are running on at least Moodle 3.5.

===I can’t find my Moodle site in the app. ===
To find your Moodle site on the app login screen, try searching for the name of your school or learning organisation.

If your school or organisation doesn’t appear in the search, you can try searching by your Moodle site URL address instead. If you don’t know the address of your Moodle site, here’s how you can find it:
# Open a web browser (like Chrome or Safari) and go to your school’s Moodle site login page.
# At the top of the page in the address bar, you'll see the URL address of your Moodle site, e.g. “campus.example.edu”. [[File:FAQ I cant find my site 1.png|alt=URL|thumb|none|''campus.example.edu'']]
# Copy the URL (don’t copy the /login nor what comes after), paste it into Your site in the app, then select Connect to your site. [[File:FAQ I cant find my site 2.png|alt=Adding an URL to the app|thumb|none|Adding an URL to the app]]
# Now you can log in to your site with your username and password.

If you tried searching by URL address and still can’t find your Moodle site, please get in touch with the person who takes care of Moodle in your school or learning organisation.
===I can’t log in with the app===
To log in to your Moodle site using the app, you first need to connect to your school’s Moodle site (view [[I can’t find my Moodle site in the app]] if you can’t find your site).

Once you’ve connected to your Moodle site, you should be able to log in with your usual username and password.

If you forgot your username or password, select the option '''Forgotten your username or password?'''. If you still have trouble logging in or can’t see any options for retrieving your username or password, please get in touch with the person who takes care of Moodle in your school or learning organisation.
===I see an error message when I try to use the app===
If you see an error message that prevents you from using the app, please get in touch with the person who takes care of Moodle in your school or learning organisation.

Some of the most common errors that your school or learning organisation will be able to fix are:
* Your token is expired or not valid.
* An error mentioning the parameter “includestealthmodules”.
* The web service function is not available.
* A message about site maintenance.

If you’re experiencing any of these errors, contact your school or learning organisation for help.
===What permissions does the app require?===
The app requires the following permissions:
* Record audio - for uploading to your Moodle site
* Read and modify the contents of your SD card - for content to be downloaded to your SD Card for offline access.
* Network access - to be able to connect with your Moodle site and check if you are connected, and if not to switch to offline mode.
* Run at startup - to receive local notifications even when the app is running in the background.
* Prevent phone from sleeping - to receive push notifications anytime.
===What are the minimum device requirements to use the Moodle app?===
Android devices: Require Android 7.0 or later. (Users with Android 5 and 6 can still use version 4.3, but they will not receive any new updates.)

iOS devices (iPhones/iPads): Require iOS 13 or later. (Please note the app was only tested on versions iOS 14 and onward.)

===I can't see my course on the app. What do I do?===
Check with your course tutor that you are correctly enrolled.
=== Why can't I upload my assignment on the app?===
If you’re experiencing any issue uploading assignment, please contact your school or learning organisation for help.
===Why can't I sometimes access the app or submit anything to it?===
This could be because of interruptions in your internet connection. Wait a while and try again. If you continue to have problems, contact your school or learning organisation for help.
===Is there a space limit on my files?===
Assignments will have a size limit which you can see, those are set by your teachers. For other space limit questions, check with your your school or learning organisation .
===When are activities completed offline synchronized?===
See [[Moodle app synchronization]].
===Why the site is asking for my username and password when an activity is opened in the browser?===
For security reasons, between auto-logins you must wait 6 minutes (this should not be a problem because most of the browsers will keep your Moodle session open).
In recent Moodle versions, the previous value can be configured in Site Administration > Mobile app authentication > Minimum time between auto-login requests

=== The Moodle app might seem slow (especially on Android devices) ===
If the app feels slow, it might be due to things outside the app itself. This can include:
* Slow internet connection
* Network problems
* The server responding slowly
* Content or settings not made for mobile
* Using the app on an old or slow device

We test the app carefully on many sites before each release, and we’re confident it usually works as well as or better than the website.

To make sure your site works well on mobile, please check [[Creating mobile-friendly courses]]

Finally, to troubleshoot this problem, we recommend trying the application with our demo site: https://school.moodledemo.net. Simply use the username "student" and the relevant password to access the site. If you find that the navigation and overall experience with the app are improved, then the issue may be at the server level. In this case, we suggest contacting your school or learning organisation for further assistance.

=== The Moodle app restarts/ closes / reopenes itself ===
This is likely because there are too many apps opened on your mobile device. Mobile devices have a finite amount of memory, and the device's memory manager is responsible for determining which applications to keep open and which to close.
To optimise your device's performance, we recommend closing all applications that are not currently in use. This will free up valuable memory and ensure that your device runs smoothly.
===I use LineageOS and I'm having problems using the app===
LineageOS uses a different WebView implementation not compatible vith the app. You need to install "Android System WebView" from Google Play (or via a trusted apk) and enabling it via Settings > Developer options > WebView implementation.
===H5P packages and external content embedded via iframes are not working on iOS ===
This is caused by a new feature of iOS 14 called ITP that blocks cookies for external sites embedded in the app (the H5P content is played embedded in an iframe pointing to the Moodle website) unless the user enables a setting in the app to allow those cookies.

The quick workaround is to enable the setting "Allow Cross-Website Tracking" available via the Settings app (look for the Moodle app, at the bottom) on your iPhone/iPad with iOS 14.
===I cannot reproduce audio that was recorded on browser on iOS devices (iPhones and iPads)===
This behaviour is related to this Moodle LMS bug: https://tracker.moodle.org/browse/MDL-80114

=== I don't receive calendar notifications (reminders) when using Android 12 or above ===

In order to receive calendar notifications you need to allow alarms and reminders for the Moodle app. To do this:
* Open Android Settings and go to the Moodle app settings. Another way to reach these settings is by long-clicking the Moodle app icon and pressing "App info".
* Make sure that Notifications are enabled.
* If you see a section called "Alarms & reminders", make sure it is Allowed (this setting is disabled by default in Android 14+).

==Teachers==
===How can I enable videos in my course to be downloaded?===
See the section 'Media download for offline usage' in [[Creating Moodle-app-friendly courses]].
===Which course format is it best to use?===
Topics or weekly course format is best suited to mobile devices.
===How do I make YouTube links open automatically in the app?===
Add YouTube links as a [[URL resource]].
===Why can't my students see their courses?===
If you or an administrator have correctly enrolled them in a course, they can see it in their mobile app. If they are correctly enrolled but can still not see their course, ask them to check with your Moodle site administrator.
=== I can't mark assignments in the app===
If you are experiencing problems when grading, please review that you are using the correct decimal separators (if the app interface is in English, you must use a period).
===What communications tools can I use in the app to engage with my learners?===
See [[Mobile app notifications]]. Chat, forums and messaging are all supported by the app.
===My Vimeo videos are not playing in the app===
In older versions of Moodle (pre-Moodle 3.7), it may be necessary to activate the "Allow frame embedding" admin setting. However, for those using Moodle version 3.7 or later, it is important to check whether a Proxy/Firewall/Web Server security module is setting the X-Frame-Options header in your HTTP request responses. If this is the case, it is recommended to deactivate this feature as it may cause conflicts, as Moodle already sets this header by default.

This setting is typically found in any of these configuration files .htaccess, httpd.conf or VirtualHost. To disable it, you can just use: Header always unset X-Frame-Options

You may also use Bootstrap responsive classes: https://getbootstrap.com/docs/4.0/utilities/embed/, for example, <div class="embed-responsive">
For older versions, see this forum discussion with a workaround: https://moodle.org/mod/forum/discuss.php?d=327342

If the issue is with vimeo videos on Moodle sites 3.10 or 3.11, please update the Moodle site to the latest version possible (at least 3.10.10 or 3.11.6). (See https://tracker.moodle.org/browse/MDL-74042)
===ReCaptcha doesn't work on my site===
In older versions of Moodle (pre-Moodle 3.7), it may be necessary to activate the "Allow frame embedding" admin setting. However, for those using Moodle version 3.7 or later, it is important to check whether a Proxy/Firewall/Web Server security module is setting the X-Frame-Options header in your HTTP request responses. If this is the case, it is recommended to deactivate this feature as it may cause conflicts, as Moodle already sets this header by default.
===H5P packages don't work on my site===
In older versions of Moodle (pre-Moodle 3.7), it may be necessary to activate the "Allow frame embedding" admin setting. However, for those using Moodle version 3.7 or later, it is important to check whether a Proxy/Firewall/Web Server security module is setting the X-Frame-Options header in your HTTP request responses. If this is the case, it is recommended to deactivate this feature as it may cause conflicts, as Moodle already sets this header by default.

This setting is typically found in any of these configuration files .htaccess, httpd.conf or VirtualHost. To disable it, you can just use: Header always unset X-Frame-Options

This can also happen when you are using the non-official H5P plugin (mod_hvp), in that case you will see the following message: This site is not configured properly for displaying mobile H5P content. Please contact a site administrator so they can apply the above suggested configuration changes.

If you are using the non-official H5P plugin (mod_hvp) you can also try changing the plugin settings "Mobile rendering handler" and try the different options until you find the one that works for you. You might need to restart the app everytime you change the settings.

'''Cookies issues'''

If your site uses HTTPS please ensure that the "Secure cookies only" (cookiesecure) setting under Site administration > HTTP security is enabled.

'''Dependency errors'''

When the following error appears "Missing dependency H5P.Editor. something X required by H5P.Editor. something Y". H5P packages need to include all the libraries (dependencies) they use so the package is self-contained. But sometimes packages might be missing at least one dependency.

In order to fix this, you could do the following:

Open Moodle’s Content Bank (from the link in the problematic H5P settings page) and upload your H5P package there, once uploaded, you will see the H5P package and an “Edit” button, click on that button so the editor opens, scroll down and click “Save”.
Now, you can replace the problematic H5P with this new one, for this, you can just include it from the Content bank by opening the activity settings page and the file picker.

=== I use a Moodle plugin but the app says it is not supported ===
You should contact the plugin developer and point him to this documentation: https://docs.moodle.org/dev/Moodle_Mobile_Remote_addons where it is explained how to add support to plugins in the Mobile app.

There is a list of Moodle plugins supported by the app here: https://moodle.org/plugins/browse.php?list=award&id=6

To learn more about how the Moodle app works and how to make your plugins compatible, check out the intermediate-level Moodle Academy course [https://moodle.academy/enrol/index.php?id=71 Make Your Plugin Moodle App Compatible].

=== I have problems playing SCORM packages ===
This might be caused because:
* The SCORM was added using an advanced option (remote imsmanifest.xml packages or file system repository unzipped SCORMS)
* The SCORM ZIP file was created using a tool that does not create standardised ZIP files (for example, zip files containing the inverted path separator "\" will not work on Android)
Please refer to [[Moodle app SCORM player]] for additional information.
=== My quizzes or lessons are not working offline ===
You need to edit the quiz or lesson activity settings and enable the "Allow lesson/quiz to be attempted offline using the mobile app" configuration option.
=== Maths notation is not displaying correctly in the app ===
If you are having issues with MathJax, please enable the [[TeX notation filter]] also.

If you have both filters enabled, please leave MathJax above TeX so it is always processed before TeX.

If the issue persists, we suggest disabling the 'Remove HTML tags from all activity names' (''formatstringstriptags'') option in ''Site Administration'' > ''Appearance'' > ''HTML settings''.

=== How can I disable text selection / copy in the app? ===
You can create a remote theme and add some custom CSS rules to disable it, see https://docs.moodle.org/dev/Moodle_Mobile_Themes
=== My images, videos or audios stop working after the first time ===
Please make sure the URL you're using on the media file doesn't have any redirect (e.g. http to https), always try to use the final URL. There's a bug in the library we use to download those files, it doesn't work when downloading files with redirects. We have plans to remove that library from the app, but since then please always try to use URLs without redirects.

==Administrators==
=== What plans are available for the Moodle app? ===
There are three main plans available for the Moodle app: Free, Pro, and Premium, each offering different features and benefits. In addition to the three main plans, there is also a Branded Moodle App (BMA) option. The BMA is a custom-built app that is branded to your organization. Learn more in [[Moodle app plans]].
=== How can I have my site listed in the Moodle app site finder? ===
Please refer to our [[Moodle app guide for admins]] for instructions.
=== How can I debug errors in the app? ===
Go to the More tab and then to Settings > General. Enable "Display debug messages". This will show an explanatory message when an error occurs, alternatively, you can do a full debugging via: https://docs.moodle.org/dev/Moodle_Mobile_debugging_WS_requests

=== How can I disable features in the app? ===
Please go to ''Site administration > Mobile features > Disabled features'' and select all the features you want to disable.

To select multiple features you will have to use Ctrl (Cmd in Mac) + Click

=== How can I add custom menu items in the app? ===
You can add custom additional menu items in the "more" menu of the app, the one represented by three consecutive dots.

Please go to ''Site administration > Mobile features > Custom menu items'' and follow the instructions in [[Moodle_app_guide_for_admins#Custom_menu_items|Moodle app guide for admins]] for the correct format to use.

As a quick example:
Academy information|https://yoursite.com/mod/page/view.php?id=X |app|en|home

=== How can I customise the language strings in the app? ===

Please go to ''Site administration > Mobile features > Custom language strings'' and follow the instructions in [[Moodle_app_guide_for_admins#Custom_language_strings|Moodle app guide for admins]] for the format to use.

As a quick example:
core.user.student|Learner|en
core.user.student|Aprendiz|es

=== I can connect with my iPhone (or iPad) but not with my Android phone ===
This usually happens when the site is using https and the certificate is not correctly configured or it is using an old protocol, please use these pages to check this certificate: https://www.sslshopper.com/ssl-checker.html, https://www.geocerts.com/ssl_checker, and https://www.ssllabs.com/ssltest/analyze.html

'''The certificate of this site cannot be trusted by your device: TLS connection could not be established: javax.net.ssl.SSLHandshakeException'''

This error could be caused because in any of the certification paths there is a certificate using SHA-1. Starting Android 10 this is not allowed, more information here: https://developer.android.com/privacy-and-security/security-ssl

You could easily check the previous using https://www.ssllabs.com/ssltest/analyze.html and going to the Certification Paths -> Android section, if there is any mention to SHA-1 this could be the cause. You will need to upgrade your certificates to avoid using SHA-1.

=== My certificate is fine but I still can't connect ===
This is usually a server configuration problem caused by any of the following server configuration issues:

'''"Access to XMLHttpRequest at 'https://yoursite/webservice/rest/server.php?moodlewsrestformat=json<nowiki/>...' from origin '<nowiki>http://localhost'</nowiki> has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.'''

This is because a Proxy/Firewall/Web Server security module is removing automatically the Access-Control-Allow-Origin: * header that Moodle sets to allow Web Service requests.

It is totally secure to remove that Proxy/Firewall/Web Server rule/configuration because that header is only set by Moodle when needed.

'''"access-control-allow-origin cannot contain more than one origin".'''

iOS and Android apps do not allow the following header to contain more than one item: "Access-Control-Allow-Origin". For example, a header like this: Access-Control-Allow-Origin: *, https://mydomain.com will cause problems.

This HTTP header is not valid, according to the specification you can only specify a domain or a "*":
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin

Please, review if you have a Proxy/Firewall/Web Server adding automatically values to that HTTP header.

'''Security rules are blocking requests using the Accept-Charset header'''

Some security rules, such as OWASP ModSecurity, are blocking requests with this header that is sent by the Moodle App. In future releases of the app, this problem will be fixed. But in the meantime, you should disable it. Find more about this in MOBILE-4342.
=== My certificate is fine but the Moodle app is detecting http instead of https ===
If the Moodle app is detecting http instead of https, please revise config.php (check "wwwroot" as well as "httpswwwroot")
===After updating Moodle LMS to a recent version my users cannot login===
This only applies to sites that are configured to use log in via an embedded browser pointing to their Moodle site.
This behaviour could be related to this Moodle LMS issue: https://tracker.moodle.org/browse/MDL-81897.
There are several ways to fix this issue:
# Upgrade their Moodle site to any of the indicated version in the issue that will solve the problem
# Manually apply the patch here: https://github.com/jleyva/moodle/compare/462d5f04a8...MDL-81897-master
# Immediate workaround: Change the app authentication so it will launch in a separate browser, by going to Site admin > Mobile app authentication > Type of login (and select the option that mentions external/system browser), remember to Save Changes
We’d recommend doing 3) that will immediately address the issue that is affecting new logins.
===I can't get the app to work. What can I do?===
Assuming you have enabled mobile services on your site (please visit [[Moodle app guide for admins]]), please check:
# If your site uses an SSL certificate, it must be a trusted certificate, not self-signed. Please use these tools or a similar one to check that your certificate is valid: [https://www.sslshopper.com/ssl-checker.html SSL Checker], [https://www.geocerts.com/ssl_checker SSL Checker], and [https://www.ssllabs.com/ssltest/analyze.html SSL Server Test]. All the checks must be ok, including the "Certificate Chain Complete". Otherwise the app might work on iOS but not on Android.
# Make sure that the "Access-Control-Allow-Origin" header only contains one item. For example, a header like this: Access-Control-Allow-Origin: *, <nowiki>https://mydomain.com</nowiki> will cause problems.
# [[Debugging]] is disabled (in ''Site administration > Development > Debugging'')
# The ADOdb debug option is disabled if you are using the external database auth or enrolment plugin (in ''Plugins > Authentication > External database'' and in ''Plugins > Enrolment > External database'').
# SHA-1 https certificates are not supported anymore in Chrome, this means that the Android version of the app won't work for your site. If your site doesn't work in desktop Chrome or Chromium it won't work in the Android app. See https://blog.chromium.org/2014/09/gradually-sunsetting-sha-1.html for more information
# If you are using IIS check that Anonymous access is not disabled for the /webservice directory.
# If you are using a web application firewall like AWS WAF, StackPath, Barracuda, Cloudflare, Juniper, etc... try to temporary disable it to check if that's the cause. If so, you'll have to whitelist these endpoints: login/token.php, webservice/*, lib/ajax/*, media/player/vimeo/wsplayer.php and /tokenpluginfile.php
You can also add WAF rules to allow traffic by detecting the app user agent such as: (http.user_agent contains "MoodleMobile")
If you still have a problem, please post in the [https://moodle.org/mod/forum/view.php?id=7798 Moodle for mobile forum].

If the issue started after updating Moodle LMS please visit [https://docs.moodle.org/en/Moodle_app_FAQ#After_updating_Moodle_LMS_to_a_recent_version_my_users_cannot_login After updating Moodle LMS to a recent version my users cannot login].

=== I cannot access with old users, but I can with recently created ones! ===
Please, do a "Purge all caches" via the Moodle administration settings, this will solve the problem.
===I can't view the courses tab as an administrator===
The Moodle app only displays courses you are enrolled in. If you want to view a course as an admin, you need to enrol in it.
===My Moodle site uses a SSO auth method (Shibboleth, Google OAuth, etc) and the app is not working===
See the section 'Mobile authentication' in the [[Moodle app guide for admins]] for details of how to configure it.

If configured the app is still not connecting: If your site uses an SSL certificate, it must be a trusted certificate, not self-signed. Please use this tool or a similar one to check that your certificate is fine: [https://www.geocerts.com/ssl_checker SSL Checker]. All the checks must be OK, including the "Certificate Chain Complete".

If your SSO method is unable to authenticate when using an "embedded browser" (it gives an authentication error), please check if it works with a "browser window". If it does work with the browser window then it means your SSO is performing an HTTP redirect, and these kind of redirects aren't supported by the app (the request is redirected by the browser not passing the POST parameters). Unfortunately, this is something we cannot control in the Mobile app (it can't be handled via JavaScript). For further information, see http://stackoverflow.com/questions/228225/prevent-redirection-of-xmlhttprequest and http://stackoverflow.com/questions/4168784/ajax-redirection-handling

There are only 2 possible solutions: set the authentication via a "browser window" instead of an embedded one (please notice this won't work in the Linux desktop app), or remove the redirect from the SSO auth method.

===SSO is not working with my custom auth plugin===
SSO should work in any plugin if the plugin handles correctly the $SESSION->wantsurl, this is the way SSO works when it is launched via the app:
* It launchs this URL https://yourmoodle/admin/tool/mobile/launch.php?service=local_mobile&passport=abc in the device browser
* If the user is not logged in, the browser will redirect the user to the login page
* If the auth plugin used implements correctly the handling of the wantsurl session var, once the user has logged in, the browser should redirect back to the https://yourmoodle/admin/tool/mobile/launch.php?service=local_mobile&passport=abc URL that will launch the mobile app via the custom URL protocol
Custom auth plugins may be failing in the last step,not redirecting back to tool/mobile, this will happen only if the plugin does not support correctly the $SESSION->wantsurl.

The SAML plugin works correctly but some modifications of that plugin may not work if important lines are changed.
===I am having problems requesting an airnotifier access key===
If you have registered your site but are still unable to request an access key, please register your site on the Moodle Apps Portal https://apps.moodle.com once your site is registered there, an Airnotifier access key will be automatically generated for you.
=== Push notifications are not working ===
Please check [[Mobile app notifications#Troubleshooting]]
=== How notifications icon badges are updated ===
'''Android''': Not all Android devices support icon badges so in some cases badges will never display numbers, also, depending on the device only a badge indicating that there are new notifications will be displayed when receiving a Push notification when the app is not in the foreground.

'''iOS''': The icon badge counter is only updated when the app is open and it will reflect the number of notifications pending reading or the number of message senders that sent you a message you have not read yet

In general, for iOS the icon badge displayed number should match the one displayed at the bottom of the app (or it should be the sum of the notifications and messages badges) and is not an indicator of the number of Push notifications the user has received, it acts as a reminder of pending notifications to be read that only gets updated when the user open the apps

There is an open issue to improve the behaviour on iOS, please watch MDL-73707
=== I configured 'QR code access' to automatic login, but the app still asks for credentials ===
Automatic authentication only works for Pro and Premium sites. You can see the app plans [https://moodle.com/app/ in this site].

If you're getting an error saying that the device you're using to connect isn't in the same network as the device that displays the QR code but both devices are connected to the same network, please check the section: [[#ipmismatch:_.27Client_IP_address_mismatch.27|ipmissmatch: 'Client IP address mismatch']].

=== I can log in on my Moodle site but I see a blank page or the app styles broken ===
This is usually because your Moodle site has a customised CSS.

Please try leaving empty CSS (''mobilecssurl'') on Site administration > Mobile app > Mobile appearance. If that works, please read [https://docs.moodle.org/dev/Moodle_App_Remote_Themes Moodle App Remote Themes] and create a new CSS file using the variables mentioned there

===The Moodle app does not connect to MoodleBox (or other internal self-hosted systems)===
You will need to disable SSL to make the app works, please see this forum discussion for more information: https://moodle.org/mod/forum/discuss.php?d=424353#p1739474
===I think I found a bug with the app. Where can I report it?===
# Log in to the [https://tracker.moodle.org/browse/MOBILE Moodle Mobile tracker] (you'll need to [http://tracker.moodle.org/secure/Signup%21default.jspa create a tracker account] if you've not done so previously)
# Check whether the issue has already been reported by doing a [https://tracker.moodle.org/issues/?jql=project%20%3D%20MOBILE search]
# If not, report the bug by clicking the 'Create Issue' link at the top right of the page, selecting 'Moodle app' as the project
# Add a detailed description providing as much information as possible (Moodle version, app version, device model and operating system, etc...), then click the Create button
===How can I get the app in my language?===
[[File:setting the app lang.png|thumb|100px|Setting your language]]
The Moodle app automatically detects your mobile's language and displays in the same language (if the translation exists). Otherwise, you can set the app language in App settings > General.

See also a post explaining how multi-lang works in the Moodle app: [https://moodle.org/mod/forum/discuss.php?d=453445#p1825637 Re: Language selector missing in Moodle app]

If the Moodle app is not yet available in your language, please contribute a translation! See [https://docs.moodle.org/dev/Translating%20Moodle%20Mobile Translating Moodle Mobile] for details of what to do.

=== Changes made to a Moodle site URL can cause logged-in users’ data to fail when synchronising. ===
We recommend that administrators manually log out all users after a site rename. If your site URL changes and have site users that are using the mobile Moodle App we suggest the following:
* For users that have not yet logged in - we recommend sending them the new URL
* For users already using the mobile Moodle App and potentially logged in request them to:
** log out of the mobile Moodle App,
** delete the old site, and
** log in using the new URL
Logged in Moodle users can continue working with the previous URL (with cached information) but they will not be able to synchronise the new information (therefore not receiving new information from their teachers, and teachers not receiving data or submissions from those students).
* To avoid the risk of data not synchronising, we recommend the site administrator logs out all app users, by manually deleting their tokens:
** Go to Site administration
** Click Server
** Click Web services
** Click Manage tokens
** Delete the tokens
Take into account that you still need to request your users to log in using the new URL.

=== Embedded content is not working ===

This could be caused because your site is using a Content-Security-Policy that is preventing the app from embedding content.

You can easily detect this when an error like this is displayed (javascript console): Refused to load URL because it does not appear in the frame-ancestors directive of the Content Security Policy.

If that's the case, you'd need to add the following elements: http://localhost moodleappfs://localhost at the end of the "Content-Security-Policy" HTTP header:

An example of a CSP allowing embedding Vimeo videos in the site and content in the app:
Content-Security-Policy: frame-ancestors 'self' https://*.vimeocdn.com https://*.vimeows.com https://*.vimeo.com http://localhost moodleappfs://localhost ;

Other type of embedded content that does not work is content hosted by Microsoft tools that require session or any type of authentication, such as SharePoint content.

=== Some activities are displayed incorrectly (blank, just a vertical line, ..) on the app ===
Please visit the forum post [[https://moodle.org/mod/forum/discuss.php?d=461909#p1854918| Some lesson activities do not display at all]].

==Error messages==
=== 'Coding error: version.php file is missing for the component' ===
This error message indicates that that plugin is not correctly installed (or uninstalled) on the Moodle site you use (see [[Installing plugins]]). Please review the mod/certificate folder to check if the version.php file is missing (or has incorrect permissions) as well as purge cache too.
=== 'Can not find data record in database table external_functions' ===
This error usually happens due to a bad configuration or setting value in your Moodle site, please check:
# The user quota global setting should be an integer. For more details, see the discussion [https://moodle.org/mod/forum/discuss.php?d=320873 How to enable Moodle Mobile App for all accounts].
# The ''usermaxuploadfilesize'' should be an integer, please try to decrease the size. It can be configured in ''Site Administration > Security > Site Policies > Maximum uploaded file size''. The default value (Site upload limit) depends on the PHP configuration, you might have to change the value of ''upload_max_filesize'' and ''post_max_size'' in your ''php.ini'' file.
# The user "lang" field in the database is set to a correct value and existing language installed in the site. Some times the lang field is set via external systems to incorrect values or pointing to a language pack that was uninstalled. Please, note that to fix this you need direct access to the database and your 'user' and 'course' table.
==='Cannot connect: Verify that you have typed correctly the URL and that your site uses Moodle 3.5 or later'===
Take into account that the app will only connect to Moodle LMS sites version 3.5 onward.
Please also check:
# Mobile services are enabled for the site.
# The user is entering the correct URL for the site (see FAQ above)
# For https sites, the certificate is valid (see FAQ above)
==='Invalid Moodle site version. The Moodle app only supports Moodle systems 3.5 onwards'===
The app will only connect to Moodle LMS sites version 3.5 onward (see [https://docs.moodle.org/35/en/Upgrading Upgrade to 3.5] as well as [[Upgrade overview]]).
==='We lost connection; you need to reconnect. Your token is now invalid.' on my custom version of the Moodle app ===
Please check:
# You have followed all the steps listed in [https://docs.moodle.org/dev/Moodle%20Mobile%20Developing%20a%20plugin%20tutorial Moodle Mobile Developing a plugin tutorial]
# You have enabled the [[Capabilities/moodle/webservice:createtoken|moodle/webservice:createtoken]] for the authenticated user
==='No permission to create web service token for the service local_mobile' when attempting to log in (any user that it is not an admin)===
Please check you have enabled the moodle/webservice:createtoken for the authenticated user or any global role you want to allow to use the mobile app
==='No permission to create web service token for the service local_mobile' when attempting to log in as an admin===
You need to create a token for the admin account (only) as follows:
# Go to ''Site administration > Plugins > Web services > Manage tokens''
# Click Add
# Enter the admin username and select 'Moodle app additional features service' (i.e. do NOT leave it as 'Moodle app web service')
# Click the 'Save changes' button.
==='Invalid response value detected' when accessing the site ===
The user quota global setting should be an integer. For more details, see the discussion [https://moodle.org/mod/forum/discuss.php?d=320873 How to enable Moodle Mobile App for all accounts].
=== ' Invalid response value detected: Invalid external api response: the value is "", the server was expecting "raw" type" ===
This usually happens when there is a field with value NULL in a table in the database that should not be there. This may happen if your Moodle has been upgraded over many years and the database schema is broken.

To fix it, you can do the following:
* Detect the field that is causing the problem (it should be indicated before the error message)
* Fix the field, for example, for the password field in the lesson table: UPDATE mdl_lesson SET password = '' WHERE password IS NULL (remember that your table prefix can be different than mdl_)
==='Invalid response value detected' when accessing My Courses or Course Overview ===
This usually happens when a course uses a language that isn't installed in the site. Please make sure that all courses use valid languages. This can be easily checked in the database, table "course", there is a column named "lang".
==='A required parameter (username) was missing'===
This may happen if your site implements HTTP redirects; the request is redirected by the browser not passing the POST parameters.

Unfortunately, this is something we cannot control in the Mobile app (it can't be handled via JavaScript). For further information, see http://stackoverflow.com/questions/228225/prevent-redirection-of-xmlhttprequest and http://stackoverflow.com/questions/4168784/ajax-redirection-handling

The solution is to change the HTTP redirect and use an HTML page with a meta tag or JavaScript redirect.
==='Cannot get course contents'===
This usually happens when the course is using a course format plugin that was uninstalled from the server or that was not properly installed.

Please, reinstall again the course format plugin.
==='Access control exception' or 'Your authentication token is invalid or has expired'===
Please double-check that 'Enable web services for mobile devices' (''enablemobilewebservice'') is actually enabled. (It might be unabled if for example you have reseted some roles.)

If this error appears as soon as you enter the username and password for a new site, then it probably means that the token expiration time is badly configured. This is how to fix it:
# Go to ''Site administration > Security > Site security settings''.
# Find the setting named ''User created token duration''.
# If the value is set to 0 or it's too low, please set it back to a valid value (the default value is 12 weeks).
# Click the 'Save changes' button.

===ipmismatch: 'Client IP address mismatch'===
This error can appear when a user opens your site in a browser while using the app. This happens if your site is behind a proxy and you're using one of these Moodle versions o higher: 3.5.11, 3.6.9, 3.7.5, 3.8.2, 3.9.0.

To fix it:
# Go to ''Site administration > Administration > Server > HTTP''.
# Find the setting named ''Ignore reverse proxies'' (reverseproxyignore).
# Enter the IP of your proxy (or range of IPs).
# Click the 'Save changes' button.
If you are still experiencing issues please try to change this setting "getremoteaddrconf" (Logged IP address source) to the different existing values.

Finally, it is possible to disable the IP restriction checks for functionality such as the QR login, to do that, go to Site administration > Mobile app > Mobile app authentication, and disable the "QR authentication same IP check" setting.
=== 'The param "includestealthmodules" is invalid' ===
Please contact your learning organisation so they upgrade to at least Moodle 3.5.3 (see [https://docs.moodle.org/35/en/Upgrading Upgrade to 3.5] as well as [[Upgrade overview]]) or they manually apply the patch listed here [[MDL-63542]].

==Older versions of the Moodle app==
We always recommend using the last version of the Moodle App but some times users are still using older versions this is the reason we are keeping this list:

=== Some users are asked to reauthenticate too often when they browse the site (Moodle App <3.9.3) ===
This can happen if the app is sending too many variables to a WebService, e.g. because a course has a large number of sections and/or activities. This error was fixed in the 3.9.3 version of the app, but if you are using an older version of the app you can increase the value of ''max_input_vars'' in ''php.ini'' to fix it in your server.

=== After upgrading to 3.9.5 some of my plugins have stopped working ===
The Moodle App 3.9.5 version came with some breaking changes for plugins, most of the existing plugins have been updated to support the new changes.
Please check the following list of plugins that should work for 3.9.5 once you have upgraded to the latest version indicated in the document: https://docs.google.com/spreadsheets/d/1E9PqcUBpp9SAfQc_zJtX5tf9GeS3UN76A85IrrB4UDw/edit#gid=0

==Any further questions?==
Please post in the [http://moodle.org/mod/forum/view.php?id=7798 Moodle for mobile forum] on moodle.org.

[[Category:FAQ]]

[[de:Moodle Mobile - FAQ]]
[[ca:Moodle Mobile FAQ]]
[[es:Moodle app FAQ]]
[[fr:Moodle pour les mobiles]]
[[ja:バイルMoodle FAQ]]

Moodle app offline features

2025-10-15T08:50:54Z

Jleyva: /* See also */

{{Mobile}}

== Introduction ==

We live in a hyper-connected 5G world and we think the Internet is everywhere, but we usually forget about:

* Underdeveloped and developing countries
* Rural areas in big countries
* Kids with restricted data plans
* Shared internet connection in schools/classrooms
* Aerial and maritime traffic

One of the most powerful features of the Moodle app is that it enables us to work offline.

Students can browse course contents offline and participate in activities, then once they are connected back to the Internet, the app will synchronise all the necessary information with their Moodle site.

== How does the app store data for offline use? ==

* While browsing the site and its contents, though note that external contents (e.g. YouTube videos) are not downloaded and embedded files (audio, video) are not always downloaded (it depends on the user connection and file size)
* When the user downloads content by the download icon
** The user can use the “cloud” icon to download specific content or a complete section or course
** The user gets alerted when downloading large files
** If a resource has been updated in the server, a refresh icon will be shown.

===Why doesn’t the app pre-fetch/cache more data?===
# Because the user may have a monthly data plan
# Because the device storage space may be limited
# Massive data download might impact on the server performance

===What does the app consider to be a large file?===
* If the user is connected to a Wi-Fi network: large file >= 20MB
*If the user is connected to a data network: large file >= 2MB

== Course features offline support ==

* All course resources can be downloaded for offline (except URL)
* All course activities are supported (except Chat and External tool)
* Additional (non-standard) plugins usually don’t work offline
* Some functionality for certain activity modules does not work offline, see below for more information.

=== Assessment ===

The offline mode is disabled by default in Quiz and Lesson, however, the teacher can decide if they want to enable it.
* A quiz may be attempted offline only if:
** There is no time limit set
** The question behavior is deferred feedback (with or without CBM) only
** New in '''Moodle 4.3.1''' - the Quiz uses sequential navigation.
** There is no network address requirement

For detailed information about Quiz and how it works offline please see [[Moodle Mobile quiz offline attempts]].

=== Other activities ===
* SCORM and H5P packages are downloaded to the user’s device by default, there are settings to control this behaviour in order to prevent the packages from being downloaded (check this support pages for more information, [[Moodle app SCORM player]] and [[Moodle app H5P support]]).
* Wiki editing is not supported offline
* Glossaries entries can’t be deleted/updated offline
* Text assignment submissions can’t be edited offline
* Activities configured with availability conditions cannot be/are not downloaded for offline (the user will have to reconnect to be able to see activities unlocked by conditions recently met)

== What other features work offline?==

Apart from resources and activities certain course and site functionality are also available offline.

The offline support for completion is only for marking courses or activities completed (when viewed).

Conditioned activities are not downloaded for offline.

* Participants
* Grades
* Completion
* Notes
* Messaging
* Notifications
* Calendar events
* Private files
* Badges
* Blogs
* Rating
* Comments

== Synchronisation ==

Synchronisation works differently depending on the device
* Android: The app must be opened but it can be in the background (you can be using a different app).
* iOS (iPhone, iPad): The app must be opened and in the foreground (it has to be the device active app).
* Desktop: The app must be opened but it can be in the background (minimised).

🔋The battery is the key factor, mobile OS limits its usage

There are two ways of synchronising data:

* Automatic
** Runs regularly, every 10 minutes
* Manual
** The user will see a message indicating there is data pending synchronisation

===What happens with the student activity after synchronisation?===
Actions performed offline are logged and stored into the system with the synchronisation time, not with the time when they happened.
We are exploring ways to improve reporting via Moodle’s xAPI support.

For more information about how synchronisation works see [[Moodle app synchronization]].

== Configuration options ==

Site administrators can decide if they want:
* Disable completely the offline mode
* Disable all courses downloading
* Disable individual courses downloading

For disabling the previous features, please see [[Moodle app guide for admins]].

Users can decide if they want to allow synchronisation only when connected to a Wi-Fi network or also when using a data network.

==Moodle App Plans ==

When using the Moodle App, site admins can choose to subscribe to a paid plan or use the free version.

Plans limit the download of complete courses in one click.

Students can still download individual contents or sections.

We recommend a Premium plan subscription: https://apps.moodle.com

== See also ==
* [[Moodle app SCORM player]]
* [[Moodle app H5P support]]
* [[Moodle Mobile quiz]]
* [[Moodle app synchronization]]
* [https://www.youtube.com/watch?v=LqwG2XfSSiQ Use case: Scaling school leadership training through app-based Moodle learning]
* [https://www.youtube.com/watch?v=nk3SJuDduNs Use case: Reaching every learner; Scalable offline-first Moodle for African education]

[[es:Características de Moodle app sin conexión]]

Moodle app guide for admins

2025-08-08T10:41:17Z

Jleyva: /* Biometric Login */

{{Mobile}}
==Enable mobile services on your site==
Your site needs to have mobile access enabled so users can use the mobile app.

For sites using https, mobile access is enabled by default in new installations of Moodle 3.0 onwards.

For http sites, mobile access can be enabled by an administrator as follows:
# In ''Site administration > Mobile app > Mobile settings'' tick the 'Enable web services for mobile devices' checkbox. (For 4.0 version: In ''Site administration > Advanced features'' tick the 'Enable web services for mobile devices' checkbox
# Click the button to save changes.
If your site uses a [https://en.wikipedia.org/wiki/Transport_Layer_Security SSL certificate], it must be a trusted certificate. For security reasons the app doesn't work with self-signed certificates.

Please, verify that your certificate is valid via: https://www.geocerts.com/ssl_checker (you shouldn't see any warning).

If your site has the /login directory protected (frequently done when using the Shibboleth authentication method), you must enable access to the login/token.php script.
===Frame embedding===
If your sites uses [https://en.wikipedia.org/wiki/ReCAPTCHA reCaptcha], Vimeo videos or custom menu items (as described bellow) you must enable the admin setting "Allow frame embedding" (allowframembedding). Please, note this is not necessary since Moodle 3.7
===Is your site behind a proxy, or load balancer or complex network infrastructure?===
In that case, you may need to configure the "Ignore reserver proxies" settings in Site administration > Administration > Server > HTTP
==Register your site on the Moodle Apps Portal==
We strongly recommend you to register your site for free on the Moodle Apps portal: https://apps.moodle.com

You will be able to retrieve statistics like the number of active user devices receiving Push Notifications and upgrade to a Pro/Premium plan for enjoying exclusive features.
==Simplify user onboarding==
Upon opening the Moodle app, first-time users encounter a "Your site" field, where they have to input the URL of their Moodle site to access their courses. To ensure a smooth onboarding experience for new users, follow these steps:
# Enable the '''Site finder''' feature that allows users to find their Moodle site by name, eliminating the need to manually enter the site URL. To enable this feature, view [[Moodle app guide for admins#Have your site listed in the Moodle app site finder|Have your site listed in the Moodle app site finder]] below.
# Enable the '''QR login''' feature (view [[Moodle app guide for admins#QR Login|instructions]] below). This feature allows users to scan a QR code available on their Moodle profile to access their Moodle site directly from the app.
# For Android users and Moodle LMS 4.3 and later: Encourage users to install the Moodle app by following the '''Get the mobile app''' link at the bottom of any Moodle page (located within the "'''?'''" icon on the desktop version). When users install the app through this link, they will be automatically redirected to their site login screen, eliminating the need to manually enter the site URL.
# Alternatively, you can create a dedicated help page for the Moodle app. This help page should include a link to the Google Play version of the app and clearly indicate the site URL referrer. For example, if your Moodle site is mymoodlesite.com the link will be https://play.google.com/store/apps/details?id=com.moodle.moodlemobile&referrer=siteurl%3Dhttps%3A%2F%2Fmymoodlesite.com
Please note that options 3&4 are not compatible with Google Workspace accounts (the installation referrer will be ignored in that case).
==Have your site listed in the Moodle app site finder==
The Moodle apps site finder enables a user to easily find their Moodle site by entering the name (no need to enter the site URL)
===How can I have my site listed in the Moodle app site finder?===
Your site will be automatically listed in the site finder if:
* either your site is registered and listed with a link on [https://stats.moodle.org/sites/ Registered sites] and has over five hundred mobile users and you have been using the Moodle app for over a year
* or you have purchased a [https://moodle.com/app/ Pro or Premium Moodle app subscription].
You can arrange for your site to be listed in the site finder as follows:
* If your site is hosted by a Moodle Partner, please contact them to request for your site to be listed.
* If you have a MoodleCloud site, please log in to the Moodle Apps Portal where you will find an option to have your site listed.
Otherwise, to have your site listed in the site finder, you need to purchase a [https://moodle.com/app/ Pro or Premium Moodle app subscription] from the Moodle Apps Portal.
===I don’t want my site listed in the Moodle app site finder. How can I remove it?===
You can remove your site from the site finder as follows:
# Log in to the [https://apps.moodle.com/ Moodle Apps Portal]. (If you don't yet have an account, you can create one for free.)
# Go to ‘App customisation’ -> ‘Site Listing’ and uncheck the option ‘Visible’ then save changes.
Your site will then be immediately removed from the site finder.

Alternatively, you can remove your site from the site finder by updating your site registration:
# Log in to your Moodle site as admin and go to ‘Site administration’ -> Registration.
# Change ‘Site listing’ to either ‘Do not list my site’ or ‘Only display my site name’.
Your site will then be removed from the site finder within 24 hours.
==Mobile authentication==

===MFA===
The Moodle mobile app does not support MFA natively yet, however, you can redirect users to a browser to force the authentication process to behave exactly as Moodle LMS. You can do the previous via Site administration > Mobile authentication > Type of login and then select any of the options that mention browser.

===SSO authentication method===
If your site uses a SSO authentication method (Shibboleth, LDAP SSO, OAuth...), then select via a browser window or via an embedded browser for 'Type of login' (typeoflogin) in 'Mobile authentication' in the Site administration. (This setting is provided for older pre-Moodle 3.2 sites via the [[Moodle Mobile additional features]] plugin.)

The options 'browser window' and 'embedded browser' are very similar; the only difference is when redirecting the user to enter their credentials in the site, the site will be opened in the device's default browser (for browser window) or the site will be opened "embedded" in the mobile app (for embedded browser). The user experience is better in embedded browser, but not all the authentication plugins will work in embedded browser (for example, if JavaScript popups are required they must use the 'browser window'). The admin should check whether both options work, and if so, choose 'embedded browser'.

If you are using Google OAuth you will have to use the 'browser window' method because Google recently blocked authentication via 'embedded browsers'.

If your organisation uses a custom branded app and 'Type of login' is set to 'Via a browser window' or 'Via embedded browser', then a URL scheme (forcedurlscheme) may be set. This will result in only the custom branded app working for the site: the official Moodle Mobile app will not work.

===QR Login===
Please note that this feature requires Moodle 3.9 and is only available if you are enjoying a [https://moodle.com/app/ Pro/Premium plan].

As a site administrator, you can enable login via QR. Please go to Site administration > Mobile app > Mobile authentication and select "QR code with automatic login" in the "QR code access" setting

Once enabled, your students will be able to login in the app by scanning a QR code available on their Moodle site profile.
===Biometric Login===
This feature is only available to Pro, [https://apps.moodle.com Premium plan customers] and in Branded Moodle Apps developed by Moodle HQ.

Biometric login allows your users to log in to your site via the Moodle App on Android and iOS devices using their fingerprint, face recognition or any other biometric option available on their mobile device. This makes the login process simpler, faster and more secure, and is specially useful if Autologout is enabled on your site.

'''Enabling biometric login for your site'''

You can enable Biometric login as an authentication method through the Moodle Apps Portal, going to App customisation > Authentication > Biometric login, and then selecting “Enable biometric login”. Your users will then be able to choose whether they want to use Biometric login or not.

For security reasons, users may be prompted to re-enter their credentials periodically. This interval is determined by the 'User created token duration' (tokenduration) security setting, which is set to a default duration of three months.

'''Setting up biometric login as a user'''

To use biometric login in the Moodle App, users must have biometric authentication enabled in their own device's settings (e.g. FaceID or TouchID for iOs users, or Fingerprints for Android users).

The first three times users log in to the app after you enable Biometric login, they will see a notification telling them that they can activate this new authentication method to access the app (provided that they have biometric authentication enabled in their device's settings).

Users can activate and deactivate their biometric login any time in the Moodle App in User account > Preferences.

===Auto logout===
From Moodle LMS 4.3 onwards, you can enhance security by enforcing automatic logout for your users when they leave or close the app, or it goes to the background.

You can even set your own custom re-authentication time, to suit your organisation's security requirements.

To activate auto logout, go to Site administration > Mobile app > Mobile authentication.

This feature is particularly effective when paired with Biometric login, since that streamlines the login process for your users.

== Customise your app theme ==
The app can also retrieve your custom styles from your Moodle site. Since the app is a HTML5 app, you can safely apply any CSS, CSS2 and CSS3 style.

Go to ''Administration > Site administration > Mobile app > Mobile appearance'' and enter in the mobilecssurl field a valid URL pointing to a CSS file containing your custom styles.

The CSS should be placed inside your Moodle installation (in your custom theme or inside a local plugin).

'''For example:''' ''https://mymoodlesite.com/theme/mytheme/style/mymobileapp.css''

Once the user is logged in the app, remote CSS files for applying your custom styles are regularly retrieved.

Notice that on the first time a user opens the app, he will see the default "orange" style. Your custom styles will be applied once the user has added a site in the app.

For further information, see the dev docs [https://docs.moodle.org/dev/Moodle%20Mobile%20Themes Moodle Mobile Themes].

If you want your own custom branding for your organization, Moodle offers the The [https://moodle.com/branded-app Branded Moodle Mobile app] service, please visit https://moodle.com/app/ for more information.
== Moodle Mobile additional features plugin for old Moodle sites ==
For old Moodle sites it is recommended to install the [[Moodle Mobile additional features]] plugin.
== Notifications ==
You might find them annoying but push notifications keeps you and your users informed and updated on everything about the app. Moodle only send useful and important notifications such as new features or service disruptions.

Enabling push notifications is easy! An administrator can enable it by connecting their Moodle site/s to our free Notifications server available (only) for registered Moodle sites.

An access key can be obtained via ''Site administration > General > Messaging > Notification settings''. Be sure the 'Mobile' is enabled and then click the link to settings, on the next page select ''Request access key''. (For Moodle site versions 3.5 and 3.6 an access key can be obtained via ''Site administration > Plugins > Message outputs > Manage message outputs''. Then by clicking the link to the Mobile settings, on the next page select ''Request access key''.)

The full guide on enabling push notifications can be found here: [[Mobile app notifications]]
== App banners ==
[[File:app banner.png|thumb|Moodle Mobile app banner]]
App banners let your users know a mobile app is available for the site. App banners are only displayed when accessing the site using a mobile browser.

App banners are disabled by default. They can be enabled in 'Mobile appearance' in the Site administration.

If you are using a custom mobile app, you must provide the unique identifier for the iOS and Android app; if you use the Moodle Mobile app, the settings may be left as default.

Please, notice the following:
* App banners for iOS devices (iPhone, iPad or iPod) are only shown when accessing the site using the Safari browser and the mobile app is not installed on the device yet. App banners are not displayed when using private browsing either.
* App banners for Android devices are only shown in very recent Chrome browser versions and when the app is not installed. Note also that Chrome uses an engagement heuristic that will display the banner only under certain conditions, like interactions with the site, the last time you interacted with it, etc. You can remove the engagement restriction check by disabling this special chrome flag: chrome://flags/#bypass-app-banner-engagement-checks. Please note also that certain custom Android versions (such as Samsung and Huawei ones) do not always support this feature

=='Get the mobile app' link==
In Moodle 3.4 onwards, the link 'Get the mobile app' in the footer of each page on the site encourages users to make use of the mobile app.

By default, the link is https://download.moodle.org/mobile however the setting 'App download page' can be changed e.g. for sites using a branded mobile app.

If mobile services are not enabled for the site, then the 'Get the mobile app' link is not displayed.

To prevent the 'Get the mobile app' link being displayed, simply remove the URL from the 'App download page' setting and save changes.
== Configuring the app from your site ==
'''IMPORTANT''': Please notice that the type and number of features that you can customise depend on your Moodle Apps plan, you can register for free on https://apps.moodle.com to check the different plans.

In Moodle 3.3 onwards, or with the [[Moodle Mobile additional features]] plugin, settings in the Site administration enable admins to configure the app.
* In Moodle 3.3 onwards go to ''Site administration > Mobile features''
* In sites with the Moodle Mobile additional features plugin installed, go to ''Site administration > Plugins > Local plugins > Mobile additional features''
===Force log out===
Replace the Change site option to "Log out" so that users must enter their credentials on their next access. This is useful for custom mobile apps, as there is no reason for users wanting to switch to a different site.
===Disabled features===
The mobile app may be simplified by removing unwanted features. Some items may already be not available in the app because they are not enabled on your site.

Options to remove include:

* Offline use
* Blocks (Note that from '''Moodle 4.3.1''' the Global search and Search forums blocks can be removed.)
* Comments
* Ratings
* Tags
* Create new account
* Responsive menu items
* Main menu
** Site home
** My courses
** Dashboard
** Calendar
** Notifications
** Messages
** Grades
** My learning plans
** Blog
** Files
** Web page
** Help
* Course
** Blocks
** Blog
** Search
** Competencies
** Participants
** Grades
** Course completion
** Notes
** Download course (new in 3.5)
** Download courses (new in 3.5)
* User
** Blog
** Badges
** Competencies
** Course completion
** Grades
** Send message
** Add contact
** Block contact
** Add a new note
** User picture
* Files
** Private files
** Ste files
** Upload
* Modules (Each module can be disabled separately)
* Blocks (Each block available in the app can be disabled separately)

===Custom menu items===
Additional items can be added to the app main menu (the more menu), such as a link to a different grade book.

In order to do so go to "Site administration > Mobile features > Custom menu items"

Each custom menu item should have the format: item text, link URL, link-opening method and language code (optional, for displaying the item to users of the specified language only), icon (optional, the name of the icon from https://ionicons.com) separated by pipe characters.

Possible link-opening methods are:
* app - for linking to an activity supported by the app i.e. almost all activity types, as listed in [[Moodle Mobile features]].
* inappbrowser - for linking to external URLs or site functionalities not supported by the app. The link will open in a browser inside the app overlaying the complete screen.
* browser - as for inappbrowser except that the link will instead open in the device default browser outside the app.
* embedded - as for inappbrowser except that the link will instead open in an iframe in a new page in the app. (For this option you may need to enable the admin setting "Allow frame embedding" (allowframembedding)
Tip: If you add a custom menu item and save changes, then it doesn't appear in the app main menu, double check that the item is correctly formatted.

Please, note that if custom menu items have the same URL, same link-opening method, and same language only the first custom menu item will be shown.

Please, note that if the app is using a language not indicated in the previous list, the first language in the list will be used. (So if you have a custom menu item in English (en) and French (fr), and the app is using Spanish the user will still see that custom menu item in English)

If you want options tied to a language, you can append _only to the language code, for example:
en_only
es_only, will display the custom menu item only when the app language is English or Spanish.

Example of a menu item (it will display a home icon followed by Academy information linking to the URL indicated):
Academy information|https://yoursite.com/mod/page/view.php?id=X |app|en|home

===Responsive menu items===
From 3.7 onwards menu items on bottom tabs are moved to the side of the screen on big screens. Also the number of items displayed on the menu may vary:
* On small screens (usually phones) from 2 to 5 items will be displayed depending on the size of the screen.
* On big screens (usually tablets an desktop version) more than 2 items will be displayed without limit.
If '''Responsive menu items''' is selected in Disabled features items will be displayed in side of bottom anyway but 5 items will be displayed in all cases without depending on the size of the screen.
===Custom language strings ===
Words and phrases displayed in the app can be customised via the "Site administration > Mobile app features > Custom language strings" (customlangstrings) setting.

Enter each custom language string on a new line with format: string identifier, custom language string and language code, separated by pipe characters. For example:
core.user.student|Learner|en
core.user.student|Aprendiz|es
The complete list of string identifiers is listed in https://latest.apps.moodledemo.net/assets/lang/en.json

The string identifier is before the colon.

For example:

"core.user.student": "Student",

means that the string "Student" has string identifier "core.user.student".
==Analytics and stats==

===Usage statistics from your Moodle site===

To retrieve information about the Moodle app usage, site administrators and teachers can check the site, course or activity logs.

* Site logs are available via "Site administration > Reports > Logs"
* Course logs are available via the course options (on top of the course page) "Reports > Logs"
* Activity logs are available via the activity page, on top you will find "Reports > Logs"

Among the log filters, there is a field called "All sources" with an option "Web Service/ws" that can be used to filter the entry logs generated by the mobile application.

You can compare the number of log entries generated by the "Web" versus "Web Service" (mobile app) to have an overall idea about how your users use the platform.

Please, notice that if you have custom "Web Services" or an installed plugin that uses Web Services, you will also see entries for them under the same filter.

If you have access to the site database, the table "external_tokens" has a "lastaccess" timestamp field that could be used to obtain active users of the app every day.

===Integration with Matomo analytics===
Note: This feature is available for [https://apps.moodle.com Premium app plans and Branded Moodle Apps]. To use this integration, you will need to have your own instance of Matomo.

Matomo is an open source web analytics tool that helps you monitor traffic to your Moodle site, including app activity.

'''Connecting to your Matomo instance in the Apps portal'''
[[File:Captura de pantalla 2023-11-14 a las 12.03.36.png|thumb|Moodle App Matomo Integration set up]]
To use Matomo to track app activity on your Moodle site, you will need to have your own instance of Matomo analytics, and to add your Moodle site as one of your measurable websites (see instructions on [https://matomo.org/faq/how-to/create-and-manage-websites/ Matomo’s website]). Then, follow these steps:
# Log in to the [https://apps.moodle.com Apps portal].
# Go to '''App customisation''' > '''Analytics''' > '''Matomo analytics'''.
# Check '''Track app activity'''.
# Add your '''Matomo URL''' - that's the URL of your Matomo instance, for example https://yoursite.matomo.cloud.
# Add the '''Website ID''' associated with your Moodle site in Matomo. To obtain this ID:
## Log in to your Matomo account.
## Go to '''Administration''' using the gear icon on the right side of the top navigation bar.
## On the left-hand panel, select '''Websites''' > '''Manage'''.
## In your list of measurables, find the Moodle site in which you want to track app activity. The '''ID''' of the measurable is the '''Website ID''' you need to enter in the apps portal.
# Click '''Save changes''' to establish the connection and start tracking app activity.
# If you'd like to stop tracking at any time, uncheck '''Track app activity''' and then save changes.

To filter Matomo data to isolate mobile app usage from Moodle site interactions, follow these steps:
[[File:Captura de pantalla 2023-11-14 a las 12.05.05.png|thumb|Moodle App Matomo referrer set-up]]
# Log in to your Matomo account.
# Click '''All visits''' at the top of the page
# Create a custom segment by applying this configuration: “Referrer URL” “is” “https://moodlemobile”
# To only see Moodle site interactions, do the following: “Referrer URL” “is not” “https://moodlemobile”

Please notice that the integration with Matomo does not work offline.

===Google Analytics for Firebase===
Only available when purchasing a [https://moodle.com/branded-app/ Branded Moodle App].

Google Analytics for Firebase is a free tool that provides valuable insights and data about how users interact with mobile apps.

Please notice that the integration with Google Analytics for Firebase does not work offline.

===Google Play and Apple App Store statistics===

If you have a custom mobile application, you can access statistics about app downloads and user engagement such as weekly active users and devices.

Google play:
# Go to Google Play console: https://play.google.com/console
# Select your app from the list.
# Navigate to specific tabs, such as "Statistics"

Apple App Store:
# Log in to App Store Connect: https://appstoreconnect.apple.com/
# Go to "App Analytics" from the dashboard.

==Web services token duration==
From Moodle 3.4 onwards, an admin can set how long a web services token created by a user (for example via the mobile app) is valid. (In previous versions of Moodle a token was valid for 3 months.)

The setting that dictates the previous 'User created token duration' (tokenduration) can be found under the Security section.
==App's cache==
The app caches WebService requests to decrease data usage and increase the app's speed. When the app needs to get some data from Moodle, it will use a cached request as long as it isn't expired.

This cache was improved in Moodle App 3.7.0, now there are several cache times depending on the WS being called. This means that some requests will expire more often than others. Also, if the user isn't using a WiFi connection, the expiration time will also be longer to decrease the data usage. These cache times cannot be configured using a Moodle setting.
==See also==
* [https://moodle.academy/course/view.php?id=100 Moodle App Configuration]- a free self-paced course for admins on Moodle Academy.
* [[Moodle Mobile FAQ]] for other administration-related mobile app questions.
* [[Moodle app security]]
* [https://docs.moodle.org/dev/Moodle%20Mobile%20debugging%20WS%20requests dev:Moodle Mobile debugging WS requests] - a guide to helping you find and report problems with the Moodle Mobile app on your site
* [https://docs.moodle.org/dev/%20Moodle%20Mobile%20Roadmap dev: Moodle Mobile Roadmap]
* [https://docs.moodle.org/dev/Moodle%20Mobile%20release%20notes dev:Moodle Mobile release notes]
* [https://docs.moodle.org/dev/Moodle%20Mobile Moodle Mobile developer docs]
* [[Moodle Mobile availability plugin]]
* [[Mobile web services]]
[https://docs.moodle.org/fr/ Guide mobile pour administrateurs]
[https://docs.moodle.org/es/Moodle app guía para administradores]
[https://docs.moodle.org/de/Moodle App - Anleitung für Administrator/innen]

Moodle app guide for admins

2025-07-28T07:08:59Z

Jleyva: /* Usage statistics from your Moodle site */

{{Mobile}}
==Enable mobile services on your site==
Your site needs to have mobile access enabled so users can use the mobile app.

For sites using https, mobile access is enabled by default in new installations of Moodle 3.0 onwards.

For http sites, mobile access can be enabled by an administrator as follows:
# In ''Site administration > Mobile app > Mobile settings'' tick the 'Enable web services for mobile devices' checkbox. (For 4.0 version: In ''Site administration > Advanced features'' tick the 'Enable web services for mobile devices' checkbox
# Click the button to save changes.
If your site uses a [https://en.wikipedia.org/wiki/Transport_Layer_Security SSL certificate], it must be a trusted certificate. For security reasons the app doesn't work with self-signed certificates.

Please, verify that your certificate is valid via: https://www.geocerts.com/ssl_checker (you shouldn't see any warning).

If your site has the /login directory protected (frequently done when using the Shibboleth authentication method), you must enable access to the login/token.php script.
===Frame embedding===
If your sites uses [https://en.wikipedia.org/wiki/ReCAPTCHA reCaptcha], Vimeo videos or custom menu items (as described bellow) you must enable the admin setting "Allow frame embedding" (allowframembedding). Please, note this is not necessary since Moodle 3.7
===Is your site behind a proxy, or load balancer or complex network infrastructure?===
In that case, you may need to configure the "Ignore reserver proxies" settings in Site administration > Administration > Server > HTTP
==Register your site on the Moodle Apps Portal==
We strongly recommend you to register your site for free on the Moodle Apps portal: https://apps.moodle.com

You will be able to retrieve statistics like the number of active user devices receiving Push Notifications and upgrade to a Pro/Premium plan for enjoying exclusive features.
==Simplify user onboarding==
Upon opening the Moodle app, first-time users encounter a "Your site" field, where they have to input the URL of their Moodle site to access their courses. To ensure a smooth onboarding experience for new users, follow these steps:
# Enable the '''Site finder''' feature that allows users to find their Moodle site by name, eliminating the need to manually enter the site URL. To enable this feature, view [[Moodle app guide for admins#Have your site listed in the Moodle app site finder|Have your site listed in the Moodle app site finder]] below.
# Enable the '''QR login''' feature (view [[Moodle app guide for admins#QR Login|instructions]] below). This feature allows users to scan a QR code available on their Moodle profile to access their Moodle site directly from the app.
# For Android users and Moodle LMS 4.3 and later: Encourage users to install the Moodle app by following the '''Get the mobile app''' link at the bottom of any Moodle page (located within the "'''?'''" icon on the desktop version). When users install the app through this link, they will be automatically redirected to their site login screen, eliminating the need to manually enter the site URL.
# Alternatively, you can create a dedicated help page for the Moodle app. This help page should include a link to the Google Play version of the app and clearly indicate the site URL referrer. For example, if your Moodle site is mymoodlesite.com the link will be https://play.google.com/store/apps/details?id=com.moodle.moodlemobile&referrer=siteurl%3Dhttps%3A%2F%2Fmymoodlesite.com
Please note that options 3&4 are not compatible with Google Workspace accounts (the installation referrer will be ignored in that case).
==Have your site listed in the Moodle app site finder==
The Moodle apps site finder enables a user to easily find their Moodle site by entering the name (no need to enter the site URL)
===How can I have my site listed in the Moodle app site finder?===
Your site will be automatically listed in the site finder if:
* either your site is registered and listed with a link on [https://stats.moodle.org/sites/ Registered sites] and has over five hundred mobile users and you have been using the Moodle app for over a year
* or you have purchased a [https://moodle.com/app/ Pro or Premium Moodle app subscription].
You can arrange for your site to be listed in the site finder as follows:
* If your site is hosted by a Moodle Partner, please contact them to request for your site to be listed.
* If you have a MoodleCloud site, please log in to the Moodle Apps Portal where you will find an option to have your site listed.
Otherwise, to have your site listed in the site finder, you need to purchase a [https://moodle.com/app/ Pro or Premium Moodle app subscription] from the Moodle Apps Portal.
===I don’t want my site listed in the Moodle app site finder. How can I remove it?===
You can remove your site from the site finder as follows:
# Log in to the [https://apps.moodle.com/ Moodle Apps Portal]. (If you don't yet have an account, you can create one for free.)
# Go to ‘App customisation’ -> ‘Site Listing’ and uncheck the option ‘Visible’ then save changes.
Your site will then be immediately removed from the site finder.

Alternatively, you can remove your site from the site finder by updating your site registration:
# Log in to your Moodle site as admin and go to ‘Site administration’ -> Registration.
# Change ‘Site listing’ to either ‘Do not list my site’ or ‘Only display my site name’.
Your site will then be removed from the site finder within 24 hours.
==Mobile authentication==

===MFA===
The Moodle mobile app does not support MFA natively yet, however, you can redirect users to a browser to force the authentication process to behave exactly as Moodle LMS. You can do the previous via Site administration > Mobile authentication > Type of login and then select any of the options that mention browser.

===SSO authentication method===
If your site uses a SSO authentication method (Shibboleth, LDAP SSO, OAuth...), then select via a browser window or via an embedded browser for 'Type of login' (typeoflogin) in 'Mobile authentication' in the Site administration. (This setting is provided for older pre-Moodle 3.2 sites via the [[Moodle Mobile additional features]] plugin.)

The options 'browser window' and 'embedded browser' are very similar; the only difference is when redirecting the user to enter their credentials in the site, the site will be opened in the device's default browser (for browser window) or the site will be opened "embedded" in the mobile app (for embedded browser). The user experience is better in embedded browser, but not all the authentication plugins will work in embedded browser (for example, if JavaScript popups are required they must use the 'browser window'). The admin should check whether both options work, and if so, choose 'embedded browser'.

If you are using Google OAuth you will have to use the 'browser window' method because Google recently blocked authentication via 'embedded browsers'.

If your organisation uses a custom branded app and 'Type of login' is set to 'Via a browser window' or 'Via embedded browser', then a URL scheme (forcedurlscheme) may be set. This will result in only the custom branded app working for the site: the official Moodle Mobile app will not work.

===QR Login===
Please note that this feature requires Moodle 3.9 and is only available if you are enjoying a [https://moodle.com/app/ Pro/Premium plan].

As a site administrator, you can enable login via QR. Please go to Site administration > Mobile app > Mobile authentication and select "QR code with automatic login" in the "QR code access" setting

Once enabled, your students will be able to login in the app by scanning a QR code available on their Moodle site profile.
===Biometric Login===
This feature is only available to Pro and [https://apps.moodle.com Premium plan customers].

Biometric login allows your users to log in to your site via the Moodle App on Android and iOS devices using their fingerprint, face recognition or any other biometric option available on their mobile device. This makes the login process simpler, faster and more secure, and is specially useful if Autologout is enabled on your site.

'''Enabling biometric login for your site'''

You can enable Biometric login as an authentication method through the Moodle Apps Portal, going to App customisation > Authentication > Biometric login, and then selecting “Enable biometric login”. Your users will then be able to choose whether they want to use Biometric login or not.

For security reasons, users may be prompted to re-enter their credentials periodically. This interval is determined by the 'User created token duration' (tokenduration) security setting, which is set to a default duration of three months.

'''Setting up biometric login as a user'''

To use biometric login in the Moodle App, users must have biometric authentication enabled in their own device's settings (e.g. FaceID or TouchID for iOs users, or Fingerprints for Android users).

The first three times users log in to the app after you enable Biometric login, they will see a notification telling them that they can activate this new authentication method to access the app (provided that they have biometric authentication enabled in their device's settings).

Users can activate and deactivate their biometric login any time in the Moodle App in User account > Preferences.
===Auto logout===
From Moodle LMS 4.3 onwards, you can enhance security by enforcing automatic logout for your users when they leave or close the app, or it goes to the background.

You can even set your own custom re-authentication time, to suit your organisation's security requirements.

To activate auto logout, go to Site administration > Mobile app > Mobile authentication.

This feature is particularly effective when paired with Biometric login, since that streamlines the login process for your users.

== Customise your app theme ==
The app can also retrieve your custom styles from your Moodle site. Since the app is a HTML5 app, you can safely apply any CSS, CSS2 and CSS3 style.

Go to ''Administration > Site administration > Mobile app > Mobile appearance'' and enter in the mobilecssurl field a valid URL pointing to a CSS file containing your custom styles.

The CSS should be placed inside your Moodle installation (in your custom theme or inside a local plugin).

'''For example:''' ''https://mymoodlesite.com/theme/mytheme/style/mymobileapp.css''

Once the user is logged in the app, remote CSS files for applying your custom styles are regularly retrieved.

Notice that on the first time a user opens the app, he will see the default "orange" style. Your custom styles will be applied once the user has added a site in the app.

For further information, see the dev docs [https://docs.moodle.org/dev/Moodle%20Mobile%20Themes Moodle Mobile Themes].

If you want your own custom branding for your organization, Moodle offers the The [https://moodle.com/branded-app Branded Moodle Mobile app] service, please visit https://moodle.com/app/ for more information.
== Moodle Mobile additional features plugin for old Moodle sites ==
For old Moodle sites it is recommended to install the [[Moodle Mobile additional features]] plugin.
== Notifications ==
You might find them annoying but push notifications keeps you and your users informed and updated on everything about the app. Moodle only send useful and important notifications such as new features or service disruptions.

Enabling push notifications is easy! An administrator can enable it by connecting their Moodle site/s to our free Notifications server available (only) for registered Moodle sites.

An access key can be obtained via ''Site administration > General > Messaging > Notification settings''. Be sure the 'Mobile' is enabled and then click the link to settings, on the next page select ''Request access key''. (For Moodle site versions 3.5 and 3.6 an access key can be obtained via ''Site administration > Plugins > Message outputs > Manage message outputs''. Then by clicking the link to the Mobile settings, on the next page select ''Request access key''.)

The full guide on enabling push notifications can be found here: [[Mobile app notifications]]
== App banners ==
[[File:app banner.png|thumb|Moodle Mobile app banner]]
App banners let your users know a mobile app is available for the site. App banners are only displayed when accessing the site using a mobile browser.

App banners are disabled by default. They can be enabled in 'Mobile appearance' in the Site administration.

If you are using a custom mobile app, you must provide the unique identifier for the iOS and Android app; if you use the Moodle Mobile app, the settings may be left as default.

Please, notice the following:
* App banners for iOS devices (iPhone, iPad or iPod) are only shown when accessing the site using the Safari browser and the mobile app is not installed on the device yet. App banners are not displayed when using private browsing either.
* App banners for Android devices are only shown in very recent Chrome browser versions and when the app is not installed. Note also that Chrome uses an engagement heuristic that will display the banner only under certain conditions, like interactions with the site, the last time you interacted with it, etc. You can remove the engagement restriction check by disabling this special chrome flag: chrome://flags/#bypass-app-banner-engagement-checks. Please note also that certain custom Android versions (such as Samsung and Huawei ones) do not always support this feature

=='Get the mobile app' link==
In Moodle 3.4 onwards, the link 'Get the mobile app' in the footer of each page on the site encourages users to make use of the mobile app.

By default, the link is https://download.moodle.org/mobile however the setting 'App download page' can be changed e.g. for sites using a branded mobile app.

If mobile services are not enabled for the site, then the 'Get the mobile app' link is not displayed.

To prevent the 'Get the mobile app' link being displayed, simply remove the URL from the 'App download page' setting and save changes.
== Configuring the app from your site ==
'''IMPORTANT''': Please notice that the type and number of features that you can customise depend on your Moodle Apps plan, you can register for free on https://apps.moodle.com to check the different plans.

In Moodle 3.3 onwards, or with the [[Moodle Mobile additional features]] plugin, settings in the Site administration enable admins to configure the app.
* In Moodle 3.3 onwards go to ''Site administration > Mobile features''
* In sites with the Moodle Mobile additional features plugin installed, go to ''Site administration > Plugins > Local plugins > Mobile additional features''
===Force log out===
Replace the Change site option to "Log out" so that users must enter their credentials on their next access. This is useful for custom mobile apps, as there is no reason for users wanting to switch to a different site.
===Disabled features===
The mobile app may be simplified by removing unwanted features. Some items may already be not available in the app because they are not enabled on your site.

Options to remove include:

* Offline use
* Blocks (Note that from '''Moodle 4.3.1''' the Global search and Search forums blocks can be removed.)
* Comments
* Ratings
* Tags
* Create new account
* Responsive menu items
* Main menu
** Site home
** My courses
** Dashboard
** Calendar
** Notifications
** Messages
** Grades
** My learning plans
** Blog
** Files
** Web page
** Help
* Course
** Blocks
** Blog
** Search
** Competencies
** Participants
** Grades
** Course completion
** Notes
** Download course (new in 3.5)
** Download courses (new in 3.5)
* User
** Blog
** Badges
** Competencies
** Course completion
** Grades
** Send message
** Add contact
** Block contact
** Add a new note
** User picture
* Files
** Private files
** Ste files
** Upload
* Modules (Each module can be disabled separately)
* Blocks (Each block available in the app can be disabled separately)

===Custom menu items===
Additional items can be added to the app main menu (the more menu), such as a link to a different grade book.

In order to do so go to "Site administration > Mobile features > Custom menu items"

Each custom menu item should have the format: item text, link URL, link-opening method and language code (optional, for displaying the item to users of the specified language only), icon (optional, the name of the icon from https://ionicons.com) separated by pipe characters.

Possible link-opening methods are:
* app - for linking to an activity supported by the app i.e. almost all activity types, as listed in [[Moodle Mobile features]].
* inappbrowser - for linking to external URLs or site functionalities not supported by the app. The link will open in a browser inside the app overlaying the complete screen.
* browser - as for inappbrowser except that the link will instead open in the device default browser outside the app.
* embedded - as for inappbrowser except that the link will instead open in an iframe in a new page in the app. (For this option you may need to enable the admin setting "Allow frame embedding" (allowframembedding)
Tip: If you add a custom menu item and save changes, then it doesn't appear in the app main menu, double check that the item is correctly formatted.

Please, note that if custom menu items have the same URL, same link-opening method, and same language only the first custom menu item will be shown.

Please, note that if the app is using a language not indicated in the previous list, the first language in the list will be used. (So if you have a custom menu item in English (en) and French (fr), and the app is using Spanish the user will still see that custom menu item in English)

If you want options tied to a language, you can append _only to the language code, for example:
en_only
es_only, will display the custom menu item only when the app language is English or Spanish.

Example of a menu item (it will display a home icon followed by Academy information linking to the URL indicated):
Academy information|https://yoursite.com/mod/page/view.php?id=X |app|en|home

===Responsive menu items===
From 3.7 onwards menu items on bottom tabs are moved to the side of the screen on big screens. Also the number of items displayed on the menu may vary:
* On small screens (usually phones) from 2 to 5 items will be displayed depending on the size of the screen.
* On big screens (usually tablets an desktop version) more than 2 items will be displayed without limit.
If '''Responsive menu items''' is selected in Disabled features items will be displayed in side of bottom anyway but 5 items will be displayed in all cases without depending on the size of the screen.
===Custom language strings ===
Words and phrases displayed in the app can be customised via the "Site administration > Mobile app features > Custom language strings" (customlangstrings) setting.

Enter each custom language string on a new line with format: string identifier, custom language string and language code, separated by pipe characters. For example:
core.user.student|Learner|en
core.user.student|Aprendiz|es
The complete list of string identifiers is listed in https://latest.apps.moodledemo.net/assets/lang/en.json

The string identifier is before the colon.

For example:

"core.user.student": "Student",

means that the string "Student" has string identifier "core.user.student".
==Analytics and stats==

===Usage statistics from your Moodle site===

To retrieve information about the Moodle app usage, site administrators and teachers can check the site, course or activity logs.

* Site logs are available via "Site administration > Reports > Logs"
* Course logs are available via the course options (on top of the course page) "Reports > Logs"
* Activity logs are available via the activity page, on top you will find "Reports > Logs"

Among the log filters, there is a field called "All sources" with an option "Web Service/ws" that can be used to filter the entry logs generated by the mobile application.

You can compare the number of log entries generated by the "Web" versus "Web Service" (mobile app) to have an overall idea about how your users use the platform.

Please, notice that if you have custom "Web Services" or an installed plugin that uses Web Services, you will also see entries for them under the same filter.

If you have access to the site database, the table "external_tokens" has a "lastaccess" timestamp field that could be used to obtain active users of the app every day.

===Integration with Matomo analytics===
Note: This feature is available for [https://apps.moodle.com Premium app plans and Branded Moodle Apps]. To use this integration, you will need to have your own instance of Matomo.

Matomo is an open source web analytics tool that helps you monitor traffic to your Moodle site, including app activity.

'''Connecting to your Matomo instance in the Apps portal'''
[[File:Captura de pantalla 2023-11-14 a las 12.03.36.png|thumb|Moodle App Matomo Integration set up]]
To use Matomo to track app activity on your Moodle site, you will need to have your own instance of Matomo analytics, and to add your Moodle site as one of your measurable websites (see instructions on [https://matomo.org/faq/how-to/create-and-manage-websites/ Matomo’s website]). Then, follow these steps:
# Log in to the [https://apps.moodle.com Apps portal].
# Go to '''App customisation''' > '''Analytics''' > '''Matomo analytics'''.
# Check '''Track app activity'''.
# Add your '''Matomo URL''' - that's the URL of your Matomo instance, for example https://yoursite.matomo.cloud.
# Add the '''Website ID''' associated with your Moodle site in Matomo. To obtain this ID:
## Log in to your Matomo account.
## Go to '''Administration''' using the gear icon on the right side of the top navigation bar.
## On the left-hand panel, select '''Websites''' > '''Manage'''.
## In your list of measurables, find the Moodle site in which you want to track app activity. The '''ID''' of the measurable is the '''Website ID''' you need to enter in the apps portal.
# Click '''Save changes''' to establish the connection and start tracking app activity.
# If you'd like to stop tracking at any time, uncheck '''Track app activity''' and then save changes.

To filter Matomo data to isolate mobile app usage from Moodle site interactions, follow these steps:
[[File:Captura de pantalla 2023-11-14 a las 12.05.05.png|thumb|Moodle App Matomo referrer set-up]]
# Log in to your Matomo account.
# Click '''All visits''' at the top of the page
# Create a custom segment by applying this configuration: “Referrer URL” “is” “https://moodlemobile”
# To only see Moodle site interactions, do the following: “Referrer URL” “is not” “https://moodlemobile”

Please notice that the integration with Matomo does not work offline.

===Google Analytics for Firebase===
Only available when purchasing a [https://moodle.com/branded-app/ Branded Moodle App].

Google Analytics for Firebase is a free tool that provides valuable insights and data about how users interact with mobile apps.

Please notice that the integration with Google Analytics for Firebase does not work offline.

===Google Play and Apple App Store statistics===

If you have a custom mobile application, you can access statistics about app downloads and user engagement such as weekly active users and devices.

Google play:
# Go to Google Play console: https://play.google.com/console
# Select your app from the list.
# Navigate to specific tabs, such as "Statistics"

Apple App Store:
# Log in to App Store Connect: https://appstoreconnect.apple.com/
# Go to "App Analytics" from the dashboard.

==Web services token duration==
From Moodle 3.4 onwards, an admin can set how long a web services token created by a user (for example via the mobile app) is valid. (In previous versions of Moodle a token was valid for 3 months.)

The setting that dictates the previous 'User created token duration' (tokenduration) can be found under the Security section.
==App's cache==
The app caches WebService requests to decrease data usage and increase the app's speed. When the app needs to get some data from Moodle, it will use a cached request as long as it isn't expired.

This cache was improved in Moodle App 3.7.0, now there are several cache times depending on the WS being called. This means that some requests will expire more often than others. Also, if the user isn't using a WiFi connection, the expiration time will also be longer to decrease the data usage. These cache times cannot be configured using a Moodle setting.
==See also==
* [https://moodle.academy/course/view.php?id=100 Moodle App Configuration]- a free self-paced course for admins on Moodle Academy.
* [[Moodle Mobile FAQ]] for other administration-related mobile app questions.
* [[Moodle app security]]
* [https://docs.moodle.org/dev/Moodle%20Mobile%20debugging%20WS%20requests dev:Moodle Mobile debugging WS requests] - a guide to helping you find and report problems with the Moodle Mobile app on your site
* [https://docs.moodle.org/dev/%20Moodle%20Mobile%20Roadmap dev: Moodle Mobile Roadmap]
* [https://docs.moodle.org/dev/Moodle%20Mobile%20release%20notes dev:Moodle Mobile release notes]
* [https://docs.moodle.org/dev/Moodle%20Mobile Moodle Mobile developer docs]
* [[Moodle Mobile availability plugin]]
* [[Mobile web services]]
[https://docs.moodle.org/fr/ Guide mobile pour administrateurs]
[https://docs.moodle.org/es/Moodle app guía para administradores]
[https://docs.moodle.org/de/Moodle App - Anleitung für Administrator/innen]

Moodle app H5P support

2025-07-04T10:57:50Z

Jleyva: /* Working offline */

{{Mobile}}
==Support by version==
=== Before Moodle 3.8 ===
* H5P was supported via an activity plugin developed by the H5P Team (requires Moodle 3.5 onwards)
* It worked in the app, the H5P content was launched in a special frame embedded in the app. Did not support offline browsing
* Required certain site configuration changes (like enabling frame embedding)
=== Moodle 3.8 ===
* Initial core support added
* H5P content only available via embedding (text editor and filter)
* H5P content supported in the Moodle App 3.8
=== Moodle 3.9 ===
* New H5P activity plugin available in the core distribution
* New Content Bank for managing H5P content in the Moodle site
* H5P activities can be graded
* H5P activities supported in the Moodle App 3.9
== How H5P content is displayed? ==
=== Embedded ===
* The content “auto-plays” in the web version and in the app if the display option 'Auto-play in mobile app' (new in Moodle LMS and app 5.0) is checked. Otherwise, it has to be manually played in the app by the student.
** As a workaround for older Moodle LMS versions, you can add this HTML attribute in the main element used to embed the H5P file: data-mobileapp-autoplay="true"
* The app will automatically download the content for offline use (so it is available without connection)
** WiFi: Only if the package size is less than 20MB
** 3G/4G: Only if the package size is less than 2MB
* For larger packages, the student can always choose to download it manually (click top-right)
* If the student is downloading the full course, all the embedded H5P packages will be downloaded
* External H5P are not downloadable for offline use
[[File:h5p_embedded.png|600px]]

=== As part of the core H5P activity (Moodle 3.9 onwards) ===
* The content is automatically downloaded and “auto-plays” in the app if:
** WiFi: Only if the package size is less than 20MB
** 3G/4G: Only if the package size is less than 2MB
* For larger packages, we display a Play button so the student can launch it.
* The H5P is always downloaded (be careful with big H5P packages), it is required for activating tracking
* In the [[Moodle_app_guide_for_admins#Disabled_features|Moodle Site Administration settings]], downloading H5P packages can be disabled.
* Students can review their previous attempts in the app
[[File:h5p_activity.png|600px]]

== Working offline ==
* Offline support is only available in the core H5P activity module
* For the offline mode to work, the app needs to download the H5P zip package to the user's device. You can prevent H5P packages from being downloaded via Moodle settings ([[Moodle_app_guide_for_admins#Disabled_features|Moodle app features section]]), selecting the "View H5P offline" option. Please note that preventing the download of H5P packages will disable the offline support.
* Students can download a full course with H5P activities or a single H5P activity
* In both cases, if he is playing the package when it is not connected to the Internet, all the tracking information will be stored locally in the device
* Once the user is connected back to the Internet, all the tracking information will be sent to the server for the teacher to review
* If the H5P package has missing dependencies or errors, it might only work online and not offline

[[Category:H5P]]

[[es:Soporte H5P Moodle app]]

Moodle app offline features

2025-07-04T10:54:16Z

Jleyva: /* Other activities */

{{Mobile}}

== Introduction ==

We live in a hyper-connected 5G world and we think the Internet is everywhere, but we usually forget about:

* Underdeveloped and developing countries
* Rural areas in big countries
* Kids with restricted data plans
* Shared internet connection in schools/classrooms
* Aerial and maritime traffic

One of the most powerful features of the Moodle app is that it enables us to work offline.

Students can browse course contents offline and participate in activities, then once they are connected back to the Internet, the app will synchronise all the necessary information with their Moodle site.

== How does the app store data for offline use? ==

* While browsing the site and its contents, though note that external contents (e.g. YouTube videos) are not downloaded and embedded files (audio, video) are not always downloaded (it depends on the user connection and file size)
* When the user downloads content by the download icon
** The user can use the “cloud” icon to download specific content or a complete section or course
** The user gets alerted when downloading large files
** If a resource has been updated in the server, a refresh icon will be shown.

===Why doesn’t the app pre-fetch/cache more data?===
# Because the user may have a monthly data plan
# Because the device storage space may be limited
# Massive data download might impact on the server performance

===What does the app consider to be a large file?===
* If the user is connected to a Wi-Fi network: large file >= 20MB
*If the user is connected to a data network: large file >= 2MB

== Course features offline support ==

* All course resources can be downloaded for offline (except URL)
* All course activities are supported (except Chat and External tool)
* Additional (non-standard) plugins usually don’t work offline
* Some functionality for certain activity modules does not work offline, see below for more information.

=== Assessment ===

The offline mode is disabled by default in Quiz and Lesson, however, the teacher can decide if they want to enable it.
* A quiz may be attempted offline only if:
** There is no time limit set
** The question behavior is deferred feedback (with or without CBM) only
** New in '''Moodle 4.3.1''' - the Quiz uses sequential navigation.
** There is no network address requirement

For detailed information about Quiz and how it works offline please see [[Moodle Mobile quiz offline attempts]].

=== Other activities ===
* SCORM and H5P packages are downloaded to the user’s device by default, there are settings to control this behaviour in order to prevent the packages from being downloaded (check this support pages for more information, [[Moodle app SCORM player]] and [[Moodle app H5P support]]).
* Wiki editing is not supported offline
* Glossaries entries can’t be deleted/updated offline
* Text assignment submissions can’t be edited offline
* Activities configured with availability conditions cannot be/are not downloaded for offline (the user will have to reconnect to be able to see activities unlocked by conditions recently met)

== What other features work offline?==

Apart from resources and activities certain course and site functionality are also available offline.

The offline support for completion is only for marking courses or activities completed (when viewed).

Conditioned activities are not downloaded for offline.

* Participants
* Grades
* Completion
* Notes
* Messaging
* Notifications
* Calendar events
* Private files
* Badges
* Blogs
* Rating
* Comments

== Synchronisation ==

Synchronisation works differently depending on the device
* Android: The app must be opened but it can be in the background (you can be using a different app).
* iOS (iPhone, iPad): The app must be opened and in the foreground (it has to be the device active app).
* Desktop: The app must be opened but it can be in the background (minimised).

🔋The battery is the key factor, mobile OS limits its usage

There are two ways of synchronising data:

* Automatic
** Runs regularly, every 10 minutes
* Manual
** The user will see a message indicating there is data pending synchronisation

===What happens with the student activity after synchronisation?===
Actions performed offline are logged and stored into the system with the synchronisation time, not with the time when they happened.
We are exploring ways to improve reporting via Moodle’s xAPI support.

For more information about how synchronisation works see [[Moodle app synchronization]].

== Configuration options ==

Site administrators can decide if they want:
* Disable completely the offline mode
* Disable all courses downloading
* Disable individual courses downloading

For disabling the previous features, please see [[Moodle app guide for admins]].

Users can decide if they want to allow synchronisation only when connected to a Wi-Fi network or also when using a data network.

==Moodle App Plans ==

When using the Moodle App, site admins can choose to subscribe to a paid plan or use the free version.

Plans limit the download of complete courses in one click.

Students can still download individual contents or sections.

We recommend a Premium plan subscription: https://apps.moodle.com

== See also ==
* [[Moodle app SCORM player]]
* [[Moodle app H5P support]]
* [[Moodle Mobile quiz]]
* [[Moodle app synchronization]]

[[es:Características de Moodle app sin conexión]]

Moodle app SCORM player

2025-07-04T10:48:46Z

Jleyva: /* Features */

{{Mobile}}
==Features==
The Moodle app SCORM player enables the playing of SCORM 1.2 packages online and offline.

The Moodle app 5.0 allows remote and SCORM 2004 packages embedded in the site to be played on the app (only online).

When a user loses connectivity, offline mode is enabled automatically and all interactions that are tracked by the SCORM package are saved.

When a user is online again, the offline attempt is synchronised back to the Moodle site, either merging it with other incomplete attempts on the site or saving it as a new attempt.

Notice that in order to be able to play packages offline, the app will have to download the SCORM zip to the user's device. In order to prevent this behaviour, you can enable the global SCORM setting "Protect package downloads" (protectpackagedownloads). Enabling the previous setting will disable the offline mode for the SCORM activity.

== Requirements ==
The Moodle app SCORM player requires Moodle 3.0 onwards. In ''Site administration > Plugins > Activity Modules > SCORM Package'' the setting 'Protect package downloads' should be disabled (default setting).

The Moodle app SCORM player may be used on sites running Moodle 2.6 to Moodle 2.9 if the [[Moodle app additional features]] plugin is installed.

If the playing of SCORM packages offline is not desired, the setting 'Protect package downloads' may be enabled. If the Moodle app additional features plugin is being used, the setting can be found in ''Site administration > Plugins > Local plugins > Moodle Mobile additional features''.

The ZIP file containing the SCORM contents should not be Windows specific. If your SCORM package contains directories using the inverted path separator "\" they won't work in Android.
== Technical details ==
The Moodle app SCORM player provides support for:
* SCORM 1.2 packages
* SCORM 2004 (only online, embedded from the site). Moodle app version 5.0 onward
* Objectives, interactions and prerequisites
* SCO navigation via nav.event
* Uploaded packages, remote zip packages and zip packages in any type of repository supported by Moodle
The Moodle app SCORM player does not currently support:
* Remote imsmanifest.xml packages or file system repository unzipped SCORMS
* Opening of packages outside the app e.g. in a new browser window
* JavaScript pop-ups via window.open (Mobile device limitation)
==Tips for Moodle app friendly SCORM packages ==
* Try to reduce the size of the images and use mobile-compatible formats e.g. png
* Try to reduce the size of videos and use mobile-compatible formats e.g. mp4
* Avoid using Flash or FLV
* Avoid using images, files or media on remote sites
* Avoid using pop-ups
* Avoid using advanced HTML5 features, as they may not be supported by old devices
* Avoid having a left navigation menu as part of the SCORM package, as this reduces the space available for the package content
* If you want to display your SCORM package in semi full-screen mode (it will just remove the app bottom menu), you have to configure it in Moodle so it will open in "New window" via the SCORM module Appearance settings.
[[Category:SCORM]]
[[es:Reproductor SCORM Moodle Mobile]]
[[de:Moodle App - SCORM Player]]

== Known issues ==

'''Large videos stored within the package do not play in iOS devices when using Video.js:'''

This is caused by the following Video.js bug, see https://github.com/videojs/video.js/issues/7557

Moodle app H5P support

2025-07-01T09:09:14Z

Jleyva: /* Embedded */

{{Mobile}}
==Support by version==
=== Before Moodle 3.8 ===
* H5P was supported via an activity plugin developed by the H5P Team (requires Moodle 3.5 onwards)
* It worked in the app, the H5P content was launched in a special frame embedded in the app. Did not support offline browsing
* Required certain site configuration changes (like enabling frame embedding)
=== Moodle 3.8 ===
* Initial core support added
* H5P content only available via embedding (text editor and filter)
* H5P content supported in the Moodle App 3.8
=== Moodle 3.9 ===
* New H5P activity plugin available in the core distribution
* New Content Bank for managing H5P content in the Moodle site
* H5P activities can be graded
* H5P activities supported in the Moodle App 3.9
== How H5P content is displayed? ==
=== Embedded ===
* The content “auto-plays” in the web version and in the app if the display option 'Auto-play in mobile app' (new in Moodle LMS and app 5.0) is checked. Otherwise, it has to be manually played in the app by the student.
** As a workaround for older Moodle LMS versions, you can add this HTML attribute in the main element used to embed the H5P file: data-mobileapp-autoplay="true"
* The app will automatically download the content for offline use (so it is available without connection)
** WiFi: Only if the package size is less than 20MB
** 3G/4G: Only if the package size is less than 2MB
* For larger packages, the student can always choose to download it manually (click top-right)
* If the student is downloading the full course, all the embedded H5P packages will be downloaded
* External H5P are not downloadable for offline use
[[File:h5p_embedded.png|600px]]

=== As part of the core H5P activity (Moodle 3.9 onwards) ===
* The content is automatically downloaded and “auto-plays” in the app if:
** WiFi: Only if the package size is less than 20MB
** 3G/4G: Only if the package size is less than 2MB
* For larger packages, we display a Play button so the student can launch it.
* The H5P is always downloaded (be careful with big H5P packages), it is required for activating tracking
* In the [[Moodle_app_guide_for_admins#Disabled_features|Moodle Site Administration settings]], downloading H5P packages can be disabled.
* Students can review their previous attempts in the app
[[File:h5p_activity.png|600px]]

== Working offline ==
* Offline support is only available in the core H5P activity module
* Students can download a full course with H5P activities or single H5P activities
* In both cases, if he is playing the package when is not connected to the Internet all the tracking information will be stored locally in the device
* Once the user is connected back to the Internet, all the tracking information will be send to the server for the teacher to review
* H5P offline support can be disabled via Moodle settings ([[Moodle_app_guide_for_admins#Disabled_features|Moodle app features section]])
* If the H5P package has missing dependencies or errors it might only work online and not offline

[[Category:H5P]]

[[es:Soporte H5P Moodle app]]

File:Moodle features students.pdf

2025-06-30T14:55:56Z

Jleyva: Jleyva uploaded a new version of File:Moodle features students.pdf

Moodle app SCORM player

2025-06-30T14:47:13Z

Jleyva:

{{Mobile}}
==Features==
The Moodle app SCORM player enables the playing of SCORM 1.2 packages online and offline.

The Moodle app 5.0 allows remote and SCORM 2004 packages embedded in the site to be played on the app (only online).

When a user loses connectivity, offline mode is enabled automatically and all interactions that are tracked by the SCORM package are saved.

When a user is online again, the offline attempt is synchronised back to the Moodle site, either merging it with other incomplete attempts on the site or saving it as a new attempt.

== Requirements ==
The Moodle app SCORM player requires Moodle 3.0 onwards. In ''Site administration > Plugins > Activity Modules > SCORM Package'' the setting 'Protect package downloads' should be disabled (default setting).

The Moodle app SCORM player may be used on sites running Moodle 2.6 to Moodle 2.9 if the [[Moodle app additional features]] plugin is installed.

If the playing of SCORM packages offline is not desired, the setting 'Protect package downloads' may be enabled. If the Moodle app additional features plugin is being used, the setting can be found in ''Site administration > Plugins > Local plugins > Moodle Mobile additional features''.

The ZIP file containing the SCORM contents should not be Windows specific. If your SCORM package contains directories using the inverted path separator "\" they won't work in Android.
== Technical details ==
The Moodle app SCORM player provides support for:
* SCORM 1.2 packages
* SCORM 2004 (only online, embedded from the site). Moodle app version 5.0 onward
* Objectives, interactions and prerequisites
* SCO navigation via nav.event
* Uploaded packages, remote zip packages and zip packages in any type of repository supported by Moodle
The Moodle app SCORM player does not currently support:
* Remote imsmanifest.xml packages or file system repository unzipped SCORMS
* Opening of packages outside the app e.g. in a new browser window
* JavaScript pop-ups via window.open (Mobile device limitation)
==Tips for Moodle app friendly SCORM packages ==
* Try to reduce the size of the images and use mobile-compatible formats e.g. png
* Try to reduce the size of videos and use mobile-compatible formats e.g. mp4
* Avoid using Flash or FLV
* Avoid using images, files or media on remote sites
* Avoid using pop-ups
* Avoid using advanced HTML5 features, as they may not be supported by old devices
* Avoid having a left navigation menu as part of the SCORM package, as this reduces the space available for the package content
* If you want to display your SCORM package in semi full-screen mode (it will just remove the app bottom menu), you have to configure it in Moodle so it will open in "New window" via the SCORM module Appearance settings.
[[Category:SCORM]]
[[es:Reproductor SCORM Moodle Mobile]]
[[de:Moodle App - SCORM Player]]

== Known issues ==

'''Large videos stored within the package do not play in iOS devices when using Video.js:'''

This is caused by the following Video.js bug, see https://github.com/videojs/video.js/issues/7557

Moodle app H5P support

2025-06-30T14:43:39Z

Jleyva: /* Working offline */

{{Mobile}}
==Support by version==
=== Before Moodle 3.8 ===
* H5P was supported via an activity plugin developed by the H5P Team (requires Moodle 3.5 onwards)
* It worked in the app, the H5P content was launched in a special frame embedded in the app. Did not support offline browsing
* Required certain site configuration changes (like enabling frame embedding)
=== Moodle 3.8 ===
* Initial core support added
* H5P content only available via embedding (text editor and filter)
* H5P content supported in the Moodle App 3.8
=== Moodle 3.9 ===
* New H5P activity plugin available in the core distribution
* New Content Bank for managing H5P content in the Moodle site
* H5P activities can be graded
* H5P activities supported in the Moodle App 3.9
== How H5P content is displayed? ==
=== Embedded ===
* The content “auto-plays” in the web version and in the app if the display option 'Auto-play in mobile app' (new in 5.0) is checked. Otherwise it has to be manually played in the app by the student,
* The app will automatically download the content for offline (so it is available without connection)
** WiFi: Only if the package size is less than 20MB
** 3G/4G: Only if the package size is less than 2MB
* For larger packages, the student can always choose to download it manually (click top-right)
* If the student is downloading the full course, all the embedded H5P packaged will be downloaded
* External H5P are not downloadable for offline
[[File:h5p_embedded.png|600px]]
=== As part of the core H5P activity (Moodle 3.9 onwards) ===
* The content is automatically downloaded and “auto-plays” in the app if:
** WiFi: Only if the package size is less than 20MB
** 3G/4G: Only if the package size is less than 2MB
* For larger packages, we display a Play button so the student can launch it.
* The H5P is always downloaded (be careful with big H5P packages), it is required for activating tracking
* In the [[Moodle_app_guide_for_admins#Disabled_features|Moodle Site Administration settings]], downloading H5P packages can be disabled.
* Students can review their previous attempts in the app
[[File:h5p_activity.png|600px]]

== Working offline ==
* Offline support is only available in the core H5P activity module
* Students can download a full course with H5P activities or single H5P activities
* In both cases, if he is playing the package when is not connected to the Internet all the tracking information will be stored locally in the device
* Once the user is connected back to the Internet, all the tracking information will be send to the server for the teacher to review
* H5P offline support can be disabled via Moodle settings ([[Moodle_app_guide_for_admins#Disabled_features|Moodle app features section]])
* If the H5P package has missing dependencies or errors it might only work online and not offline

[[Category:H5P]]

[[es:Soporte H5P Moodle app]]

Creating mobile-friendly courses

2025-06-20T06:18:59Z

Jleyva: /* Course content */

Moodle app FAQ

2025-05-16T08:16:45Z

Jleyva: /* The Moodle app might seem slow (especially on Android devices) */

{{Mobile}}
==Students==
===How can I log in?===
To log in to your Moodle site with the Moodle App, you need the URL (web address) of the Moodle site that you’re trying to access. If your organisation has Search enabled, you can try searching by the name of your organisation or eLearning site.

If your organisation allows you to log in via QR code, you’ll find the QR code at the bottom of your user profile on your Moodle site. You just need to press “Scan QR code” on the app, scan the QR code on your profile and you’ll be logged in automatically.

If your organisation allows you to log in using face recognition or fingerprint, you can activate this in the App, going to User account > Preferences. You’ll need to have biometric authentication enabled in your own device’s settings.
===Who can I contact for help with the app?===
If you’re a student and need help with issues related to logging in, registering to a Moodle site or trouble connecting to the app, you should contact your school or learning organisation. For example, one of your teachers, or the person who takes care of Moodle.
Moodle HQ make the Moodle software and the Moodle app, but they don’t manage nor have access to your Moodle site or your user data.
===How can I get the Moodle app?===
You can download the Moodle App for free from [https://play.google.com/store/apps/details?id=com.moodle.moodlemobile Google Play] and the Apple [https://itunes.apple.com/app/moodle-mobile/id633359593?mt=8 App Store]. You will find it by searching “Moodle”, and the author/owner is “Moodle Pty Ltd”.
If you are unable to download the app from Google play, please visit [https://download.moodle.org/mobile/ Moodle app downloads]
===I can't get the app to work. ===
To ensure that the Moodle app functions properly, please double-check that you have correctly entered the URL address of the Moodle site you are using (please visit [https://docs.moodle.org/en/Moodle_app_FAQ#I_can%E2%80%99t_find_my_Moodle_site_in_the_app. I can’t find my Moodle site in the app]). If you are experiencing difficulties connecting to your site, please contact the person or team who takes care of Moodle in your school or learning organisation. Please note the app only works with Moodle sites that have been set up to allow it, and that are running on at least Moodle 3.5.

===I can’t find my Moodle site in the app. ===
To find your Moodle site on the app login screen, try searching for the name of your school or learning organisation.

If your school or organisation doesn’t appear in the search, you can try searching by your Moodle site URL address instead. If you don’t know the address of your Moodle site, here’s how you can find it:
# Open a web browser (like Chrome or Safari) and go to your school’s Moodle site login page.
# At the top of the page in the address bar, you'll see the URL address of your Moodle site, e.g. “campus.example.edu”. [[File:FAQ I cant find my site 1.png|alt=URL|thumb|none|''campus.example.edu'']]
# Copy the URL (don’t copy the /login nor what comes after), paste it into Your site in the app, then select Connect to your site. [[File:FAQ I cant find my site 2.png|alt=Adding an URL to the app|thumb|none|Adding an URL to the app]]
# Now you can log in to your site with your username and password.

If you tried searching by URL address and still can’t find your Moodle site, please get in touch with the person who takes care of Moodle in your school or learning organisation.
===I can’t log in with the app===
To log in to your Moodle site using the app, you first need to connect to your school’s Moodle site (view [[I can’t find my Moodle site in the app]] if you can’t find your site).

Once you’ve connected to your Moodle site, you should be able to log in with your usual username and password.

If you forgot your username or password, select the option '''Forgotten your username or password?'''. If you still have trouble logging in or can’t see any options for retrieving your username or password, please get in touch with the person who takes care of Moodle in your school or learning organisation.
===I see an error message when I try to use the app===
If you see an error message that prevents you from using the app, please get in touch with the person who takes care of Moodle in your school or learning organisation.

Some of the most common errors that your school or learning organisation will be able to fix are:
* Your token is expired or not valid.
* An error mentioning the parameter “includestealthmodules”.
* The web service function is not available.
* A message about site maintenance.

If you’re experiencing any of these errors, contact your school or learning organisation for help.
===What permissions does the app require?===
The app requires the following permissions:
* Record audio - for uploading to your Moodle site
* Read and modify the contents of your SD card - for content to be downloaded to your SD Card for offline access.
* Network access - to be able to connect with your Moodle site and check if you are connected, and if not to switch to offline mode.
* Run at startup - to receive local notifications even when the app is running in the background.
* Prevent phone from sleeping - to receive push notifications anytime.
===What are the minimum device requirements to use the Moodle app?===
Android devices: Require Android 7.0 or later. (Users with Android 5 and 6 can still use version 4.3, but they will not receive any new updates.)

iOS devices (iPhones/iPads): Require iOS 13 or later. (Please note the app was only tested on versions iOS 14 and onward.)

===I can't see my course on the app. What do I do?===
Check with your course tutor that you are correctly enrolled.
=== Why can't I upload my assignment on the app?===
If you’re experiencing any issue uploading assignment, please contact your school or learning organisation for help.
===Why can't I sometimes access the app or submit anything to it?===
This could be because of interruptions in your internet connection. Wait a while and try again. If you continue to have problems, contact your school or learning organisation for help.
===Is there a space limit on my files?===
Assignments will have a size limit which you can see, those are set by your teachers. For other space limit questions, check with your your school or learning organisation .
===When are activities completed offline synchronized?===
See [[Moodle app synchronization]].
===Why the site is asking for my username and password when an activity is opened in the browser?===
For security reasons, between auto-logins you must wait 6 minutes (this should not be a problem because most of the browsers will keep your Moodle session open).
In recent Moodle versions, the previous value can be configured in Site Administration > Mobile app authentication > Minimum time between auto-login requests

=== The Moodle app might seem slow (especially on Android devices) ===
If the app feels slow, it might be due to things outside the app itself. This can include:
* Slow internet connection
* Network problems
* The server responding slowly
* Content or settings not made for mobile
* Using the app on an old or slow device

We test the app carefully on many sites before each release, and we’re confident it usually works as well as or better than the website.

To make sure your site works well on mobile, please check [[Creating mobile-friendly courses]]

Finally, to troubleshoot this problem, we recommend trying the application with our demo site: https://school.moodledemo.net. Simply use the username "student" and the relevant password to access the site. If you find that the navigation and overall experience with the app are improved, then the issue may be at the server level. In this case, we suggest contacting your school or learning organisation for further assistance.

=== The Moodle app restarts/ closes / reopenes itself ===
This is likely because there are too many apps opened on your mobile device. Mobile devices have a finite amount of memory, and the device's memory manager is responsible for determining which applications to keep open and which to close.
To optimise your device's performance, we recommend closing all applications that are not currently in use. This will free up valuable memory and ensure that your device runs smoothly.
===I use LineageOS and I'm having problems using the app===
LineageOS uses a different WebView implementation not compatible vith the app. You need to install "Android System WebView" from Google Play (or via a trusted apk) and enabling it via Settings > Developer options > WebView implementation.
===H5P packages and external content embedded via iframes are not working on iOS ===
This is caused by a new feature of iOS 14 called ITP that blocks cookies for external sites embedded in the app (the H5P content is played embedded in an iframe pointing to the Moodle website) unless the user enables a setting in the app to allow those cookies.

The quick workaround is to enable the setting "Allow Cross-Website Tracking" available via the Settings app (look for the Moodle app, at the bottom) on your iPhone/iPad with iOS 14.
===I cannot reproduce audio that was recorded on browser on iOS devices (iPhones and iPads)===
This behaviour is related to this Moodle LMS bug: https://tracker.moodle.org/browse/MDL-80114

=== I don't receive calendar notifications (reminders) when using Android 12 or above ===

In order to receive calendar notifications you need to allow alarms and reminders for the Moodle app. To do this:
* Open Android Settings and go to the Moodle app settings. Another way to reach these settings is by long-clicking the Moodle app icon and pressing "App info".
* Make sure that Notifications are enabled.
* If you see a section called "Alarms & reminders", make sure it is Allowed (this setting is disabled by default in Android 14+).

==Teachers==
===How can I enable videos in my course to be downloaded?===
See the section 'Media download for offline usage' in [[Creating Moodle-app-friendly courses]].
===Which course format is it best to use?===
Topics or weekly course format is best suited to mobile devices.
===How do I make YouTube links open automatically in the app?===
Add YouTube links as a [[URL resource]].
===Why can't my students see their courses?===
If you or an administrator have correctly enrolled them in a course, they can see it in their mobile app. If they are correctly enrolled but can still not see their course, ask them to check with your Moodle site administrator.
=== I can't mark assignments in the app===
If you are experiencing problems when grading, please review that you are using the correct decimal separators (if the app interface is in English, you must use a period).
===What communications tools can I use in the app to engage with my learners?===
See [[Mobile app notifications]]. Chat, forums and messaging are all supported by the app.
===My Vimeo videos are not playing in the app===
In older versions of Moodle (pre-Moodle 3.7), it may be necessary to activate the "Allow frame embedding" admin setting. However, for those using Moodle version 3.7 or later, it is important to check whether a Proxy/Firewall/Web Server security module is setting the X-Frame-Options header in your HTTP request responses. If this is the case, it is recommended to deactivate this feature as it may cause conflicts, as Moodle already sets this header by default.

This setting is typically found in any of these configuration files .htaccess, httpd.conf or VirtualHost. To disable it, you can just use: Header always unset X-Frame-Options

You may also use Bootstrap responsive classes: https://getbootstrap.com/docs/4.0/utilities/embed/, for example, <div class="embed-responsive">
For older versions, see this forum discussion with a workaround: https://moodle.org/mod/forum/discuss.php?d=327342

If the issue is with vimeo videos on Moodle sites 3.10 or 3.11, please update the Moodle site to the latest version possible (at least 3.10.10 or 3.11.6). (See https://tracker.moodle.org/browse/MDL-74042)
===ReCaptcha doesn't work on my site===
In older versions of Moodle (pre-Moodle 3.7), it may be necessary to activate the "Allow frame embedding" admin setting. However, for those using Moodle version 3.7 or later, it is important to check whether a Proxy/Firewall/Web Server security module is setting the X-Frame-Options header in your HTTP request responses. If this is the case, it is recommended to deactivate this feature as it may cause conflicts, as Moodle already sets this header by default.
===H5P packages don't work on my site===
In older versions of Moodle (pre-Moodle 3.7), it may be necessary to activate the "Allow frame embedding" admin setting. However, for those using Moodle version 3.7 or later, it is important to check whether a Proxy/Firewall/Web Server security module is setting the X-Frame-Options header in your HTTP request responses. If this is the case, it is recommended to deactivate this feature as it may cause conflicts, as Moodle already sets this header by default.

This setting is typically found in any of these configuration files .htaccess, httpd.conf or VirtualHost. To disable it, you can just use: Header always unset X-Frame-Options

This can also happen when you are using the non-official H5P plugin (mod_hvp), in that case you will see the following message: This site is not configured properly for displaying mobile H5P content. Please contact a site administrator so they can apply the above suggested configuration changes.

'''Cookies issues'''

If your site uses HTTPS please ensure that the "Secure cookies only" (cookiesecure) setting under Site administration > HTTP security is enabled.

'''Dependency errors'''

When the following error appears "Missing dependency H5P.Editor. something X required by H5P.Editor. something Y". H5P packages need to include all the libraries (dependencies) they use so the package is self-contained. But sometimes packages might be missing at least one dependency.

In order to fix this, you could do the following:

Open Moodle’s Content Bank (from the link in the problematic H5P settings page) and upload your H5P package there, once uploaded, you will see the H5P package and an “Edit” button, click on that button so the editor opens, scroll down and click “Save”.
Now, you can replace the problematic H5P with this new one, for this, you can just include it from the Content bank by opening the activity settings page and the file picker.
=== I use a Moodle plugin but the app says it is not supported ===
You should contact the plugin developer and point him to this documentation: https://docs.moodle.org/dev/Moodle_Mobile_Remote_addons where it is explained how to add support to plugins in the Mobile app.

There is a list of Moodle plugins supported by the app here: https://moodle.org/plugins/browse.php?list=award&id=6
=== I have problems playing SCORM packages ===
This might be caused because:
* The SCORM was added using an advanced option (remote imsmanifest.xml packages or file system repository unzipped SCORMS)
* The SCORM ZIP file was created using a tool that does not create standardised ZIP files (for example, zip files containing the inverted path separator "\" will not work on Android)
Please refer to [[Moodle app SCORM player]] for additional information.
=== My quizzes or lessons are not working offline ===
You need to edit the quiz or lesson activity settings and enable the "Allow lesson/quiz to be attempted offline using the mobile app" configuration option.
=== Maths notation is not displaying correctly in the app ===
If you are having issues with MathJax, please enable the [[TeX notation filter]] also.

If you have both filters enabled, please leave MathJax above TeX so it is always processed before TeX.

If the issue persists, we suggest disabling the 'Remove HTML tags from all activity names' (''formatstringstriptags'') option in ''Site Administration'' > ''Appearance'' > ''HTML settings''.

=== How can I disable text selection / copy in the app? ===
You can create a remote theme and add some custom CSS rules to disable it, see https://docs.moodle.org/dev/Moodle_Mobile_Themes
=== My images, videos or audios stop working after the first time ===
Please make sure the URL you're using on the media file doesn't have any redirect (e.g. http to https), always try to use the final URL. There's a bug in the library we use to download those files, it doesn't work when downloading files with redirects. We have plans to remove that library from the app, but since then please always try to use URLs without redirects.

==Administrators==
=== What plans are available for the Moodle app? ===
There are three main plans available for the Moodle app: Free, Pro, and Premium, each offering different features and benefits. In addition to the three main plans, there is also a Branded Moodle App (BMA) option. The BMA is a custom-built app that is branded to your organization. Learn more in [[Moodle app plans]].
=== How can I have my site listed in the Moodle app site finder? ===
Please refer to our [[Moodle app guide for admins]] for instructions.
=== How can I debug errors in the app? ===
Go to the More tab and then to Settings > General. Enable "Display debug messages". This will show an explanatory message when an error occurs, alternatively, you can do a full debugging via: https://docs.moodle.org/dev/Moodle_Mobile_debugging_WS_requests

=== How can I disable features in the app? ===
Please go to ''Site administration > Mobile features > Disabled features'' and select all the features you want to disable.

To select multiple features you will have to use Ctrl (Cmd in Mac) + Click

=== How can I add custom menu items in the app? ===
You can add custom additional menu items in the "more" menu of the app, the one represented by three consecutive dots.

Please go to ''Site administration > Mobile features > Custom menu items'' and follow the instructions in [[Moodle_app_guide_for_admins#Custom_menu_items|Moodle app guide for admins]] for the correct format to use.

As a quick example:
Academy information|https://yoursite.com/mod/page/view.php?id=X |app|en|home

=== How can I customise the language strings in the app? ===

Please go to ''Site administration > Mobile features > Custom language strings'' and follow the instructions in [[Moodle_app_guide_for_admins#Custom_language_strings|Moodle app guide for admins]] for the format to use.

As a quick example:
core.user.student|Learner|en
core.user.student|Aprendiz|es

=== I can connect with my iPhone (or iPad) but not with my Android phone ===
This usually happens when the site is using https and the certificate is not correctly configured or it is using an old protocol, please use these pages to check this certificate: https://www.sslshopper.com/ssl-checker.html, https://www.geocerts.com/ssl_checker, and https://www.ssllabs.com/ssltest/analyze.html

'''The certificate of this site cannot be trusted by your device: TLS connection could not be established: javax.net.ssl.SSLHandshakeException'''

This error could be caused because in any of the certification paths there is a certificate using SHA-1. Starting Android 10 this is not allowed, more information here: https://developer.android.com/privacy-and-security/security-ssl

You could easily check the previous using https://www.ssllabs.com/ssltest/analyze.html and going to the Certification Paths -> Android section, if there is any mention to SHA-1 this could be the cause. You will need to upgrade your certificates to avoid using SHA-1.

=== My certificate is fine but I still can't connect ===
This is usually a server configuration problem caused by any of the following server configuration issues:

'''"Access to XMLHttpRequest at 'https://yoursite/webservice/rest/server.php?moodlewsrestformat=json<nowiki/>...' from origin '<nowiki>http://localhost'</nowiki> has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.'''

This is because a Proxy/Firewall/Web Server security module is removing automatically the Access-Control-Allow-Origin: * header that Moodle sets to allow Web Service requests.

It is totally secure to remove that Proxy/Firewall/Web Server rule/configuration because that header is only set by Moodle when needed.

'''"access-control-allow-origin cannot contain more than one origin".'''

iOS and Android apps do not allow the following header to contain more than one item: "Access-Control-Allow-Origin". For example, a header like this: Access-Control-Allow-Origin: *, https://mydomain.com will cause problems.

This HTTP header is not valid, according to the specification you can only specify a domain or a "*":
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin

Please, review if you have a Proxy/Firewall/Web Server adding automatically values to that HTTP header.

'''Security rules are blocking requests using the Accept-Charset header'''

Some security rules, such as OWASP ModSecurity, are blocking requests with this header that is sent by the Moodle App. In future releases of the app, this problem will be fixed. But in the meantime, you should disable it. Find more about this in MOBILE-4342.
=== My certificate is fine but the Moodle app is detecting http instead of https ===
If the Moodle app is detecting http instead of https, please revise config.php (check "wwwroot" as well as "httpswwwroot")
===After updating Moodle LMS to a recent version my users cannot login===
This only applies to sites that are configured to use log in via an embedded browser pointing to their Moodle site.
This behaviour could be related to this Moodle LMS issue: https://tracker.moodle.org/browse/MDL-81897.
There are several ways to fix this issue:
# Upgrade their Moodle site to any of the indicated version in the issue that will solve the problem
# Manually apply the patch here: https://github.com/jleyva/moodle/compare/462d5f04a8...MDL-81897-master
# Immediate workaround: Change the app authentication so it will launch in a separate browser, by going to Site admin > Mobile app authentication > Type of login (and select the option that mentions external/system browser), remember to Save Changes
We’d recommend doing 3) that will immediately address the issue that is affecting new logins.
===I can't get the app to work. What can I do?===
Assuming you have enabled mobile services on your site, please check:
# If your site uses an SSL certificate, it must be a trusted certificate, not self-signed. Please use these tools or a similar one to check that your certificate is valid: [https://www.sslshopper.com/ssl-checker.html SSL Checker], [https://www.geocerts.com/ssl_checker SSL Checker], and [https://www.ssllabs.com/ssltest/analyze.html SSL Server Test]. All the checks must be ok, including the "Certificate Chain Complete". Otherwise the app might work on iOS but not on Android.
# Make sure that the "Access-Control-Allow-Origin" header only contains one item. For example, a header like this: Access-Control-Allow-Origin: *, <nowiki>https://mydomain.com</nowiki> will cause problems.
# [[Debugging]] is disabled (in ''Site administration > Development > Debugging'')
# The ADOdb debug option is disabled if you are using the external database auth or enrolment plugin (in ''Plugins > Authentication > External database'' and in ''Plugins > Enrolment > External database'').
# SHA-1 https certificates are not supported anymore in Chrome, this means that the Android version of the app won't work for your site. If your site doesn't work in desktop Chrome or Chromium it won't work in the Android app. See https://blog.chromium.org/2014/09/gradually-sunsetting-sha-1.html for more information
# If you are using IIS check that Anonymous access is not disabled for the /webservice directory.
# If you are using a web application firewall like AWS WAF, StackPath, Barracuda, Cloudflare, Juniper, etc... try to temporary disable it to check if that's the cause. If so, you'll have to whitelist these endpoints: login/token.php, webservice/*, lib/ajax/*, media/player/vimeo/wsplayer.php and /tokenpluginfile.php
You can also add WAF rules to allow traffic by detecting the app user agent such as: (http.user_agent contains "MoodleMobile")
If you still have a problem, please post in the [https://moodle.org/mod/forum/view.php?id=7798 Moodle for mobile forum].

If the issue started after updating Moodle LMS please visit [[After updating Moodle LMS to a recent version my users cannot login]].

=== I cannot access with old users, but I can with recently created ones! ===
Please, do a "Purge all caches" via the Moodle administration settings, this will solve the problem.
===I can't view the courses tab as an administrator===
The Moodle app only displays courses you are enrolled in. If you want to view a course as an admin, you need to enrol in it.
===My Moodle site uses a SSO auth method (Shibboleth, CAS, Google OAuth, etc) and the app is not working===
See the section 'Mobile authentication' in the [[Moodle app guide for admins]] for details of how to configure it.

If configured the app is still not connecting: If your site uses an SSL certificate, it must be a trusted certificate, not self-signed. Please use this tool or a similar one to check that your certificate is fine: [https://www.geocerts.com/ssl_checker SSL Checker]. All the checks must be OK, including the "Certificate Chain Complete".

If your SSO method is unable to authenticate when using an "embedded browser" (it gives an authentication error), please check if it works with a "browser window". If it does work with the browser window then it means your SSO is performing an HTTP redirect, and these kind of redirects aren't supported by the app (the request is redirected by the browser not passing the POST parameters). Unfortunately, this is something we cannot control in the Mobile app (it can't be handled via JavaScript). For further information, see http://stackoverflow.com/questions/228225/prevent-redirection-of-xmlhttprequest and http://stackoverflow.com/questions/4168784/ajax-redirection-handling

There are only 2 possible solutions: set the authentication via a "browser window" instead of an embedded one (please notice this won't work in the Linux desktop app), or remove the redirect from the SSO auth method.
===SSO is not working with my custom auth plugin===
SSO should work in any plugin if the plugin handles correctly the $SESSION->wantsurl, this is the way SSO works when it is launched via the app:
* It launchs this URL https://yourmoodle/admin/tool/mobile/launch.php?service=local_mobile&passport=abc in the device browser
* If the user is not logged in, the browser will redirect the user to the login page
* If the auth plugin used implements correctly the handling of the wantsurl session var, once the user has logged in, the browser should redirect back to the https://yourmoodle/admin/tool/mobile/launch.php?service=local_mobile&passport=abc URL that will launch the mobile app via the custom URL protocol
Custom auth plugins may be failing in the last step,not redirecting back to tool/mobile, this will happen only if the plugin does not support correctly the $SESSION->wantsurl.

The SAML plugin works correctly but some modifications of that plugin may not work if important lines are changed.
===I am having problems requesting an airnotifier access key===
If you have registered your site but are still unable to request an access key, please register your site on the Moodle Apps Portal https://apps.moodle.com once your site is registered there, an Airnotifier access key will be automatically generated for you.
=== Push notifications are not working ===
Please check [[Mobile app notifications#Troubleshooting]]
=== How notifications icon badges are updated ===
'''Android''': Not all Android devices support icon badges so in some cases badges will never display numbers, also, depending on the device only a badge indicating that there are new notifications will be displayed when receiving a Push notification when the app is not in the foreground.

'''iOS''': The icon badge counter is only updated when the app is open and it will reflect the number of notifications pending reading or the number of message senders that sent you a message you have not read yet

In general, for iOS the icon badge displayed number should match the one displayed at the bottom of the app (or it should be the sum of the notifications and messages badges) and is not an indicator of the number of Push notifications the user has received, it acts as a reminder of pending notifications to be read that only gets updated when the user open the apps

There is an open issue to improve the behaviour on iOS, please watch MDL-73707
=== I configured 'QR code access' to automatic login, but the app still asks for credentials ===
Automatic authentication only works for Pro and Premium sites. You can see the app plans [https://moodle.com/app/ in this site].

If you're getting an error saying that the device you're using to connect isn't in the same network as the device that displays the QR code but both devices are connected to the same network, please check the section: [[#ipmismatch:_.27Client_IP_address_mismatch.27|ipmissmatch: 'Client IP address mismatch']].

=== I can log in on my Moodle site but I see a blank page or the app styles broken ===
This is usually because your Moodle site has a customised CSS.

Please try leaving empty CSS (''mobilecssurl'') on Site administration > Mobile app > Mobile appearance. If that works, please read [https://docs.moodle.org/dev/Moodle_App_Remote_Themes Moodle App Remote Themes] and create a new CSS file using the variables mentioned there

===The Moodle app does not connect to MoodleBox (or other internal self-hosted systems)===
You will need to disable SSL to make the app works, please see this forum discussion for more information: https://moodle.org/mod/forum/discuss.php?d=424353#p1739474
===I think I found a bug with the app. Where can I report it?===
# Log in to the [https://tracker.moodle.org/browse/MOBILE Moodle Mobile tracker] (you'll need to [http://tracker.moodle.org/secure/Signup%21default.jspa create a tracker account] if you've not done so previously)
# Check whether the issue has already been reported by doing a [https://tracker.moodle.org/issues/?jql=project%20%3D%20MOBILE search]
# If not, report the bug by clicking the 'Create Issue' link at the top right of the page, selecting 'Moodle app' as the project
# Add a detailed description providing as much information as possible (Moodle version, app version, device model and operating system, etc...), then click the Create button
===How can I get the app in my language?===
[[File:setting the app lang.png|thumb|100px|Setting your language]]
The Moodle app automatically detects your mobile's language and displays in the same language (if the translation exists). Otherwise, you can set the app language in App settings > General.

See also a post explaining how multi-lang works in the Moodle app: [https://moodle.org/mod/forum/discuss.php?d=453445#p1825637 Re: Language selector missing in Moodle app]

If the Moodle app is not yet available in your language, please contribute a translation! See [https://docs.moodle.org/dev/Translating%20Moodle%20Mobile Translating Moodle Mobile] for details of what to do.

=== Changes made to a Moodle site URL can cause logged-in users’ data to fail when synchronising. ===
We recommend that administrators manually log out all users after a site rename. If your site URL changes and have site users that are using the mobile Moodle App we suggest the following:
* For users that have not yet logged in - we recommend sending them the new URL
* For users already using the mobile Moodle App and potentially logged in request them to:
** log out of the mobile Moodle App,
** delete the old site, and
** log in using the new URL
Logged in Moodle users can continue working with the previous URL (with cached information) but they will not be able to synchronise the new information (therefore not receiving new information from their teachers, and teachers not receiving data or submissions from those students).
* To avoid the risk of data not synchronising, we recommend the site administrator logs out all app users, by manually deleting their tokens:
** Go to Site administration
** Click Server
** Click Web services
** Click Manage tokens
** Delete the tokens
Take into account that you still need to request your users to log in using the new URL.

=== Embedded content is not working ===

This could be caused because your site is using a Content-Security-Policy that is preventing the app from embedding content.

You can easily detect this when an error like this is displayed (javascript console): Refused to load URL because it does not appear in the frame-ancestors directive of the Content Security Policy.

If that's the case, you'd need to add the following elements: http://localhost moodleappfs://localhost at the end of the "Content-Security-Policy" HTTP header:

An example of a CSP allowing embedding Vimeo videos in the site and content in the app:
Content-Security-Policy: frame-ancestors 'self' https://*.vimeocdn.com https://*.vimeows.com https://*.vimeo.com http://localhost moodleappfs://localhost ;

Other type of embedded content that does not work is content hosted by Microsoft tools that require session or any type of authentication, such as SharePoint content.

=== Some activities are displayed incorrectly (blank, just a vertical line, ..) on the app ===
Please visit the forum post [[https://moodle.org/mod/forum/discuss.php?d=461909#p1854918| Some lesson activities do not display at all]].

==Error messages==
=== 'Coding error: version.php file is missing for the component' ===
This error message indicates that that plugin is not correctly installed (or uninstalled) on the Moodle site you use (see [[Installing plugins]]). Please review the mod/certificate folder to check if the version.php file is missing (or has incorrect permissions) as well as purge cache too.
=== 'Can not find data record in database table external_functions' ===
This error usually happens due to a bad configuration or setting value in your Moodle site, please check:
# The user quota global setting should be an integer. For more details, see the discussion [https://moodle.org/mod/forum/discuss.php?d=320873 How to enable Moodle Mobile App for all accounts].
# The ''usermaxuploadfilesize'' should be an integer, please try to decrease the size. It can be configured in ''Site Administration > Security > Site Policies > Maximum uploaded file size''. The default value (Site upload limit) depends on the PHP configuration, you might have to change the value of ''upload_max_filesize'' and ''post_max_size'' in your ''php.ini'' file.
# The user "lang" field in the database is set to a correct value and existing language installed in the site. Some times the lang field is set via external systems to incorrect values or pointing to a language pack that was uninstalled. Please, note that to fix this you need direct access to the database and your 'user' and 'course' table.
==='Cannot connect: Verify that you have typed correctly the URL and that your site uses Moodle 3.5 or later'===
Take into account that the app will only connect to Moodle LMS sites version 3.5 onward.
Please also check:
# Mobile services are enabled for the site.
# The user is entering the correct URL for the site (see FAQ above)
# For https sites, the certificate is valid (see FAQ above)
==='Invalid Moodle site version. The Moodle app only supports Moodle systems 3.5 onwards'===
The app will only connect to Moodle LMS sites version 3.5 onward (see [https://docs.moodle.org/35/en/Upgrading Upgrade to 3.5] as well as [[Upgrade overview]]).
==='We lost connection; you need to reconnect. Your token is now invalid.' on my custom version of the Moodle app ===
Please check:
# You have followed all the steps listed in [https://docs.moodle.org/dev/Moodle%20Mobile%20Developing%20a%20plugin%20tutorial Moodle Mobile Developing a plugin tutorial]
# You have enabled the [[Capabilities/moodle/webservice:createtoken|moodle/webservice:createtoken]] for the authenticated user
==='No permission to create web service token for the service local_mobile' when attempting to log in (any user that it is not an admin)===
Please check you have enabled the moodle/webservice:createtoken for the authenticated user or any global role you want to allow to use the mobile app
==='No permission to create web service token for the service local_mobile' when attempting to log in as an admin===
You need to create a token for the admin account (only) as follows:
# Go to ''Site administration > Plugins > Web services > Manage tokens''
# Click Add
# Enter the admin username and select 'Moodle app additional features service' (i.e. do NOT leave it as 'Moodle app web service')
# Click the 'Save changes' button.
==='Invalid response value detected' when accessing the site ===
The user quota global setting should be an integer. For more details, see the discussion [https://moodle.org/mod/forum/discuss.php?d=320873 How to enable Moodle Mobile App for all accounts].
=== ' Invalid response value detected: Invalid external api response: the value is "", the server was expecting "raw" type" ===
This usually happens when there is a field with value NULL in a table in the database that should not be there. This may happen if your Moodle has been upgraded over many years and the database schema is broken.

To fix it, you can do the following:
* Detect the field that is causing the problem (it should be indicated before the error message)
* Fix the field, for example, for the password field in the lesson table: UPDATE mdl_lesson SET password = '' WHERE password IS NULL (remember that your table prefix can be different than mdl_)
==='Invalid response value detected' when accessing My Courses or Course Overview ===
This usually happens when a course uses a language that isn't installed in the site. Please make sure that all courses use valid languages. This can be easily checked in the database, table "course", there is a column named "lang".
==='A required parameter (username) was missing'===
This may happen if your site implements HTTP redirects; the request is redirected by the browser not passing the POST parameters.

Unfortunately, this is something we cannot control in the Mobile app (it can't be handled via JavaScript). For further information, see http://stackoverflow.com/questions/228225/prevent-redirection-of-xmlhttprequest and http://stackoverflow.com/questions/4168784/ajax-redirection-handling

The solution is to change the HTTP redirect and use an HTML page with a meta tag or JavaScript redirect.
==='Cannot get course contents'===
This usually happens when the course is using a course format plugin that was uninstalled from the server or that was not properly installed.

Please, reinstall again the course format plugin.
==='Access control exception' or 'Your authentication token is invalid or has expired'===
Please double-check that 'Enable web services for mobile devices' (''enablemobilewebservice'') is actually enabled. (It might be unabled if for example you have reseted some roles.)

If this error appears as soon as you enter the username and password for a new site, then it probably means that the token expiration time is badly configured. This is how to fix it:
# Go to ''Site administration > Security > Site security settings''.
# Find the setting named ''User created token duration''.
# If the value is set to 0 or it's too low, please set it back to a valid value (the default value is 12 weeks).
# Click the 'Save changes' button.

===ipmismatch: 'Client IP address mismatch'===
This error can appear when a user opens your site in a browser while using the app. This happens if your site is behind a proxy and you're using one of these Moodle versions o higher: 3.5.11, 3.6.9, 3.7.5, 3.8.2, 3.9.0.

To fix it:
# Go to ''Site administration > Administration > Server > HTTP''.
# Find the setting named ''Ignore reverse proxies'' (reverseproxyignore).
# Enter the IP of your proxy (or range of IPs).
# Click the 'Save changes' button.
If you are still experiencing issues please try to change this setting "getremoteaddrconf" (Logged IP address source) to the different existing values.

Finally, it is possible to disable the IP restriction checks for functionality such as the QR login, to do that, go to Site administration > Mobile app > Mobile app authentication, and disable the "QR authentication same IP check" setting.
=== 'The param "includestealthmodules" is invalid' ===
Please contact your learning organisation so they upgrade to at least Moodle 3.5.3 (see [https://docs.moodle.org/35/en/Upgrading Upgrade to 3.5] as well as [[Upgrade overview]]) or they manually apply the patch listed here [[MDL-63542]].

==Older versions of the Moodle app==
We always recommend using the last version of the Moodle App but some times users are still using older versions this is the reason we are keeping this list:

=== Some users are asked to reauthenticate too often when they browse the site (Moodle App <3.9.3) ===
This can happen if the app is sending too many variables to a WebService, e.g. because a course has a large number of sections and/or activities. This error was fixed in the 3.9.3 version of the app, but if you are using an older version of the app you can increase the value of ''max_input_vars'' in ''php.ini'' to fix it in your server.

=== After upgrading to 3.9.5 some of my plugins have stopped working ===
The Moodle App 3.9.5 version came with some breaking changes for plugins, most of the existing plugins have been updated to support the new changes.
Please check the following list of plugins that should work for 3.9.5 once you have upgraded to the latest version indicated in the document: https://docs.google.com/spreadsheets/d/1E9PqcUBpp9SAfQc_zJtX5tf9GeS3UN76A85IrrB4UDw/edit#gid=0

==Any further questions?==
Please post in the [http://moodle.org/mod/forum/view.php?id=7798 Moodle for mobile forum] on moodle.org.

[[Category:FAQ]]

[[de:Moodle Mobile - FAQ]]
[[ca:Moodle Mobile FAQ]]
[[es:Moodle app FAQ]]
[[fr:Moodle pour les mobiles]]
[[ja:バイルMoodle FAQ]]

Moodle app FAQ

2025-05-16T08:16:25Z

Jleyva: /* The Moodle app might seem slow (especially on Android devices) */

{{Mobile}}
==Students==
===How can I log in?===
To log in to your Moodle site with the Moodle App, you need the URL (web address) of the Moodle site that you’re trying to access. If your organisation has Search enabled, you can try searching by the name of your organisation or eLearning site.

If your organisation allows you to log in via QR code, you’ll find the QR code at the bottom of your user profile on your Moodle site. You just need to press “Scan QR code” on the app, scan the QR code on your profile and you’ll be logged in automatically.

If your organisation allows you to log in using face recognition or fingerprint, you can activate this in the App, going to User account > Preferences. You’ll need to have biometric authentication enabled in your own device’s settings.
===Who can I contact for help with the app?===
If you’re a student and need help with issues related to logging in, registering to a Moodle site or trouble connecting to the app, you should contact your school or learning organisation. For example, one of your teachers, or the person who takes care of Moodle.
Moodle HQ make the Moodle software and the Moodle app, but they don’t manage nor have access to your Moodle site or your user data.
===How can I get the Moodle app?===
You can download the Moodle App for free from [https://play.google.com/store/apps/details?id=com.moodle.moodlemobile Google Play] and the Apple [https://itunes.apple.com/app/moodle-mobile/id633359593?mt=8 App Store]. You will find it by searching “Moodle”, and the author/owner is “Moodle Pty Ltd”.
If you are unable to download the app from Google play, please visit [https://download.moodle.org/mobile/ Moodle app downloads]
===I can't get the app to work. ===
To ensure that the Moodle app functions properly, please double-check that you have correctly entered the URL address of the Moodle site you are using (please visit [https://docs.moodle.org/en/Moodle_app_FAQ#I_can%E2%80%99t_find_my_Moodle_site_in_the_app. I can’t find my Moodle site in the app]). If you are experiencing difficulties connecting to your site, please contact the person or team who takes care of Moodle in your school or learning organisation. Please note the app only works with Moodle sites that have been set up to allow it, and that are running on at least Moodle 3.5.

===I can’t find my Moodle site in the app. ===
To find your Moodle site on the app login screen, try searching for the name of your school or learning organisation.

If your school or organisation doesn’t appear in the search, you can try searching by your Moodle site URL address instead. If you don’t know the address of your Moodle site, here’s how you can find it:
# Open a web browser (like Chrome or Safari) and go to your school’s Moodle site login page.
# At the top of the page in the address bar, you'll see the URL address of your Moodle site, e.g. “campus.example.edu”. [[File:FAQ I cant find my site 1.png|alt=URL|thumb|none|''campus.example.edu'']]
# Copy the URL (don’t copy the /login nor what comes after), paste it into Your site in the app, then select Connect to your site. [[File:FAQ I cant find my site 2.png|alt=Adding an URL to the app|thumb|none|Adding an URL to the app]]
# Now you can log in to your site with your username and password.

If you tried searching by URL address and still can’t find your Moodle site, please get in touch with the person who takes care of Moodle in your school or learning organisation.
===I can’t log in with the app===
To log in to your Moodle site using the app, you first need to connect to your school’s Moodle site (view [[I can’t find my Moodle site in the app]] if you can’t find your site).

Once you’ve connected to your Moodle site, you should be able to log in with your usual username and password.

If you forgot your username or password, select the option '''Forgotten your username or password?'''. If you still have trouble logging in or can’t see any options for retrieving your username or password, please get in touch with the person who takes care of Moodle in your school or learning organisation.
===I see an error message when I try to use the app===
If you see an error message that prevents you from using the app, please get in touch with the person who takes care of Moodle in your school or learning organisation.

Some of the most common errors that your school or learning organisation will be able to fix are:
* Your token is expired or not valid.
* An error mentioning the parameter “includestealthmodules”.
* The web service function is not available.
* A message about site maintenance.

If you’re experiencing any of these errors, contact your school or learning organisation for help.
===What permissions does the app require?===
The app requires the following permissions:
* Record audio - for uploading to your Moodle site
* Read and modify the contents of your SD card - for content to be downloaded to your SD Card for offline access.
* Network access - to be able to connect with your Moodle site and check if you are connected, and if not to switch to offline mode.
* Run at startup - to receive local notifications even when the app is running in the background.
* Prevent phone from sleeping - to receive push notifications anytime.
===What are the minimum device requirements to use the Moodle app?===
Android devices: Require Android 7.0 or later. (Users with Android 5 and 6 can still use version 4.3, but they will not receive any new updates.)

iOS devices (iPhones/iPads): Require iOS 13 or later. (Please note the app was only tested on versions iOS 14 and onward.)

===I can't see my course on the app. What do I do?===
Check with your course tutor that you are correctly enrolled.
=== Why can't I upload my assignment on the app?===
If you’re experiencing any issue uploading assignment, please contact your school or learning organisation for help.
===Why can't I sometimes access the app or submit anything to it?===
This could be because of interruptions in your internet connection. Wait a while and try again. If you continue to have problems, contact your school or learning organisation for help.
===Is there a space limit on my files?===
Assignments will have a size limit which you can see, those are set by your teachers. For other space limit questions, check with your your school or learning organisation .
===When are activities completed offline synchronized?===
See [[Moodle app synchronization]].
===Why the site is asking for my username and password when an activity is opened in the browser?===
For security reasons, between auto-logins you must wait 6 minutes (this should not be a problem because most of the browsers will keep your Moodle session open).
In recent Moodle versions, the previous value can be configured in Site Administration > Mobile app authentication > Minimum time between auto-login requests

=== The Moodle app might seem slow (especially on Android devices) ===
If the app feels slow, it might be due to things outside the app itself. This can include:
* Slow internet connection
* Network problems
* The server responding slowly
* Content or settings not made for mobile
* Using the app on an old device

We test the app carefully on many sites before each release, and we’re confident it usually works as well as or better than the website.

To make sure your site works well on mobile, please check [[Creating mobile-friendly courses]]

Finally, to troubleshoot this problem, we recommend trying the application with our demo site: https://school.moodledemo.net. Simply use the username "student" and the relevant password to access the site. If you find that the navigation and overall experience with the app are improved, then the issue may be at the server level. In this case, we suggest contacting your school or learning organisation for further assistance.

=== The Moodle app restarts/ closes / reopenes itself ===
This is likely because there are too many apps opened on your mobile device. Mobile devices have a finite amount of memory, and the device's memory manager is responsible for determining which applications to keep open and which to close.
To optimise your device's performance, we recommend closing all applications that are not currently in use. This will free up valuable memory and ensure that your device runs smoothly.
===I use LineageOS and I'm having problems using the app===
LineageOS uses a different WebView implementation not compatible vith the app. You need to install "Android System WebView" from Google Play (or via a trusted apk) and enabling it via Settings > Developer options > WebView implementation.
===H5P packages and external content embedded via iframes are not working on iOS ===
This is caused by a new feature of iOS 14 called ITP that blocks cookies for external sites embedded in the app (the H5P content is played embedded in an iframe pointing to the Moodle website) unless the user enables a setting in the app to allow those cookies.

The quick workaround is to enable the setting "Allow Cross-Website Tracking" available via the Settings app (look for the Moodle app, at the bottom) on your iPhone/iPad with iOS 14.
===I cannot reproduce audio that was recorded on browser on iOS devices (iPhones and iPads)===
This behaviour is related to this Moodle LMS bug: https://tracker.moodle.org/browse/MDL-80114

=== I don't receive calendar notifications (reminders) when using Android 12 or above ===

In order to receive calendar notifications you need to allow alarms and reminders for the Moodle app. To do this:
* Open Android Settings and go to the Moodle app settings. Another way to reach these settings is by long-clicking the Moodle app icon and pressing "App info".
* Make sure that Notifications are enabled.
* If you see a section called "Alarms & reminders", make sure it is Allowed (this setting is disabled by default in Android 14+).

==Teachers==
===How can I enable videos in my course to be downloaded?===
See the section 'Media download for offline usage' in [[Creating Moodle-app-friendly courses]].
===Which course format is it best to use?===
Topics or weekly course format is best suited to mobile devices.
===How do I make YouTube links open automatically in the app?===
Add YouTube links as a [[URL resource]].
===Why can't my students see their courses?===
If you or an administrator have correctly enrolled them in a course, they can see it in their mobile app. If they are correctly enrolled but can still not see their course, ask them to check with your Moodle site administrator.
=== I can't mark assignments in the app===
If you are experiencing problems when grading, please review that you are using the correct decimal separators (if the app interface is in English, you must use a period).
===What communications tools can I use in the app to engage with my learners?===
See [[Mobile app notifications]]. Chat, forums and messaging are all supported by the app.
===My Vimeo videos are not playing in the app===
In older versions of Moodle (pre-Moodle 3.7), it may be necessary to activate the "Allow frame embedding" admin setting. However, for those using Moodle version 3.7 or later, it is important to check whether a Proxy/Firewall/Web Server security module is setting the X-Frame-Options header in your HTTP request responses. If this is the case, it is recommended to deactivate this feature as it may cause conflicts, as Moodle already sets this header by default.

This setting is typically found in any of these configuration files .htaccess, httpd.conf or VirtualHost. To disable it, you can just use: Header always unset X-Frame-Options

You may also use Bootstrap responsive classes: https://getbootstrap.com/docs/4.0/utilities/embed/, for example, <div class="embed-responsive">
For older versions, see this forum discussion with a workaround: https://moodle.org/mod/forum/discuss.php?d=327342

If the issue is with vimeo videos on Moodle sites 3.10 or 3.11, please update the Moodle site to the latest version possible (at least 3.10.10 or 3.11.6). (See https://tracker.moodle.org/browse/MDL-74042)
===ReCaptcha doesn't work on my site===
In older versions of Moodle (pre-Moodle 3.7), it may be necessary to activate the "Allow frame embedding" admin setting. However, for those using Moodle version 3.7 or later, it is important to check whether a Proxy/Firewall/Web Server security module is setting the X-Frame-Options header in your HTTP request responses. If this is the case, it is recommended to deactivate this feature as it may cause conflicts, as Moodle already sets this header by default.
===H5P packages don't work on my site===
In older versions of Moodle (pre-Moodle 3.7), it may be necessary to activate the "Allow frame embedding" admin setting. However, for those using Moodle version 3.7 or later, it is important to check whether a Proxy/Firewall/Web Server security module is setting the X-Frame-Options header in your HTTP request responses. If this is the case, it is recommended to deactivate this feature as it may cause conflicts, as Moodle already sets this header by default.

This setting is typically found in any of these configuration files .htaccess, httpd.conf or VirtualHost. To disable it, you can just use: Header always unset X-Frame-Options

This can also happen when you are using the non-official H5P plugin (mod_hvp), in that case you will see the following message: This site is not configured properly for displaying mobile H5P content. Please contact a site administrator so they can apply the above suggested configuration changes.

'''Cookies issues'''

If your site uses HTTPS please ensure that the "Secure cookies only" (cookiesecure) setting under Site administration > HTTP security is enabled.

'''Dependency errors'''

When the following error appears "Missing dependency H5P.Editor. something X required by H5P.Editor. something Y". H5P packages need to include all the libraries (dependencies) they use so the package is self-contained. But sometimes packages might be missing at least one dependency.

In order to fix this, you could do the following:

Open Moodle’s Content Bank (from the link in the problematic H5P settings page) and upload your H5P package there, once uploaded, you will see the H5P package and an “Edit” button, click on that button so the editor opens, scroll down and click “Save”.
Now, you can replace the problematic H5P with this new one, for this, you can just include it from the Content bank by opening the activity settings page and the file picker.
=== I use a Moodle plugin but the app says it is not supported ===
You should contact the plugin developer and point him to this documentation: https://docs.moodle.org/dev/Moodle_Mobile_Remote_addons where it is explained how to add support to plugins in the Mobile app.

There is a list of Moodle plugins supported by the app here: https://moodle.org/plugins/browse.php?list=award&id=6
=== I have problems playing SCORM packages ===
This might be caused because:
* The SCORM was added using an advanced option (remote imsmanifest.xml packages or file system repository unzipped SCORMS)
* The SCORM ZIP file was created using a tool that does not create standardised ZIP files (for example, zip files containing the inverted path separator "\" will not work on Android)
Please refer to [[Moodle app SCORM player]] for additional information.
=== My quizzes or lessons are not working offline ===
You need to edit the quiz or lesson activity settings and enable the "Allow lesson/quiz to be attempted offline using the mobile app" configuration option.
=== Maths notation is not displaying correctly in the app ===
If you are having issues with MathJax, please enable the [[TeX notation filter]] also.

If you have both filters enabled, please leave MathJax above TeX so it is always processed before TeX.

If the issue persists, we suggest disabling the 'Remove HTML tags from all activity names' (''formatstringstriptags'') option in ''Site Administration'' > ''Appearance'' > ''HTML settings''.

=== How can I disable text selection / copy in the app? ===
You can create a remote theme and add some custom CSS rules to disable it, see https://docs.moodle.org/dev/Moodle_Mobile_Themes
=== My images, videos or audios stop working after the first time ===
Please make sure the URL you're using on the media file doesn't have any redirect (e.g. http to https), always try to use the final URL. There's a bug in the library we use to download those files, it doesn't work when downloading files with redirects. We have plans to remove that library from the app, but since then please always try to use URLs without redirects.

==Administrators==
=== What plans are available for the Moodle app? ===
There are three main plans available for the Moodle app: Free, Pro, and Premium, each offering different features and benefits. In addition to the three main plans, there is also a Branded Moodle App (BMA) option. The BMA is a custom-built app that is branded to your organization. Learn more in [[Moodle app plans]].
=== How can I have my site listed in the Moodle app site finder? ===
Please refer to our [[Moodle app guide for admins]] for instructions.
=== How can I debug errors in the app? ===
Go to the More tab and then to Settings > General. Enable "Display debug messages". This will show an explanatory message when an error occurs, alternatively, you can do a full debugging via: https://docs.moodle.org/dev/Moodle_Mobile_debugging_WS_requests

=== How can I disable features in the app? ===
Please go to ''Site administration > Mobile features > Disabled features'' and select all the features you want to disable.

To select multiple features you will have to use Ctrl (Cmd in Mac) + Click

=== How can I add custom menu items in the app? ===
You can add custom additional menu items in the "more" menu of the app, the one represented by three consecutive dots.

Please go to ''Site administration > Mobile features > Custom menu items'' and follow the instructions in [[Moodle_app_guide_for_admins#Custom_menu_items|Moodle app guide for admins]] for the correct format to use.

As a quick example:
Academy information|https://yoursite.com/mod/page/view.php?id=X |app|en|home

=== How can I customise the language strings in the app? ===

Please go to ''Site administration > Mobile features > Custom language strings'' and follow the instructions in [[Moodle_app_guide_for_admins#Custom_language_strings|Moodle app guide for admins]] for the format to use.

As a quick example:
core.user.student|Learner|en
core.user.student|Aprendiz|es

=== I can connect with my iPhone (or iPad) but not with my Android phone ===
This usually happens when the site is using https and the certificate is not correctly configured or it is using an old protocol, please use these pages to check this certificate: https://www.sslshopper.com/ssl-checker.html, https://www.geocerts.com/ssl_checker, and https://www.ssllabs.com/ssltest/analyze.html

'''The certificate of this site cannot be trusted by your device: TLS connection could not be established: javax.net.ssl.SSLHandshakeException'''

This error could be caused because in any of the certification paths there is a certificate using SHA-1. Starting Android 10 this is not allowed, more information here: https://developer.android.com/privacy-and-security/security-ssl

You could easily check the previous using https://www.ssllabs.com/ssltest/analyze.html and going to the Certification Paths -> Android section, if there is any mention to SHA-1 this could be the cause. You will need to upgrade your certificates to avoid using SHA-1.

=== My certificate is fine but I still can't connect ===
This is usually a server configuration problem caused by any of the following server configuration issues:

'''"Access to XMLHttpRequest at 'https://yoursite/webservice/rest/server.php?moodlewsrestformat=json<nowiki/>...' from origin '<nowiki>http://localhost'</nowiki> has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.'''

This is because a Proxy/Firewall/Web Server security module is removing automatically the Access-Control-Allow-Origin: * header that Moodle sets to allow Web Service requests.

It is totally secure to remove that Proxy/Firewall/Web Server rule/configuration because that header is only set by Moodle when needed.

'''"access-control-allow-origin cannot contain more than one origin".'''

iOS and Android apps do not allow the following header to contain more than one item: "Access-Control-Allow-Origin". For example, a header like this: Access-Control-Allow-Origin: *, https://mydomain.com will cause problems.

This HTTP header is not valid, according to the specification you can only specify a domain or a "*":
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin

Please, review if you have a Proxy/Firewall/Web Server adding automatically values to that HTTP header.

'''Security rules are blocking requests using the Accept-Charset header'''

Some security rules, such as OWASP ModSecurity, are blocking requests with this header that is sent by the Moodle App. In future releases of the app, this problem will be fixed. But in the meantime, you should disable it. Find more about this in MOBILE-4342.
=== My certificate is fine but the Moodle app is detecting http instead of https ===
If the Moodle app is detecting http instead of https, please revise config.php (check "wwwroot" as well as "httpswwwroot")
===After updating Moodle LMS to a recent version my users cannot login===
This only applies to sites that are configured to use log in via an embedded browser pointing to their Moodle site.
This behaviour could be related to this Moodle LMS issue: https://tracker.moodle.org/browse/MDL-81897.
There are several ways to fix this issue:
# Upgrade their Moodle site to any of the indicated version in the issue that will solve the problem
# Manually apply the patch here: https://github.com/jleyva/moodle/compare/462d5f04a8...MDL-81897-master
# Immediate workaround: Change the app authentication so it will launch in a separate browser, by going to Site admin > Mobile app authentication > Type of login (and select the option that mentions external/system browser), remember to Save Changes
We’d recommend doing 3) that will immediately address the issue that is affecting new logins.
===I can't get the app to work. What can I do?===
Assuming you have enabled mobile services on your site, please check:
# If your site uses an SSL certificate, it must be a trusted certificate, not self-signed. Please use these tools or a similar one to check that your certificate is valid: [https://www.sslshopper.com/ssl-checker.html SSL Checker], [https://www.geocerts.com/ssl_checker SSL Checker], and [https://www.ssllabs.com/ssltest/analyze.html SSL Server Test]. All the checks must be ok, including the "Certificate Chain Complete". Otherwise the app might work on iOS but not on Android.
# Make sure that the "Access-Control-Allow-Origin" header only contains one item. For example, a header like this: Access-Control-Allow-Origin: *, <nowiki>https://mydomain.com</nowiki> will cause problems.
# [[Debugging]] is disabled (in ''Site administration > Development > Debugging'')
# The ADOdb debug option is disabled if you are using the external database auth or enrolment plugin (in ''Plugins > Authentication > External database'' and in ''Plugins > Enrolment > External database'').
# SHA-1 https certificates are not supported anymore in Chrome, this means that the Android version of the app won't work for your site. If your site doesn't work in desktop Chrome or Chromium it won't work in the Android app. See https://blog.chromium.org/2014/09/gradually-sunsetting-sha-1.html for more information
# If you are using IIS check that Anonymous access is not disabled for the /webservice directory.
# If you are using a web application firewall like AWS WAF, StackPath, Barracuda, Cloudflare, Juniper, etc... try to temporary disable it to check if that's the cause. If so, you'll have to whitelist these endpoints: login/token.php, webservice/*, lib/ajax/*, media/player/vimeo/wsplayer.php and /tokenpluginfile.php
You can also add WAF rules to allow traffic by detecting the app user agent such as: (http.user_agent contains "MoodleMobile")
If you still have a problem, please post in the [https://moodle.org/mod/forum/view.php?id=7798 Moodle for mobile forum].

If the issue started after updating Moodle LMS please visit [[After updating Moodle LMS to a recent version my users cannot login]].

=== I cannot access with old users, but I can with recently created ones! ===
Please, do a "Purge all caches" via the Moodle administration settings, this will solve the problem.
===I can't view the courses tab as an administrator===
The Moodle app only displays courses you are enrolled in. If you want to view a course as an admin, you need to enrol in it.
===My Moodle site uses a SSO auth method (Shibboleth, CAS, Google OAuth, etc) and the app is not working===
See the section 'Mobile authentication' in the [[Moodle app guide for admins]] for details of how to configure it.

If configured the app is still not connecting: If your site uses an SSL certificate, it must be a trusted certificate, not self-signed. Please use this tool or a similar one to check that your certificate is fine: [https://www.geocerts.com/ssl_checker SSL Checker]. All the checks must be OK, including the "Certificate Chain Complete".

If your SSO method is unable to authenticate when using an "embedded browser" (it gives an authentication error), please check if it works with a "browser window". If it does work with the browser window then it means your SSO is performing an HTTP redirect, and these kind of redirects aren't supported by the app (the request is redirected by the browser not passing the POST parameters). Unfortunately, this is something we cannot control in the Mobile app (it can't be handled via JavaScript). For further information, see http://stackoverflow.com/questions/228225/prevent-redirection-of-xmlhttprequest and http://stackoverflow.com/questions/4168784/ajax-redirection-handling

There are only 2 possible solutions: set the authentication via a "browser window" instead of an embedded one (please notice this won't work in the Linux desktop app), or remove the redirect from the SSO auth method.
===SSO is not working with my custom auth plugin===
SSO should work in any plugin if the plugin handles correctly the $SESSION->wantsurl, this is the way SSO works when it is launched via the app:
* It launchs this URL https://yourmoodle/admin/tool/mobile/launch.php?service=local_mobile&passport=abc in the device browser
* If the user is not logged in, the browser will redirect the user to the login page
* If the auth plugin used implements correctly the handling of the wantsurl session var, once the user has logged in, the browser should redirect back to the https://yourmoodle/admin/tool/mobile/launch.php?service=local_mobile&passport=abc URL that will launch the mobile app via the custom URL protocol
Custom auth plugins may be failing in the last step,not redirecting back to tool/mobile, this will happen only if the plugin does not support correctly the $SESSION->wantsurl.

The SAML plugin works correctly but some modifications of that plugin may not work if important lines are changed.
===I am having problems requesting an airnotifier access key===
If you have registered your site but are still unable to request an access key, please register your site on the Moodle Apps Portal https://apps.moodle.com once your site is registered there, an Airnotifier access key will be automatically generated for you.
=== Push notifications are not working ===
Please check [[Mobile app notifications#Troubleshooting]]
=== How notifications icon badges are updated ===
'''Android''': Not all Android devices support icon badges so in some cases badges will never display numbers, also, depending on the device only a badge indicating that there are new notifications will be displayed when receiving a Push notification when the app is not in the foreground.

'''iOS''': The icon badge counter is only updated when the app is open and it will reflect the number of notifications pending reading or the number of message senders that sent you a message you have not read yet

In general, for iOS the icon badge displayed number should match the one displayed at the bottom of the app (or it should be the sum of the notifications and messages badges) and is not an indicator of the number of Push notifications the user has received, it acts as a reminder of pending notifications to be read that only gets updated when the user open the apps

There is an open issue to improve the behaviour on iOS, please watch MDL-73707
=== I configured 'QR code access' to automatic login, but the app still asks for credentials ===
Automatic authentication only works for Pro and Premium sites. You can see the app plans [https://moodle.com/app/ in this site].

If you're getting an error saying that the device you're using to connect isn't in the same network as the device that displays the QR code but both devices are connected to the same network, please check the section: [[#ipmismatch:_.27Client_IP_address_mismatch.27|ipmissmatch: 'Client IP address mismatch']].

=== I can log in on my Moodle site but I see a blank page or the app styles broken ===
This is usually because your Moodle site has a customised CSS.

Please try leaving empty CSS (''mobilecssurl'') on Site administration > Mobile app > Mobile appearance. If that works, please read [https://docs.moodle.org/dev/Moodle_App_Remote_Themes Moodle App Remote Themes] and create a new CSS file using the variables mentioned there

===The Moodle app does not connect to MoodleBox (or other internal self-hosted systems)===
You will need to disable SSL to make the app works, please see this forum discussion for more information: https://moodle.org/mod/forum/discuss.php?d=424353#p1739474
===I think I found a bug with the app. Where can I report it?===
# Log in to the [https://tracker.moodle.org/browse/MOBILE Moodle Mobile tracker] (you'll need to [http://tracker.moodle.org/secure/Signup%21default.jspa create a tracker account] if you've not done so previously)
# Check whether the issue has already been reported by doing a [https://tracker.moodle.org/issues/?jql=project%20%3D%20MOBILE search]
# If not, report the bug by clicking the 'Create Issue' link at the top right of the page, selecting 'Moodle app' as the project
# Add a detailed description providing as much information as possible (Moodle version, app version, device model and operating system, etc...), then click the Create button
===How can I get the app in my language?===
[[File:setting the app lang.png|thumb|100px|Setting your language]]
The Moodle app automatically detects your mobile's language and displays in the same language (if the translation exists). Otherwise, you can set the app language in App settings > General.

See also a post explaining how multi-lang works in the Moodle app: [https://moodle.org/mod/forum/discuss.php?d=453445#p1825637 Re: Language selector missing in Moodle app]

If the Moodle app is not yet available in your language, please contribute a translation! See [https://docs.moodle.org/dev/Translating%20Moodle%20Mobile Translating Moodle Mobile] for details of what to do.

=== Changes made to a Moodle site URL can cause logged-in users’ data to fail when synchronising. ===
We recommend that administrators manually log out all users after a site rename. If your site URL changes and have site users that are using the mobile Moodle App we suggest the following:
* For users that have not yet logged in - we recommend sending them the new URL
* For users already using the mobile Moodle App and potentially logged in request them to:
** log out of the mobile Moodle App,
** delete the old site, and
** log in using the new URL
Logged in Moodle users can continue working with the previous URL (with cached information) but they will not be able to synchronise the new information (therefore not receiving new information from their teachers, and teachers not receiving data or submissions from those students).
* To avoid the risk of data not synchronising, we recommend the site administrator logs out all app users, by manually deleting their tokens:
** Go to Site administration
** Click Server
** Click Web services
** Click Manage tokens
** Delete the tokens
Take into account that you still need to request your users to log in using the new URL.

=== Embedded content is not working ===

This could be caused because your site is using a Content-Security-Policy that is preventing the app from embedding content.

You can easily detect this when an error like this is displayed (javascript console): Refused to load URL because it does not appear in the frame-ancestors directive of the Content Security Policy.

If that's the case, you'd need to add the following elements: http://localhost moodleappfs://localhost at the end of the "Content-Security-Policy" HTTP header:

An example of a CSP allowing embedding Vimeo videos in the site and content in the app:
Content-Security-Policy: frame-ancestors 'self' https://*.vimeocdn.com https://*.vimeows.com https://*.vimeo.com http://localhost moodleappfs://localhost ;

Other type of embedded content that does not work is content hosted by Microsoft tools that require session or any type of authentication, such as SharePoint content.

=== Some activities are displayed incorrectly (blank, just a vertical line, ..) on the app ===
Please visit the forum post [[https://moodle.org/mod/forum/discuss.php?d=461909#p1854918| Some lesson activities do not display at all]].

==Error messages==
=== 'Coding error: version.php file is missing for the component' ===
This error message indicates that that plugin is not correctly installed (or uninstalled) on the Moodle site you use (see [[Installing plugins]]). Please review the mod/certificate folder to check if the version.php file is missing (or has incorrect permissions) as well as purge cache too.
=== 'Can not find data record in database table external_functions' ===
This error usually happens due to a bad configuration or setting value in your Moodle site, please check:
# The user quota global setting should be an integer. For more details, see the discussion [https://moodle.org/mod/forum/discuss.php?d=320873 How to enable Moodle Mobile App for all accounts].
# The ''usermaxuploadfilesize'' should be an integer, please try to decrease the size. It can be configured in ''Site Administration > Security > Site Policies > Maximum uploaded file size''. The default value (Site upload limit) depends on the PHP configuration, you might have to change the value of ''upload_max_filesize'' and ''post_max_size'' in your ''php.ini'' file.
# The user "lang" field in the database is set to a correct value and existing language installed in the site. Some times the lang field is set via external systems to incorrect values or pointing to a language pack that was uninstalled. Please, note that to fix this you need direct access to the database and your 'user' and 'course' table.
==='Cannot connect: Verify that you have typed correctly the URL and that your site uses Moodle 3.5 or later'===
Take into account that the app will only connect to Moodle LMS sites version 3.5 onward.
Please also check:
# Mobile services are enabled for the site.
# The user is entering the correct URL for the site (see FAQ above)
# For https sites, the certificate is valid (see FAQ above)
==='Invalid Moodle site version. The Moodle app only supports Moodle systems 3.5 onwards'===
The app will only connect to Moodle LMS sites version 3.5 onward (see [https://docs.moodle.org/35/en/Upgrading Upgrade to 3.5] as well as [[Upgrade overview]]).
==='We lost connection; you need to reconnect. Your token is now invalid.' on my custom version of the Moodle app ===
Please check:
# You have followed all the steps listed in [https://docs.moodle.org/dev/Moodle%20Mobile%20Developing%20a%20plugin%20tutorial Moodle Mobile Developing a plugin tutorial]
# You have enabled the [[Capabilities/moodle/webservice:createtoken|moodle/webservice:createtoken]] for the authenticated user
==='No permission to create web service token for the service local_mobile' when attempting to log in (any user that it is not an admin)===
Please check you have enabled the moodle/webservice:createtoken for the authenticated user or any global role you want to allow to use the mobile app
==='No permission to create web service token for the service local_mobile' when attempting to log in as an admin===
You need to create a token for the admin account (only) as follows:
# Go to ''Site administration > Plugins > Web services > Manage tokens''
# Click Add
# Enter the admin username and select 'Moodle app additional features service' (i.e. do NOT leave it as 'Moodle app web service')
# Click the 'Save changes' button.
==='Invalid response value detected' when accessing the site ===
The user quota global setting should be an integer. For more details, see the discussion [https://moodle.org/mod/forum/discuss.php?d=320873 How to enable Moodle Mobile App for all accounts].
=== ' Invalid response value detected: Invalid external api response: the value is "", the server was expecting "raw" type" ===
This usually happens when there is a field with value NULL in a table in the database that should not be there. This may happen if your Moodle has been upgraded over many years and the database schema is broken.

To fix it, you can do the following:
* Detect the field that is causing the problem (it should be indicated before the error message)
* Fix the field, for example, for the password field in the lesson table: UPDATE mdl_lesson SET password = '' WHERE password IS NULL (remember that your table prefix can be different than mdl_)
==='Invalid response value detected' when accessing My Courses or Course Overview ===
This usually happens when a course uses a language that isn't installed in the site. Please make sure that all courses use valid languages. This can be easily checked in the database, table "course", there is a column named "lang".
==='A required parameter (username) was missing'===
This may happen if your site implements HTTP redirects; the request is redirected by the browser not passing the POST parameters.

Unfortunately, this is something we cannot control in the Mobile app (it can't be handled via JavaScript). For further information, see http://stackoverflow.com/questions/228225/prevent-redirection-of-xmlhttprequest and http://stackoverflow.com/questions/4168784/ajax-redirection-handling

The solution is to change the HTTP redirect and use an HTML page with a meta tag or JavaScript redirect.
==='Cannot get course contents'===
This usually happens when the course is using a course format plugin that was uninstalled from the server or that was not properly installed.

Please, reinstall again the course format plugin.
==='Access control exception' or 'Your authentication token is invalid or has expired'===
Please double-check that 'Enable web services for mobile devices' (''enablemobilewebservice'') is actually enabled. (It might be unabled if for example you have reseted some roles.)

If this error appears as soon as you enter the username and password for a new site, then it probably means that the token expiration time is badly configured. This is how to fix it:
# Go to ''Site administration > Security > Site security settings''.
# Find the setting named ''User created token duration''.
# If the value is set to 0 or it's too low, please set it back to a valid value (the default value is 12 weeks).
# Click the 'Save changes' button.

===ipmismatch: 'Client IP address mismatch'===
This error can appear when a user opens your site in a browser while using the app. This happens if your site is behind a proxy and you're using one of these Moodle versions o higher: 3.5.11, 3.6.9, 3.7.5, 3.8.2, 3.9.0.

To fix it:
# Go to ''Site administration > Administration > Server > HTTP''.
# Find the setting named ''Ignore reverse proxies'' (reverseproxyignore).
# Enter the IP of your proxy (or range of IPs).
# Click the 'Save changes' button.
If you are still experiencing issues please try to change this setting "getremoteaddrconf" (Logged IP address source) to the different existing values.

Finally, it is possible to disable the IP restriction checks for functionality such as the QR login, to do that, go to Site administration > Mobile app > Mobile app authentication, and disable the "QR authentication same IP check" setting.
=== 'The param "includestealthmodules" is invalid' ===
Please contact your learning organisation so they upgrade to at least Moodle 3.5.3 (see [https://docs.moodle.org/35/en/Upgrading Upgrade to 3.5] as well as [[Upgrade overview]]) or they manually apply the patch listed here [[MDL-63542]].

==Older versions of the Moodle app==
We always recommend using the last version of the Moodle App but some times users are still using older versions this is the reason we are keeping this list:

=== Some users are asked to reauthenticate too often when they browse the site (Moodle App <3.9.3) ===
This can happen if the app is sending too many variables to a WebService, e.g. because a course has a large number of sections and/or activities. This error was fixed in the 3.9.3 version of the app, but if you are using an older version of the app you can increase the value of ''max_input_vars'' in ''php.ini'' to fix it in your server.

=== After upgrading to 3.9.5 some of my plugins have stopped working ===
The Moodle App 3.9.5 version came with some breaking changes for plugins, most of the existing plugins have been updated to support the new changes.
Please check the following list of plugins that should work for 3.9.5 once you have upgraded to the latest version indicated in the document: https://docs.google.com/spreadsheets/d/1E9PqcUBpp9SAfQc_zJtX5tf9GeS3UN76A85IrrB4UDw/edit#gid=0

==Any further questions?==
Please post in the [http://moodle.org/mod/forum/view.php?id=7798 Moodle for mobile forum] on moodle.org.

[[Category:FAQ]]

[[de:Moodle Mobile - FAQ]]
[[ca:Moodle Mobile FAQ]]
[[es:Moodle app FAQ]]
[[fr:Moodle pour les mobiles]]
[[ja:バイルMoodle FAQ]]

Creating mobile-friendly courses

2025-05-16T08:13:10Z

Jleyva: /* Offline activities */

Creating mobile-friendly courses

2025-05-16T08:07:12Z

Jleyva: /* Mobile device considerations */

Moodle app guide for admins

2025-05-06T06:27:16Z

Jleyva: /* App banners */

{{Mobile}}
==Enable mobile services on your site==
Your site needs to have mobile access enabled so users can use the mobile app.

For sites using https, mobile access is enabled by default in new installations of Moodle 3.0 onwards.

For http sites, mobile access can be enabled by an administrator as follows:
# In ''Site administration > Mobile app > Mobile settings'' tick the 'Enable web services for mobile devices' checkbox. (For 4.0 version: In ''Site administration > Advanced features'' tick the 'Enable web services for mobile devices' checkbox
# Click the button to save changes.
If your site uses a [https://en.wikipedia.org/wiki/Transport_Layer_Security SSL certificate], it must be a trusted certificate. For security reasons the app doesn't work with self-signed certificates.

Please, verify that your certificate is valid via: https://www.geocerts.com/ssl_checker (you shouldn't see any warning).

If your site has the /login directory protected (frequently done when using the Shibboleth authentication method), you must enable access to the login/token.php script.
===Frame embedding===
If your sites uses [https://en.wikipedia.org/wiki/ReCAPTCHA reCaptcha], Vimeo videos or custom menu items (as described bellow) you must enable the admin setting "Allow frame embedding" (allowframembedding). Please, note this is not necessary since Moodle 3.7
===Is your site behind a proxy, or load balancer or complex network infrastructure?===
In that case, you may need to configure the "Ignore reserver proxies" settings in Site administration > Administration > Server > HTTP
==Register your site on the Moodle Apps Portal==
We strongly recommend you to register your site for free on the Moodle Apps portal: https://apps.moodle.com

You will be able to retrieve statistics like the number of active user devices receiving Push Notifications and upgrade to a Pro/Premium plan for enjoying exclusive features.
==Simplify user onboarding==
Upon opening the Moodle app, first-time users encounter a "Your site" field, where they have to input the URL of their Moodle site to access their courses. To ensure a smooth onboarding experience for new users, follow these steps:
# Enable the '''Site finder''' feature that allows users to find their Moodle site by name, eliminating the need to manually enter the site URL. To enable this feature, view [[Moodle app guide for admins#Have your site listed in the Moodle app site finder|Have your site listed in the Moodle app site finder]] below.
# Enable the '''QR login''' feature (view [[Moodle app guide for admins#QR Login|instructions]] below). This feature allows users to scan a QR code available on their Moodle profile to access their Moodle site directly from the app.
# For Android users and Moodle LMS 4.3 and later: Encourage users to install the Moodle app by following the '''Get the mobile app''' link at the bottom of any Moodle page (located within the "'''?'''" icon on the desktop version). When users install the app through this link, they will be automatically redirected to their site login screen, eliminating the need to manually enter the site URL.
# Alternatively, you can create a dedicated help page for the Moodle app. This help page should include a link to the Google Play version of the app and clearly indicate the site URL referrer. For example, if your Moodle site is mymoodlesite.com the link will be https://play.google.com/store/apps/details?id=com.moodle.moodlemobile&referrer=siteurl%3Dhttps%3A%2F%2Fmymoodlesite.com
Please note that options 3&4 are not compatible with Google Workspace accounts (the installation referrer will be ignored in that case).
==Have your site listed in the Moodle app site finder==
The Moodle apps site finder enables a user to easily find their Moodle site by entering the name (no need to enter the site URL)
===How can I have my site listed in the Moodle app site finder?===
Your site will be automatically listed in the site finder if:
* either your site is registered and listed with a link on [https://stats.moodle.org/sites/ Registered sites] and has over five hundred mobile users and you have been using the Moodle app for over a year
* or you have purchased a [https://moodle.com/app/ Pro or Premium Moodle app subscription].
You can arrange for your site to be listed in the site finder as follows:
* If your site is hosted by a Moodle Partner, please contact them to request for your site to be listed.
* If you have a MoodleCloud site, please log in to the Moodle Apps Portal where you will find an option to have your site listed.
Otherwise, to have your site listed in the site finder, you need to purchase a [https://moodle.com/app/ Pro or Premium Moodle app subscription] from the Moodle Apps Portal.
===I don’t want my site listed in the Moodle app site finder. How can I remove it?===
You can remove your site from the site finder as follows:
# Log in to the [https://apps.moodle.com/ Moodle Apps Portal]. (If you don't yet have an account, you can create one for free.)
# Go to ‘App customisation’ -> ‘Site Listing’ and uncheck the option ‘Visible’ then save changes.
Your site will then be immediately removed from the site finder.

Alternatively, you can remove your site from the site finder by updating your site registration:
# Log in to your Moodle site as admin and go to ‘Site administration’ -> Registration.
# Change ‘Site listing’ to either ‘Do not list my site’ or ‘Only display my site name’.
Your site will then be removed from the site finder within 24 hours.
==Mobile authentication==

===MFA===
The Moodle mobile app does not support MFA natively yet, however, you can redirect users to a browser to force the authentication process to behave exactly as Moodle LMS. You can do the previous via Site administration > Mobile authentication > Type of login and then select any of the options that mention browser.

===SSO authentication method===
If your site uses a SSO authentication method (CAS, Shibboleth, LDAP SSO, OAuth...), then select via a browser window or via an embedded browser for 'Type of login' (typeoflogin) in 'Mobile authentication' in the Site administration. (This setting is provided for older pre-Moodle 3.2 sites via the [[Moodle Mobile additional features]] plugin.)

The options 'browser window' and 'embedded browser' are very similar; the only difference is when redirecting the user to enter their credentials in the site, the site will be opened in the device's default browser (for browser window) or the site will be opened "embedded" in the mobile app (for embedded browser). The user experience is better in embedded browser, but not all the authentication plugins will work in embedded browser (for example, if JavaScript popups are required they must use the 'browser window'). The admin should check whether both options work, and if so, choose 'embedded browser'.

If you are using Google OAuth you will have to use the 'browser window' method because Google recently blocked authentication via 'embedded browsers'.

If your organisation uses a custom branded app and 'Type of login' is set to 'Via a browser window' or 'Via embedded browser', then a URL scheme (forcedurlscheme) may be set. This will result in only the custom branded app working for the site: the official Moodle Mobile app will not work.
===QR Login===
Please note that this feature requires Moodle 3.9 and is only available if you are enjoying a [https://moodle.com/app/ Pro/Premium plan].

As a site administrator, you can enable login via QR. Please go to Site administration > Mobile app > Mobile authentication and select "QR code with automatic login" in the "QR code access" setting

Once enabled, your students will be able to login in the app by scanning a QR code available on their Moodle site profile.
===Biometric Login===
This feature is only available to Pro and [https://apps.moodle.com Premium plan customers].

Biometric login allows your users to log in to your site via the Moodle App on Android and iOS devices using their fingerprint, face recognition or any other biometric option available on their mobile device. This makes the login process simpler, faster and more secure, and is specially useful if Autologout is enabled on your site.

'''Enabling biometric login for your site'''

You can enable Biometric login as an authentication method through the Moodle Apps Portal, going to App customisation > Authentication > Biometric login, and then selecting “Enable biometric login”. Your users will then be able to choose whether they want to use Biometric login or not.

For security reasons, users may be prompted to re-enter their credentials periodically. This interval is determined by the 'User created token duration' (tokenduration) security setting, which is set to a default duration of three months.

'''Setting up biometric login as a user'''

To use biometric login in the Moodle App, users must have biometric authentication enabled in their own device's settings (e.g. FaceID or TouchID for iOs users, or Fingerprints for Android users).

The first three times users log in to the app after you enable Biometric login, they will see a notification telling them that they can activate this new authentication method to access the app (provided that they have biometric authentication enabled in their device's settings).

Users can activate and deactivate their biometric login any time in the Moodle App in User account > Preferences.
===Auto logout===
From Moodle LMS 4.3 onwards, you can enhance security by enforcing automatic logout for your users when they leave or close the app, or it goes to the background.

You can even set your own custom re-authentication time, to suit your organisation's security requirements.

To activate auto logout, go to Site administration > Mobile app > Mobile authentication.

This feature is particularly effective when paired with Biometric login, since that streamlines the login process for your users.

== Customise your app theme ==
The app can also retrieve your custom styles from your Moodle site. Since the app is a HTML5 app, you can safely apply any CSS, CSS2 and CSS3 style.

Go to ''Administration > Site administration > Mobile app > Mobile appearance'' and enter in the mobilecssurl field a valid URL pointing to a CSS file containing your custom styles.

The CSS should be placed inside your Moodle installation (in your custom theme or inside a local plugin).

'''For example:''' ''https://mymoodlesite.com/theme/mytheme/style/mymobileapp.css''

Once the user is logged in the app, remote CSS files for applying your custom styles are regularly retrieved.

Notice that on the first time a user opens the app, he will see the default "orange" style. Your custom styles will be applied once the user has added a site in the app.

For further information, see the dev docs [https://docs.moodle.org/dev/Moodle%20Mobile%20Themes Moodle Mobile Themes].

If you want your own custom branding for your organization, Moodle offers the The [https://moodle.com/branded-app Branded Moodle Mobile app] service, please visit https://moodle.com/app/ for more information.
== Moodle Mobile additional features plugin for old Moodle sites ==
For old Moodle sites it is recommended to install the [[Moodle Mobile additional features]] plugin.
== Notifications ==
You might find them annoying but push notifications keeps you and your users informed and updated on everything about the app. Moodle only send useful and important notifications such as new features or service disruptions.

Enabling push notifications is easy! An administrator can enable it by connecting their Moodle site/s to our free Notifications server available (only) for registered Moodle sites.

An access key can be obtained via ''Site administration > General > Messaging > Notification settings''. Be sure the 'Mobile' is enabled and then click the link to settings, on the next page select ''Request access key''. (For Moodle site versions 3.5 and 3.6 an access key can be obtained via ''Site administration > Plugins > Message outputs > Manage message outputs''. Then by clicking the link to the Mobile settings, on the next page select ''Request access key''.)

The full guide on enabling push notifications can be found here: [[Mobile app notifications]]
== App banners ==
[[File:app banner.png|thumb|Moodle Mobile app banner]]
App banners let your users know a mobile app is available for the site. App banners are only displayed when accessing the site using a mobile browser.

App banners are disabled by default. They can be enabled in 'Mobile appearance' in the Site administration.

If you are using a custom mobile app, you must provide the unique identifier for the iOS and Android app; if you use the Moodle Mobile app, the settings may be left as default.

Please, notice the following:
* App banners for iOS devices (iPhone, iPad or iPod) are only shown when accessing the site using the Safari browser and the mobile app is not installed on the device yet. App banners are not displayed when using private browsing either.
* App banners for Android devices are only shown in very recent Chrome browser versions and when the app is not installed. Note also that Chrome uses an engagement heuristic that will display the banner only under certain conditions, like interactions with the site, the last time you interacted with it, etc. You can remove the engagement restriction check by disabling this special chrome flag: chrome://flags/#bypass-app-banner-engagement-checks. Please note also that certain custom Android versions (such as Samsung and Huawei ones) do not always support this feature

=='Get the mobile app' link==
In Moodle 3.4 onwards, the link 'Get the mobile app' in the footer of each page on the site encourages users to make use of the mobile app.

By default, the link is https://download.moodle.org/mobile however the setting 'App download page' can be changed e.g. for sites using a branded mobile app.

If mobile services are not enabled for the site, then the 'Get the mobile app' link is not displayed.

To prevent the 'Get the mobile app' link being displayed, simply remove the URL from the 'App download page' setting and save changes.
== Configuring the app from your site ==
'''IMPORTANT''': Please notice that the type and number of features that you can customise depend on your Moodle Apps plan, you can register for free on https://apps.moodle.com to check the different plans.

In Moodle 3.3 onwards, or with the [[Moodle Mobile additional features]] plugin, settings in the Site administration enable admins to configure the app.
* In Moodle 3.3 onwards go to ''Site administration > Mobile features''
* In sites with the Moodle Mobile additional features plugin installed, go to ''Site administration > Plugins > Local plugins > Mobile additional features''
===Force log out===
Replace the Change site option to "Log out" so that users must enter their credentials on their next access. This is useful for custom mobile apps, as there is no reason for users wanting to switch to a different site.
===Disabled features===
The mobile app may be simplified by removing unwanted features. Some items may already be not available in the app because they are not enabled on your site.

Options to remove include:

* Offline use
* Blocks (Note that from '''Moodle 4.3.1''' the Global search and Search forums blocks can be removed.)
* Comments
* Ratings
* Tags
* Create new account
* Responsive menu items
* Main menu
** Site home
** My courses
** Dashboard
** Calendar
** Notifications
** Messages
** Grades
** My learning plans
** Blog
** Files
** Web page
** Help
* Course
** Blocks
** Blog
** Search
** Competencies
** Participants
** Grades
** Course completion
** Notes
** Download course (new in 3.5)
** Download courses (new in 3.5)
* User
** Blog
** Badges
** Competencies
** Course completion
** Grades
** Send message
** Add contact
** Block contact
** Add a new note
** User picture
* Files
** Private files
** Ste files
** Upload
* Modules (Each module can be disabled separately)
* Blocks (Each block available in the app can be disabled separately)

===Custom menu items===
Additional items can be added to the app main menu (the more menu), such as a link to a different grade book.

In order to do so go to "Site administration > Mobile features > Custom menu items"

Each custom menu item should have the format: item text, link URL, link-opening method and language code (optional, for displaying the item to users of the specified language only), icon (optional, the name of the icon from https://ionicons.com) separated by pipe characters.

Possible link-opening methods are:
* app - for linking to an activity supported by the app i.e. almost all activity types, as listed in [[Moodle Mobile features]].
* inappbrowser - for linking to external URLs or site functionalities not supported by the app. The link will open in a browser inside the app overlaying the complete screen.
* browser - as for inappbrowser except that the link will instead open in the device default browser outside the app.
* embedded - as for inappbrowser except that the link will instead open in an iframe in a new page in the app. (For this option you may need to enable the admin setting "Allow frame embedding" (allowframembedding)
Tip: If you add a custom menu item and save changes, then it doesn't appear in the app main menu, double check that the item is correctly formatted.

Please, note that if custom menu items have the same URL, same link-opening method, and same language only the first custom menu item will be shown.

Please, note that if the app is using a language not indicated in the previous list, the first language in the list will be used. (So if you have a custom menu item in English (en) and French (fr), and the app is using Spanish the user will still see that custom menu item in English)

If you want options tied to a language, you can append _only to the language code, for example:
en_only
es_only, will display the custom menu item only when the app language is English or Spanish.

Example of a menu item (it will display a home icon followed by Academy information linking to the URL indicated):
Academy information|https://yoursite.com/mod/page/view.php?id=X |app|en|home

===Responsive menu items===
From 3.7 onwards menu items on bottom tabs are moved to the side of the screen on big screens. Also the number of items displayed on the menu may vary:
* On small screens (usually phones) from 2 to 5 items will be displayed depending on the size of the screen.
* On big screens (usually tablets an desktop version) more than 2 items will be displayed without limit.
If '''Responsive menu items''' is selected in Disabled features items will be displayed in side of bottom anyway but 5 items will be displayed in all cases without depending on the size of the screen.
===Custom language strings ===
Words and phrases displayed in the app can be customised via the "Site administration > Mobile app features > Custom language strings" (customlangstrings) setting.

Enter each custom language string on a new line with format: string identifier, custom language string and language code, separated by pipe characters. For example:
core.user.student|Learner|en
core.user.student|Aprendiz|es
The complete list of string identifiers is listed in https://latest.apps.moodledemo.net/assets/lang/en.json

The string identifier is before the colon.

For example:

"core.user.student": "Student",

means that the string "Student" has string identifier "core.user.student".
==Analytics and stats==

===Usage statistics from your Moodle site===

To retrieve information about the Moodle app usage, site administrators and teachers can check the system, course or activity logs.

Among the log filters, there is a field called "All sources" with an option "Web Service/ws" that can be used to filter the entry logs generated by the mobile application.

You can compare the number of log entries generated by the "Web" versus "Web Service" (mobile app) to have an overall idea about how your users use the platform.

Please, notice that if you have custom "Web Services" or an installed plugin that uses Web Services, you will also see entries for them under the same filter.

If you have access to the site database, the table "external_tokens" has a "lastaccess" timestamp field that could be used to obtain active users of the app every day.

===Integration with Matomo analytics===
Note: This feature is available for [https://apps.moodle.com Premium app plans and Branded Moodle Apps]. To use this integration, you will need to have your own instance of Matomo.

Matomo is an open source web analytics tool that helps you monitor traffic to your Moodle site, including app activity.

'''Connecting to your Matomo instance in the Apps portal'''
[[File:Captura de pantalla 2023-11-14 a las 12.03.36.png|thumb|Moodle App Matomo Integration set up]]
To use Matomo to track app activity on your Moodle site, you will need to have your own instance of Matomo analytics, and to add your Moodle site as one of your measurable websites (see instructions on [https://matomo.org/faq/how-to/create-and-manage-websites/ Matomo’s website]). Then, follow these steps:
# Log in to the [https://apps.moodle.com Apps portal].
# Go to '''App customisation''' > '''Analytics''' > '''Matomo analytics'''.
# Check '''Track app activity'''.
# Add your '''Matomo URL''' - that's the URL of your Matomo instance, for example https://yoursite.matomo.cloud.
# Add the '''Website ID''' associated with your Moodle site in Matomo. To obtain this ID:
## Log in to your Matomo account.
## Go to '''Administration''' using the gear icon on the right side of the top navigation bar.
## On the left-hand panel, select '''Websites''' > '''Manage'''.
## In your list of measurables, find the Moodle site in which you want to track app activity. The '''ID''' of the measurable is the '''Website ID''' you need to enter in the apps portal.
# Click '''Save changes''' to establish the connection and start tracking app activity.
# If you'd like to stop tracking at any time, uncheck '''Track app activity''' and then save changes.

To filter Matomo data to isolate mobile app usage from Moodle site interactions, follow these steps:
[[File:Captura de pantalla 2023-11-14 a las 12.05.05.png|thumb|Moodle App Matomo referrer set-up]]
# Log in to your Matomo account.
# Click '''All visits''' at the top of the page
# Create a custom segment by applying this configuration: “Referrer URL” “is” “https://moodlemobile”
# To only see Moodle site interactions, do the following: “Referrer URL” “is not” “https://moodlemobile”

Please notice that the integration with Matomo does not work offline.

===Google Analytics for Firebase===
Only available when purchasing a [https://moodle.com/branded-app/ Branded Moodle App].

Google Analytics for Firebase is a free tool that provides valuable insights and data about how users interact with mobile apps.

Please notice that the integration with Google Analytics for Firebase does not work offline.

===Google Play and Apple App Store statistics===

If you have a custom mobile application, you can access statistics about app downloads and user engagement such as weekly active users and devices.

Google play:
# Go to Google Play console: https://play.google.com/console
# Select your app from the list.
# Navigate to specific tabs, such as "Statistics"

Apple App Store:
# Log in to App Store Connect: https://appstoreconnect.apple.com/
# Go to "App Analytics" from the dashboard.

==Web services token duration==
From Moodle 3.4 onwards, an admin can set how long a web services token created by a user (for example via the mobile app) is valid. (In previous versions of Moodle a token was valid for 3 months.)

The setting that dictates the previous 'User created token duration' (tokenduration) can be found under the Security section.
==App's cache==
The app caches WebService requests to decrease data usage and increase the app's speed. When the app needs to get some data from Moodle, it will use a cached request as long as it isn't expired.

This cache was improved in Moodle App 3.7.0, now there are several cache times depending on the WS being called. This means that some requests will expire more often than others. Also, if the user isn't using a WiFi connection, the expiration time will also be longer to decrease the data usage. These cache times cannot be configured using a Moodle setting.
==See also==
* [https://moodle.academy/course/view.php?id=100 Moodle App Configuration]- a free self-paced course for admins on Moodle Academy.
* [[Moodle Mobile FAQ]] for other administration-related mobile app questions.
* [[Moodle app security]]
* [https://docs.moodle.org/dev/Moodle%20Mobile%20debugging%20WS%20requests dev:Moodle Mobile debugging WS requests] - a guide to helping you find and report problems with the Moodle Mobile app on your site
* [https://docs.moodle.org/dev/%20Moodle%20Mobile%20Roadmap dev: Moodle Mobile Roadmap]
* [https://docs.moodle.org/dev/Moodle%20Mobile%20release%20notes dev:Moodle Mobile release notes]
* [https://docs.moodle.org/dev/Moodle%20Mobile Moodle Mobile developer docs]
* [[Moodle Mobile availability plugin]]
* [[Mobile web services]]
[https://docs.moodle.org/fr/ Guide mobile pour administrateurs]
[https://docs.moodle.org/es/Moodle app guía para administradores]
[https://docs.moodle.org/de/Moodle App - Anleitung für Administrator/innen]

Moodle app guide for admins

2025-05-06T06:26:37Z

Jleyva: /* App banners */

{{Mobile}}
==Enable mobile services on your site==
Your site needs to have mobile access enabled so users can use the mobile app.

For sites using https, mobile access is enabled by default in new installations of Moodle 3.0 onwards.

For http sites, mobile access can be enabled by an administrator as follows:
# In ''Site administration > Mobile app > Mobile settings'' tick the 'Enable web services for mobile devices' checkbox. (For 4.0 version: In ''Site administration > Advanced features'' tick the 'Enable web services for mobile devices' checkbox
# Click the button to save changes.
If your site uses a [https://en.wikipedia.org/wiki/Transport_Layer_Security SSL certificate], it must be a trusted certificate. For security reasons the app doesn't work with self-signed certificates.

Please, verify that your certificate is valid via: https://www.geocerts.com/ssl_checker (you shouldn't see any warning).

If your site has the /login directory protected (frequently done when using the Shibboleth authentication method), you must enable access to the login/token.php script.
===Frame embedding===
If your sites uses [https://en.wikipedia.org/wiki/ReCAPTCHA reCaptcha], Vimeo videos or custom menu items (as described bellow) you must enable the admin setting "Allow frame embedding" (allowframembedding). Please, note this is not necessary since Moodle 3.7
===Is your site behind a proxy, or load balancer or complex network infrastructure?===
In that case, you may need to configure the "Ignore reserver proxies" settings in Site administration > Administration > Server > HTTP
==Register your site on the Moodle Apps Portal==
We strongly recommend you to register your site for free on the Moodle Apps portal: https://apps.moodle.com

You will be able to retrieve statistics like the number of active user devices receiving Push Notifications and upgrade to a Pro/Premium plan for enjoying exclusive features.
==Simplify user onboarding==
Upon opening the Moodle app, first-time users encounter a "Your site" field, where they have to input the URL of their Moodle site to access their courses. To ensure a smooth onboarding experience for new users, follow these steps:
# Enable the '''Site finder''' feature that allows users to find their Moodle site by name, eliminating the need to manually enter the site URL. To enable this feature, view [[Moodle app guide for admins#Have your site listed in the Moodle app site finder|Have your site listed in the Moodle app site finder]] below.
# Enable the '''QR login''' feature (view [[Moodle app guide for admins#QR Login|instructions]] below). This feature allows users to scan a QR code available on their Moodle profile to access their Moodle site directly from the app.
# For Android users and Moodle LMS 4.3 and later: Encourage users to install the Moodle app by following the '''Get the mobile app''' link at the bottom of any Moodle page (located within the "'''?'''" icon on the desktop version). When users install the app through this link, they will be automatically redirected to their site login screen, eliminating the need to manually enter the site URL.
# Alternatively, you can create a dedicated help page for the Moodle app. This help page should include a link to the Google Play version of the app and clearly indicate the site URL referrer. For example, if your Moodle site is mymoodlesite.com the link will be https://play.google.com/store/apps/details?id=com.moodle.moodlemobile&referrer=siteurl%3Dhttps%3A%2F%2Fmymoodlesite.com
Please note that options 3&4 are not compatible with Google Workspace accounts (the installation referrer will be ignored in that case).
==Have your site listed in the Moodle app site finder==
The Moodle apps site finder enables a user to easily find their Moodle site by entering the name (no need to enter the site URL)
===How can I have my site listed in the Moodle app site finder?===
Your site will be automatically listed in the site finder if:
* either your site is registered and listed with a link on [https://stats.moodle.org/sites/ Registered sites] and has over five hundred mobile users and you have been using the Moodle app for over a year
* or you have purchased a [https://moodle.com/app/ Pro or Premium Moodle app subscription].
You can arrange for your site to be listed in the site finder as follows:
* If your site is hosted by a Moodle Partner, please contact them to request for your site to be listed.
* If you have a MoodleCloud site, please log in to the Moodle Apps Portal where you will find an option to have your site listed.
Otherwise, to have your site listed in the site finder, you need to purchase a [https://moodle.com/app/ Pro or Premium Moodle app subscription] from the Moodle Apps Portal.
===I don’t want my site listed in the Moodle app site finder. How can I remove it?===
You can remove your site from the site finder as follows:
# Log in to the [https://apps.moodle.com/ Moodle Apps Portal]. (If you don't yet have an account, you can create one for free.)
# Go to ‘App customisation’ -> ‘Site Listing’ and uncheck the option ‘Visible’ then save changes.
Your site will then be immediately removed from the site finder.

Alternatively, you can remove your site from the site finder by updating your site registration:
# Log in to your Moodle site as admin and go to ‘Site administration’ -> Registration.
# Change ‘Site listing’ to either ‘Do not list my site’ or ‘Only display my site name’.
Your site will then be removed from the site finder within 24 hours.
==Mobile authentication==

===MFA===
The Moodle mobile app does not support MFA natively yet, however, you can redirect users to a browser to force the authentication process to behave exactly as Moodle LMS. You can do the previous via Site administration > Mobile authentication > Type of login and then select any of the options that mention browser.

===SSO authentication method===
If your site uses a SSO authentication method (CAS, Shibboleth, LDAP SSO, OAuth...), then select via a browser window or via an embedded browser for 'Type of login' (typeoflogin) in 'Mobile authentication' in the Site administration. (This setting is provided for older pre-Moodle 3.2 sites via the [[Moodle Mobile additional features]] plugin.)

The options 'browser window' and 'embedded browser' are very similar; the only difference is when redirecting the user to enter their credentials in the site, the site will be opened in the device's default browser (for browser window) or the site will be opened "embedded" in the mobile app (for embedded browser). The user experience is better in embedded browser, but not all the authentication plugins will work in embedded browser (for example, if JavaScript popups are required they must use the 'browser window'). The admin should check whether both options work, and if so, choose 'embedded browser'.

If you are using Google OAuth you will have to use the 'browser window' method because Google recently blocked authentication via 'embedded browsers'.

If your organisation uses a custom branded app and 'Type of login' is set to 'Via a browser window' or 'Via embedded browser', then a URL scheme (forcedurlscheme) may be set. This will result in only the custom branded app working for the site: the official Moodle Mobile app will not work.
===QR Login===
Please note that this feature requires Moodle 3.9 and is only available if you are enjoying a [https://moodle.com/app/ Pro/Premium plan].

As a site administrator, you can enable login via QR. Please go to Site administration > Mobile app > Mobile authentication and select "QR code with automatic login" in the "QR code access" setting

Once enabled, your students will be able to login in the app by scanning a QR code available on their Moodle site profile.
===Biometric Login===
This feature is only available to Pro and [https://apps.moodle.com Premium plan customers].

Biometric login allows your users to log in to your site via the Moodle App on Android and iOS devices using their fingerprint, face recognition or any other biometric option available on their mobile device. This makes the login process simpler, faster and more secure, and is specially useful if Autologout is enabled on your site.

'''Enabling biometric login for your site'''

You can enable Biometric login as an authentication method through the Moodle Apps Portal, going to App customisation > Authentication > Biometric login, and then selecting “Enable biometric login”. Your users will then be able to choose whether they want to use Biometric login or not.

For security reasons, users may be prompted to re-enter their credentials periodically. This interval is determined by the 'User created token duration' (tokenduration) security setting, which is set to a default duration of three months.

'''Setting up biometric login as a user'''

To use biometric login in the Moodle App, users must have biometric authentication enabled in their own device's settings (e.g. FaceID or TouchID for iOs users, or Fingerprints for Android users).

The first three times users log in to the app after you enable Biometric login, they will see a notification telling them that they can activate this new authentication method to access the app (provided that they have biometric authentication enabled in their device's settings).

Users can activate and deactivate their biometric login any time in the Moodle App in User account > Preferences.
===Auto logout===
From Moodle LMS 4.3 onwards, you can enhance security by enforcing automatic logout for your users when they leave or close the app, or it goes to the background.

You can even set your own custom re-authentication time, to suit your organisation's security requirements.

To activate auto logout, go to Site administration > Mobile app > Mobile authentication.

This feature is particularly effective when paired with Biometric login, since that streamlines the login process for your users.

== Customise your app theme ==
The app can also retrieve your custom styles from your Moodle site. Since the app is a HTML5 app, you can safely apply any CSS, CSS2 and CSS3 style.

Go to ''Administration > Site administration > Mobile app > Mobile appearance'' and enter in the mobilecssurl field a valid URL pointing to a CSS file containing your custom styles.

The CSS should be placed inside your Moodle installation (in your custom theme or inside a local plugin).

'''For example:''' ''https://mymoodlesite.com/theme/mytheme/style/mymobileapp.css''

Once the user is logged in the app, remote CSS files for applying your custom styles are regularly retrieved.

Notice that on the first time a user opens the app, he will see the default "orange" style. Your custom styles will be applied once the user has added a site in the app.

For further information, see the dev docs [https://docs.moodle.org/dev/Moodle%20Mobile%20Themes Moodle Mobile Themes].

If you want your own custom branding for your organization, Moodle offers the The [https://moodle.com/branded-app Branded Moodle Mobile app] service, please visit https://moodle.com/app/ for more information.
== Moodle Mobile additional features plugin for old Moodle sites ==
For old Moodle sites it is recommended to install the [[Moodle Mobile additional features]] plugin.
== Notifications ==
You might find them annoying but push notifications keeps you and your users informed and updated on everything about the app. Moodle only send useful and important notifications such as new features or service disruptions.

Enabling push notifications is easy! An administrator can enable it by connecting their Moodle site/s to our free Notifications server available (only) for registered Moodle sites.

An access key can be obtained via ''Site administration > General > Messaging > Notification settings''. Be sure the 'Mobile' is enabled and then click the link to settings, on the next page select ''Request access key''. (For Moodle site versions 3.5 and 3.6 an access key can be obtained via ''Site administration > Plugins > Message outputs > Manage message outputs''. Then by clicking the link to the Mobile settings, on the next page select ''Request access key''.)

The full guide on enabling push notifications can be found here: [[Mobile app notifications]]
== App banners ==
[[File:app banner.png|thumb|Moodle Mobile app banner]]
App banners let your users know a mobile app is available for the site. App banners are only displayed when accessing the site using a mobile browser.

App banners are disabled by default. They can be enabled in 'Mobile appearance' in the Site administration.

If you are using a custom mobile app, you must provide the unique identifier for the iOS and Android app; if you use the Moodle Mobile app, the settings may be left as default.

Please, notice the following:
* App banners for iOS devices (iPhone, iPad or iPod) are only shown when accessing the site using the Safari browser and the mobile app is not installed on the device yet.
* App banners for Android devices are only shown in very recent Chrome browser versions and when the app is not installed. Note also that Chrome uses an engagement heuristic that will display the banner only under certain conditions, like interactions with the site, the last time you interacted with it, etc. You can remove the engagement restriction check by disabling this special chrome flag: chrome://flags/#bypass-app-banner-engagement-checks. Please note also that certain custom Android versions (such as Samsung and Huawei ones) do not always support this feature

=='Get the mobile app' link==
In Moodle 3.4 onwards, the link 'Get the mobile app' in the footer of each page on the site encourages users to make use of the mobile app.

By default, the link is https://download.moodle.org/mobile however the setting 'App download page' can be changed e.g. for sites using a branded mobile app.

If mobile services are not enabled for the site, then the 'Get the mobile app' link is not displayed.

To prevent the 'Get the mobile app' link being displayed, simply remove the URL from the 'App download page' setting and save changes.
== Configuring the app from your site ==
'''IMPORTANT''': Please notice that the type and number of features that you can customise depend on your Moodle Apps plan, you can register for free on https://apps.moodle.com to check the different plans.

In Moodle 3.3 onwards, or with the [[Moodle Mobile additional features]] plugin, settings in the Site administration enable admins to configure the app.
* In Moodle 3.3 onwards go to ''Site administration > Mobile features''
* In sites with the Moodle Mobile additional features plugin installed, go to ''Site administration > Plugins > Local plugins > Mobile additional features''
===Force log out===
Replace the Change site option to "Log out" so that users must enter their credentials on their next access. This is useful for custom mobile apps, as there is no reason for users wanting to switch to a different site.
===Disabled features===
The mobile app may be simplified by removing unwanted features. Some items may already be not available in the app because they are not enabled on your site.

Options to remove include:

* Offline use
* Blocks (Note that from '''Moodle 4.3.1''' the Global search and Search forums blocks can be removed.)
* Comments
* Ratings
* Tags
* Create new account
* Responsive menu items
* Main menu
** Site home
** My courses
** Dashboard
** Calendar
** Notifications
** Messages
** Grades
** My learning plans
** Blog
** Files
** Web page
** Help
* Course
** Blocks
** Blog
** Search
** Competencies
** Participants
** Grades
** Course completion
** Notes
** Download course (new in 3.5)
** Download courses (new in 3.5)
* User
** Blog
** Badges
** Competencies
** Course completion
** Grades
** Send message
** Add contact
** Block contact
** Add a new note
** User picture
* Files
** Private files
** Ste files
** Upload
* Modules (Each module can be disabled separately)
* Blocks (Each block available in the app can be disabled separately)

===Custom menu items===
Additional items can be added to the app main menu (the more menu), such as a link to a different grade book.

In order to do so go to "Site administration > Mobile features > Custom menu items"

Each custom menu item should have the format: item text, link URL, link-opening method and language code (optional, for displaying the item to users of the specified language only), icon (optional, the name of the icon from https://ionicons.com) separated by pipe characters.

Possible link-opening methods are:
* app - for linking to an activity supported by the app i.e. almost all activity types, as listed in [[Moodle Mobile features]].
* inappbrowser - for linking to external URLs or site functionalities not supported by the app. The link will open in a browser inside the app overlaying the complete screen.
* browser - as for inappbrowser except that the link will instead open in the device default browser outside the app.
* embedded - as for inappbrowser except that the link will instead open in an iframe in a new page in the app. (For this option you may need to enable the admin setting "Allow frame embedding" (allowframembedding)
Tip: If you add a custom menu item and save changes, then it doesn't appear in the app main menu, double check that the item is correctly formatted.

Please, note that if custom menu items have the same URL, same link-opening method, and same language only the first custom menu item will be shown.

Please, note that if the app is using a language not indicated in the previous list, the first language in the list will be used. (So if you have a custom menu item in English (en) and French (fr), and the app is using Spanish the user will still see that custom menu item in English)

If you want options tied to a language, you can append _only to the language code, for example:
en_only
es_only, will display the custom menu item only when the app language is English or Spanish.

Example of a menu item (it will display a home icon followed by Academy information linking to the URL indicated):
Academy information|https://yoursite.com/mod/page/view.php?id=X |app|en|home

===Responsive menu items===
From 3.7 onwards menu items on bottom tabs are moved to the side of the screen on big screens. Also the number of items displayed on the menu may vary:
* On small screens (usually phones) from 2 to 5 items will be displayed depending on the size of the screen.
* On big screens (usually tablets an desktop version) more than 2 items will be displayed without limit.
If '''Responsive menu items''' is selected in Disabled features items will be displayed in side of bottom anyway but 5 items will be displayed in all cases without depending on the size of the screen.
===Custom language strings ===
Words and phrases displayed in the app can be customised via the "Site administration > Mobile app features > Custom language strings" (customlangstrings) setting.

Enter each custom language string on a new line with format: string identifier, custom language string and language code, separated by pipe characters. For example:
core.user.student|Learner|en
core.user.student|Aprendiz|es
The complete list of string identifiers is listed in https://latest.apps.moodledemo.net/assets/lang/en.json

The string identifier is before the colon.

For example:

"core.user.student": "Student",

means that the string "Student" has string identifier "core.user.student".
==Analytics and stats==

===Usage statistics from your Moodle site===

To retrieve information about the Moodle app usage, site administrators and teachers can check the system, course or activity logs.

Among the log filters, there is a field called "All sources" with an option "Web Service/ws" that can be used to filter the entry logs generated by the mobile application.

You can compare the number of log entries generated by the "Web" versus "Web Service" (mobile app) to have an overall idea about how your users use the platform.

Please, notice that if you have custom "Web Services" or an installed plugin that uses Web Services, you will also see entries for them under the same filter.

If you have access to the site database, the table "external_tokens" has a "lastaccess" timestamp field that could be used to obtain active users of the app every day.

===Integration with Matomo analytics===
Note: This feature is available for [https://apps.moodle.com Premium app plans and Branded Moodle Apps]. To use this integration, you will need to have your own instance of Matomo.

Matomo is an open source web analytics tool that helps you monitor traffic to your Moodle site, including app activity.

'''Connecting to your Matomo instance in the Apps portal'''
[[File:Captura de pantalla 2023-11-14 a las 12.03.36.png|thumb|Moodle App Matomo Integration set up]]
To use Matomo to track app activity on your Moodle site, you will need to have your own instance of Matomo analytics, and to add your Moodle site as one of your measurable websites (see instructions on [https://matomo.org/faq/how-to/create-and-manage-websites/ Matomo’s website]). Then, follow these steps:
# Log in to the [https://apps.moodle.com Apps portal].
# Go to '''App customisation''' > '''Analytics''' > '''Matomo analytics'''.
# Check '''Track app activity'''.
# Add your '''Matomo URL''' - that's the URL of your Matomo instance, for example https://yoursite.matomo.cloud.
# Add the '''Website ID''' associated with your Moodle site in Matomo. To obtain this ID:
## Log in to your Matomo account.
## Go to '''Administration''' using the gear icon on the right side of the top navigation bar.
## On the left-hand panel, select '''Websites''' > '''Manage'''.
## In your list of measurables, find the Moodle site in which you want to track app activity. The '''ID''' of the measurable is the '''Website ID''' you need to enter in the apps portal.
# Click '''Save changes''' to establish the connection and start tracking app activity.
# If you'd like to stop tracking at any time, uncheck '''Track app activity''' and then save changes.

To filter Matomo data to isolate mobile app usage from Moodle site interactions, follow these steps:
[[File:Captura de pantalla 2023-11-14 a las 12.05.05.png|thumb|Moodle App Matomo referrer set-up]]
# Log in to your Matomo account.
# Click '''All visits''' at the top of the page
# Create a custom segment by applying this configuration: “Referrer URL” “is” “https://moodlemobile”
# To only see Moodle site interactions, do the following: “Referrer URL” “is not” “https://moodlemobile”

Please notice that the integration with Matomo does not work offline.

===Google Analytics for Firebase===
Only available when purchasing a [https://moodle.com/branded-app/ Branded Moodle App].

Google Analytics for Firebase is a free tool that provides valuable insights and data about how users interact with mobile apps.

Please notice that the integration with Google Analytics for Firebase does not work offline.

===Google Play and Apple App Store statistics===

If you have a custom mobile application, you can access statistics about app downloads and user engagement such as weekly active users and devices.

Google play:
# Go to Google Play console: https://play.google.com/console
# Select your app from the list.
# Navigate to specific tabs, such as "Statistics"

Apple App Store:
# Log in to App Store Connect: https://appstoreconnect.apple.com/
# Go to "App Analytics" from the dashboard.

==Web services token duration==
From Moodle 3.4 onwards, an admin can set how long a web services token created by a user (for example via the mobile app) is valid. (In previous versions of Moodle a token was valid for 3 months.)

The setting that dictates the previous 'User created token duration' (tokenduration) can be found under the Security section.
==App's cache==
The app caches WebService requests to decrease data usage and increase the app's speed. When the app needs to get some data from Moodle, it will use a cached request as long as it isn't expired.

This cache was improved in Moodle App 3.7.0, now there are several cache times depending on the WS being called. This means that some requests will expire more often than others. Also, if the user isn't using a WiFi connection, the expiration time will also be longer to decrease the data usage. These cache times cannot be configured using a Moodle setting.
==See also==
* [https://moodle.academy/course/view.php?id=100 Moodle App Configuration]- a free self-paced course for admins on Moodle Academy.
* [[Moodle Mobile FAQ]] for other administration-related mobile app questions.
* [[Moodle app security]]
* [https://docs.moodle.org/dev/Moodle%20Mobile%20debugging%20WS%20requests dev:Moodle Mobile debugging WS requests] - a guide to helping you find and report problems with the Moodle Mobile app on your site
* [https://docs.moodle.org/dev/%20Moodle%20Mobile%20Roadmap dev: Moodle Mobile Roadmap]
* [https://docs.moodle.org/dev/Moodle%20Mobile%20release%20notes dev:Moodle Mobile release notes]
* [https://docs.moodle.org/dev/Moodle%20Mobile Moodle Mobile developer docs]
* [[Moodle Mobile availability plugin]]
* [[Mobile web services]]
[https://docs.moodle.org/fr/ Guide mobile pour administrateurs]
[https://docs.moodle.org/es/Moodle app guía para administradores]
[https://docs.moodle.org/de/Moodle App - Anleitung für Administrator/innen]

Moodle app security

2025-04-30T08:47:27Z

Jleyva: /* Warnings typically raised by static code analysis tools */

{{Mobile}}

The Moodle app is a hybrid app (uses web-technologies) developed on top of a well-tested widely used framework called "Cordova" that provides a robust container for HTML apps.

Security is very important to us, this is why we follow the Cordova and Moodle security recommendations:
* Cordova: https://cordova.apache.org/docs/en/latest/guide/appdev/security/
* Moodle: https://docs.moodle.org/dev/Security (when developing Web Services)

== How we approach security ==

* Login and authorisation
** Authorisation is done via temporary access tokens. The duration of the access tokens can be configured via Moodle settings.
** Single Sign-On (or auto-login) from the app to the site is done using a special private token (that is obtained and stored when the user log-in with the app)
** Single Sign-On (or auto-login) from the app to the site has several additional restrictions (like limiting it in only several times per hour)
** QR-Login is done using temporary tokens that require the user to be in the same network (IP address) and it is limited to 10 minutes time
** For retrieving files from the server (images or other assets), a different non-authentication token is used.

* Permissions
** The app only has access to a subset of Moodle functionalities (available through the Moodle App Service)
** Privileges escalation is not possible via the Web Services layer since all the operations are done in a non-privileged way, permissions are checked based on the currently authenticated user.
** Even if a temporary access token for an admin (or privileged user) was hijacked, it wouldn't be possible for the attacker to access to site administration functionality via the Moodle site.

Because the app is a Webservices client we recommend to enable it only under https and use the following settings to enforce security like:
* Enable only certain roles to be able to access via the app via system capabilities (avoid site administrators)
* Use Moodle security settings to reduce the expiration time of WebService access tokens (so the user has to authenticate again)
* Apart from that, the Cordova framework enforces security adding restrictions like avoiding connecting to sites running non-trusted certificates.

== What is the Moodle app security issues process? ==

* We follow the standard Moodle security process: https://docs.moodle.org/dev/Moodle_security_procedures
* There is only one relevant difference: security patches are applied immediately in the next app release or in an emergency release (depending the risks attached to the issue)

== Shared responsibility ==

* The organisation hosting the Moodle site is also responsible for providing secure access to the Moodle site, the site should be configured to use HTTPS (secure connection) so the connection is app-to-site encrypted.
* Apart from the previous, the Moodle site administrator can enable additional security measures such as enforcing end-to-end encryption for Push notifications via the site administration notification settings.

== Do you run security/penetration/pentest or static code analysis tests? ==

We do occasionally receive automated vulnerability reports of this nature. The issue with automated tools is that they usually output generic results that indicate where an exploit may be possible, which means the results often contain many false positives.

As mentioned above our app is built on top of Cordova, we rely on the Cordova framework developers to detect any native code issue.

You can do a search in the Cordova project tracker to see that several runs with the Static Code Analysis Veracode tool created issues that have been already solved, see: https://issues.apache.org/jira/issues/?jql=project%20%3D%20CB%20AND%20text%20~%20%22veracode%22%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC

Unfortunately, those Veracode runs are not publicly available because most of the time are run by external parties using the framework.

Please, note also that there are CVE codes for Cordova security issues: https://www.cvedetails.com/product/27153/Apache-Cordova.html?vendor_id=4

== Warnings typically raised by static code analysis tools ==

* '''Lack of Jailbreak Detection''' The Moodle app does not include jailbreak or root detection. This is due to the lack of official APIs from Google or Apple, and our testing of existing non-official plugins to support it showed a high rate of false positives, particularly on Android with budget devices or recent iOS updates. Notably, the app securely stores authentication tokens in the keystore/keychain, not in the session. The session token is used only for temporary content retrieval and has limited validity, ensuring that even on compromised devices, attackers cannot extract sensitive data to perform impersonation attacks.
* '''No Certificate Pinning''' The Moodle app does not support certificate pinning because it is designed to connect to any Moodle site globally (there are hundreds of thousands of sites, each one with its own URL, using Moodle), whether hosted on HTTPS, HTTP, or local networks. Additionally, the Cordova framework we rely on does not natively support certificate pinning.
* '''Lack of Encryption for Manifest Files''' The app does not include sensitive keys or certificates in publicly accessible files, eliminating the need for encryption of manifest files. The Firebase certificates available in the app’s GitHub repository are bound to the app’s fingerprint, ensuring they cannot be exploited.
* '''Static Web Service Authentication Tokens (Session Fixation)''' Web service tokens are not regenerated with each login by design. This aligns with how the Moodle Web Services API operates, allowing users to connect across multiple devices (e.g., phone and tablet) without invalidating tokens. Regenerating tokens would restrict multi-device access.
* '''Lack of Code Obfuscation''' The Moodle app code is open source. Since no keys or private data are generated during compilation, code obfuscation is not necessary.
* '''Improper Session Timeout & Logout Function''' The Moodle app follows a common approach used by most mobile apps on Android and iOS, where users are not prompted to log in repeatedly after short periods of inactivity. Mobile devices provide adequate protection through features such as automatic locking when inactive. However, Moodle site administrators have full control over how the app handles session timeouts and logout behavior. They can:
** Define how the logout function works (soft logout or complete session termination).
** Set a custom session timeout duration.
** Configure the duration of the Web Service authentication token.

These configurations can be managed through:
** '''Site administration > Mobile app authentication settings'''
** '''Site administration > Security settings'''

[[es:Seguridad de Moodle app]]

Creating mobile-friendly courses

2025-03-06T13:04:10Z

Jleyva:

Moodle app FAQ

2025-03-05T13:44:23Z

Jleyva: /* Embedded content is not working */

{{Mobile}}
==Students==
===How can I log in?===
To log in to your Moodle site with the Moodle App, you need the URL (web address) of the Moodle site that you’re trying to access. If your organisation has Search enabled, you can try searching by the name of your organisation or eLearning site.

If your organisation allows you to log in via QR code, you’ll find the QR code at the bottom of your user profile on your Moodle site. You just need to press “Scan QR code” on the app, scan the QR code on your profile and you’ll be logged in automatically.

If your organisation allows you to log in using face recognition or fingerprint, you can activate this in the App, going to User account > Preferences. You’ll need to have biometric authentication enabled in your own device’s settings.
===Who can I contact for help with the app?===
If you’re a student and need help with issues related to logging in, registering to a Moodle site or trouble connecting to the app, you should contact your school or learning organisation. For example, one of your teachers, or the person who takes care of Moodle.
Moodle HQ make the Moodle software and the Moodle app, but they don’t manage nor have access to your Moodle site or your user data.
===How can I get the Moodle app?===
You can download the Moodle App for free from [https://play.google.com/store/apps/details?id=com.moodle.moodlemobile Google Play] and the Apple [https://itunes.apple.com/app/moodle-mobile/id633359593?mt=8 App Store]. You will find it by searching “Moodle”, and the author/owner is “Moodle Pty Ltd”.
If you are unable to download the app from Google play, please visit [https://download.moodle.org/mobile/ Moodle app downloads]
===I can't get the app to work. ===
To ensure that the Moodle app functions properly, please double-check that you have correctly entered the URL address of the Moodle site you are using (please visit [https://docs.moodle.org/en/Moodle_app_FAQ#I_can%E2%80%99t_find_my_Moodle_site_in_the_app. I can’t find my Moodle site in the app]). If you are experiencing difficulties connecting to your site, please contact the person or team who takes care of Moodle in your school or learning organisation. Please note the app only works with Moodle sites that have been set up to allow it, and that are running on at least Moodle 3.5.

===I can’t find my Moodle site in the app. ===
To find your Moodle site on the app login screen, try searching for the name of your school or learning organisation.

If your school or organisation doesn’t appear in the search, you can try searching by your Moodle site URL address instead. If you don’t know the address of your Moodle site, here’s how you can find it:
# Open a web browser (like Chrome or Safari) and go to your school’s Moodle site login page.
# At the top of the page in the address bar, you'll see the URL address of your Moodle site, e.g. “campus.example.edu”. [[File:FAQ I cant find my site 1.png|alt=URL|thumb|none|''campus.example.edu'']]
# Copy the URL (don’t copy the /login nor what comes after), paste it into Your site in the app, then select Connect to your site. [[File:FAQ I cant find my site 2.png|alt=Adding an URL to the app|thumb|none|Adding an URL to the app]]
# Now you can log in to your site with your username and password.

If you tried searching by URL address and still can’t find your Moodle site, please get in touch with the person who takes care of Moodle in your school or learning organisation.
===I can’t log in with the app===
To log in to your Moodle site using the app, you first need to connect to your school’s Moodle site (view [[I can’t find my Moodle site in the app]] if you can’t find your site).

Once you’ve connected to your Moodle site, you should be able to log in with your usual username and password.

If you forgot your username or password, select the option '''Forgotten your username or password?'''. If you still have trouble logging in or can’t see any options for retrieving your username or password, please get in touch with the person who takes care of Moodle in your school or learning organisation.
===I see an error message when I try to use the app===
If you see an error message that prevents you from using the app, please get in touch with the person who takes care of Moodle in your school or learning organisation.

Some of the most common errors that your school or learning organisation will be able to fix are:
* Your token is expired or not valid.
* An error mentioning the parameter “includestealthmodules”.
* The web service function is not available.
* A message about site maintenance.

If you’re experiencing any of these errors, contact your school or learning organisation for help.
===What permissions does the app require?===
The app requires the following permissions:
* Record audio - for uploading to your Moodle site
* Read and modify the contents of your SD card - for content to be downloaded to your SD Card for offline access.
* Network access - to be able to connect with your Moodle site and check if you are connected, and if not to switch to offline mode.
* Run at startup - to receive local notifications even when the app is running in the background.
* Prevent phone from sleeping - to receive push notifications anytime.
===What are the minimum device requirements to use the Moodle app?===
Android devices: Require Android 7.0 or later. (Users with Android 5 and 6 can still use version 4.3, but they will not receive any new updates.)

iOS devices (iPhones/iPads): Require iOS 13 or later. (Please note the app was only tested on versions iOS 14 and onward.)

===I can't see my course on the app. What do I do?===
Check with your course tutor that you are correctly enrolled.
=== Why can't I upload my assignment on the app?===
If you’re experiencing any issue uploading assignment, please contact your school or learning organisation for help.
===Why can't I sometimes access the app or submit anything to it?===
This could be because of interruptions in your internet connection. Wait a while and try again. If you continue to have problems, contact your school or learning organisation for help.
===Is there a space limit on my files?===
Assignments will have a size limit which you can see, those are set by your teachers. For other space limit questions, check with your your school or learning organisation .
===When are activities completed offline synchronized?===
See [[Moodle app synchronization]].
===Why the site is asking for my username and password when an activity is opened in the browser?===
For security reasons, between auto-logins you must wait 6 minutes (this should not be a problem because most of the browsers will keep your Moodle session open).
In recent Moodle versions, the previous value can be configured in Site Administration > Mobile app authentication > Minimum time between auto-login requests

=== The Moodle app might seem slow (especially on Android devices) ===
There are several factors that could be causing this issue. It could be due to outdated or underperforming devices, or perhaps there are too many applications open, causing limited memory in your mobile device.

To troubleshoot this problem, we recommend trying the application with our demo site: https://school.moodledemo.net. Simply use the username "student" and the relevant password to access the site. If you find that the navigation and overall experience with the app are improved, then the issue may be at the server level. In this case, we suggest contacting your school or learning organisation for further assistance.

=== The Moodle app restarts/ closes / reopenes itself ===
This is likely because there are too many apps opened on your mobile device. Mobile devices have a finite amount of memory, and the device's memory manager is responsible for determining which applications to keep open and which to close.
To optimise your device's performance, we recommend closing all applications that are not currently in use. This will free up valuable memory and ensure that your device runs smoothly.
===I use LineageOS and I'm having problems using the app===
LineageOS uses a different WebView implementation not compatible vith the app. You need to install "Android System WebView" from Google Play (or via a trusted apk) and enabling it via Settings > Developer options > WebView implementation.
===H5P packages and external content embedded via iframes are not working on iOS ===
This is caused by a new feature of iOS 14 called ITP that blocks cookies for external sites embedded in the app (the H5P content is played embedded in an iframe pointing to the Moodle website) unless the user enables a setting in the app to allow those cookies.

The quick workaround is to enable the setting "Allow Cross-Website Tracking" available via the Settings app (look for the Moodle app, at the bottom) on your iPhone/iPad with iOS 14.
===I cannot reproduce audio that was recorded on browser on iOS devices (iPhones and iPads)===
This behaviour is related to this Moodle LMS bug: https://tracker.moodle.org/browse/MDL-80114

=== I don't receive calendar notifications (reminders) when using Android 12 or above ===

In order to receive calendar notifications you need to allow alarms and reminders for the Moodle app. To do this:
* Open Android Settings and go to the Moodle app settings. Another way to reach these settings is by long-clicking the Moodle app icon and pressing "App info".
* Make sure that Notifications are enabled.
* If you see a section called "Alarms & reminders", make sure it is Allowed (this setting is disabled by default in Android 14+).

==Teachers==
===How can I enable videos in my course to be downloaded?===
See the section 'Media download for offline usage' in [[Creating Moodle-app-friendly courses]].
===Which course format is it best to use?===
Topics or weekly course format is best suited to mobile devices.
===How do I make YouTube links open automatically in the app?===
Add YouTube links as a [[URL resource]].
===Why can't my students see their courses?===
If you or an administrator have correctly enrolled them in a course, they can see it in their mobile app. If they are correctly enrolled but can still not see their course, ask them to check with your Moodle site administrator.
=== I can't mark assignments in the app===
If you are experiencing problems when grading, please review that you are using the correct decimal separators (if the app interface is in English, you must use a period).
===What communications tools can I use in the app to engage with my learners?===
See [[Mobile app notifications]]. Chat, forums and messaging are all supported by the app.
===My Vimeo videos are not playing in the app===
In older versions of Moodle (pre-Moodle 3.7), it may be necessary to activate the "Allow frame embedding" admin setting. However, for those using Moodle version 3.7 or later, it is important to check whether a Proxy/Firewall/Web Server security module is setting the X-Frame-Options header in your HTTP request responses. If this is the case, it is recommended to deactivate this feature as it may cause conflicts, as Moodle already sets this header by default.

This setting is typically found in any of these configuration files .htaccess, httpd.conf or VirtualHost. To disable it, you can just use: Header always unset X-Frame-Options

You may also use Bootstrap responsive classes: https://getbootstrap.com/docs/4.0/utilities/embed/, for example, <div class="embed-responsive">
For older versions, see this forum discussion with a workaround: https://moodle.org/mod/forum/discuss.php?d=327342

If the issue is with vimeo videos on Moodle sites 3.10 or 3.11, please update the Moodle site to the latest version possible (at least 3.10.10 or 3.11.6). (See https://tracker.moodle.org/browse/MDL-74042)
===ReCaptcha doesn't work on my site===
In older versions of Moodle (pre-Moodle 3.7), it may be necessary to activate the "Allow frame embedding" admin setting. However, for those using Moodle version 3.7 or later, it is important to check whether a Proxy/Firewall/Web Server security module is setting the X-Frame-Options header in your HTTP request responses. If this is the case, it is recommended to deactivate this feature as it may cause conflicts, as Moodle already sets this header by default.
===H5P packages don't work on my site===
In older versions of Moodle (pre-Moodle 3.7), it may be necessary to activate the "Allow frame embedding" admin setting. However, for those using Moodle version 3.7 or later, it is important to check whether a Proxy/Firewall/Web Server security module is setting the X-Frame-Options header in your HTTP request responses. If this is the case, it is recommended to deactivate this feature as it may cause conflicts, as Moodle already sets this header by default.

This setting is typically found in any of these configuration files .htaccess, httpd.conf or VirtualHost. To disable it, you can just use: Header always unset X-Frame-Options

This can also happen when you are using the non-official H5P plugin (mod_hvp), in that case you will see the following message: This site is not configured properly for displaying mobile H5P content. Please contact a site administrator so they can apply the above suggested configuration changes.

'''Cookies issues'''

If your site uses HTTPS please ensure that the "Secure cookies only" (cookiesecure) setting under Site administration > HTTP security is enabled.

'''Dependency errors'''

When the following error appears "Missing dependency H5P.Editor. something X required by H5P.Editor. something Y". H5P packages need to include all the libraries (dependencies) they use so the package is self-contained. But sometimes packages might be missing at least one dependency.

In order to fix this, you could do the following:

Open Moodle’s Content Bank (from the link in the problematic H5P settings page) and upload your H5P package there, once uploaded, you will see the H5P package and an “Edit” button, click on that button so the editor opens, scroll down and click “Save”.
Now, you can replace the problematic H5P with this new one, for this, you can just include it from the Content bank by opening the activity settings page and the file picker.
=== I use a Moodle plugin but the app says it is not supported ===
You should contact the plugin developer and point him to this documentation: https://docs.moodle.org/dev/Moodle_Mobile_Remote_addons where it is explained how to add support to plugins in the Mobile app.

There is a list of Moodle plugins supported by the app here: https://moodle.org/plugins/browse.php?list=award&id=6
=== I have problems playing SCORM packages ===
This might be caused because:
* The SCORM was added using an advanced option (remote imsmanifest.xml packages or file system repository unzipped SCORMS)
* The SCORM ZIP file was created using a tool that does not create standardised ZIP files (for example, zip files containing the inverted path separator "\" will not work on Android)
Please refer to [[Moodle app SCORM player]] for additional information.
=== My quizzes or lessons are not working offline ===
You need to edit the quiz or lesson activity settings and enable the "Allow lesson/quiz to be attempted offline using the mobile app" configuration option.
=== Maths notation is not displaying correctly in the app ===
If you are having issues with MathJax, please enable the [[TeX notation filter]] also.

If you have both filters enabled, please leave MathJax above TeX so it is always processed before TeX.
=== How can I disable text selection / copy in the app? ===
You can create a remote theme and add some custom CSS rules to disable it, see https://docs.moodle.org/dev/Moodle_Mobile_Themes
=== My images, videos or audios stop working after the first time ===
Please make sure the URL you're using on the media file doesn't have any redirect (e.g. http to https), always try to use the final URL. There's a bug in the library we use to download those files, it doesn't work when downloading files with redirects. We have plans to remove that library from the app, but since then please always try to use URLs without redirects.

==Administrators==
=== What plans are available for the Moodle app? ===
There are three main plans available for the Moodle app: Free, Pro, and Premium, each offering different features and benefits. In addition to the three main plans, there is also a Branded Moodle App (BMA) option. The BMA is a custom-built app that is branded to your organization. Learn more in [[Moodle app plans]].
=== How can I have my site listed in the Moodle app site finder? ===
Please refer to our [[Moodle app guide for admins]] for instructions.
=== How can I debug errors in the app? ===
Go to the More tab and then to Settings > General. Enable "Display debug messages". This will show an explanatory message when an error occurs, alternatively, you can do a full debugging via: https://docs.moodle.org/dev/Moodle_Mobile_debugging_WS_requests

=== How can I disable features in the app? ===
Please go to ''Site administration > Mobile features > Disabled features'' and select all the features you want to disable.

To select multiple features you will have to use Ctrl (Cmd in Mac) + Click

=== How can I add custom menu items in the app? ===
You can add custom additional menu items in the "more" menu of the app, the one represented by three consecutive dots.

Please go to ''Site administration > Mobile features > Custom menu items'' and follow the instructions in [[Moodle_app_guide_for_admins#Custom_menu_items|Moodle app guide for admins]] for the correct format to use.

As a quick example:
Academy information|https://yoursite.com/mod/page/view.php?id=X |app|en|home

=== How can I customise the language strings in the app? ===

Please go to ''Site administration > Mobile features > Custom language strings'' and follow the instructions in [[Moodle_app_guide_for_admins#Custom_language_strings|Moodle app guide for admins]] for the format to use.

As a quick example:
core.user.student|Learner|en
core.user.student|Aprendiz|es

=== I can connect with my iPhone (or iPad) but not with my Android phone ===
This usually happens when the site is using https and the certificate is not correctly configured or it is using an old protocol, please use these pages to check this certificate: https://www.sslshopper.com/ssl-checker.html, https://www.geocerts.com/ssl_checker, and https://www.ssllabs.com/ssltest/analyze.html

'''The certificate of this site cannot be trusted by your device: TLS connection could not be established: javax.net.ssl.SSLHandshakeException'''

This error could be caused because in any of the certification paths there is a certificate using SHA-1. Starting Android 10 this is not allowed, more information here: https://developer.android.com/privacy-and-security/security-ssl

You could easily check the previous using https://www.ssllabs.com/ssltest/analyze.html and going to the Certification Paths -> Android section, if there is any mention to SHA-1 this could be the cause. You will need to upgrade your certificates to avoid using SHA-1.

=== My certificate is fine but I still can't connect ===
This is usually a server configuration problem caused by any of the following server configuration issues:

'''"Access to XMLHttpRequest at 'https://yoursite/webservice/rest/server.php?moodlewsrestformat=json<nowiki/>...' from origin '<nowiki>http://localhost'</nowiki> has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.'''

This is because a Proxy/Firewall/Web Server security module is removing automatically the Access-Control-Allow-Origin: * header that Moodle sets to allow Web Service requests.

It is totally secure to remove that Proxy/Firewall/Web Server rule/configuration because that header is only set by Moodle when needed.

'''"access-control-allow-origin cannot contain more than one origin".'''

iOS and Android apps do not allow the following header to contain more than one item: "Access-Control-Allow-Origin". For example, a header like this: Access-Control-Allow-Origin: *, https://mydomain.com will cause problems.

This HTTP header is not valid, according to the specification you can only specify a domain or a "*":
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin

Please, review if you have a Proxy/Firewall/Web Server adding automatically values to that HTTP header.

'''Security rules are blocking requests using the Accept-Charset header'''

Some security rules, such as OWASP ModSecurity, are blocking requests with this header that is sent by the Moodle App. In future releases of the app, this problem will be fixed. But in the meantime, you should disable it. Find more about this in MOBILE-4342.
=== My certificate is fine but the Moodle app is detecting http instead of https ===
If the Moodle app is detecting http instead of https, please revise config.php (check "wwwroot" as well as "httpswwwroot")
===After updating Moodle LMS to a recent version my users cannot login===
This only applies to sites that are configured to use log in via an embedded browser pointing to their Moodle site.
This behaviour could be related to this Moodle LMS issue: https://tracker.moodle.org/browse/MDL-81897.
There are several ways to fix this issue:
# Upgrade their Moodle site to any of the indicated version in the issue that will solve the problem
# Manually apply the patch here: https://github.com/jleyva/moodle/compare/462d5f04a8...MDL-81897-master
# Immediate workaround: Change the app authentication so it will launch in a separate browser, by going to Site admin > Mobile app authentication > Type of login (and select the option that mentions external/system browser), remember to Save Changes
We’d recommend doing 3) that will immediately address the issue that is affecting new logins.
===I can't get the app to work. What can I do?===
Assuming you have enabled mobile services on your site, please check:
# If your site uses an SSL certificate, it must be a trusted certificate, not self-signed. Please use these tools or a similar one to check that your certificate is valid: [https://www.sslshopper.com/ssl-checker.html SSL Checker], [https://www.geocerts.com/ssl_checker SSL Checker], and [https://www.ssllabs.com/ssltest/analyze.html SSL Server Test]. All the checks must be ok, including the "Certificate Chain Complete". Otherwise the app might work on iOS but not on Android.
# Make sure that the "Access-Control-Allow-Origin" header only contains one item. For example, a header like this: Access-Control-Allow-Origin: *, <nowiki>https://mydomain.com</nowiki> will cause problems.
# [[Debugging]] is disabled (in ''Site administration > Development > Debugging'')
# The ADOdb debug option is disabled if you are using the external database auth or enrolment plugin (in ''Plugins > Authentication > External database'' and in ''Plugins > Enrolment > External database'').
# SHA-1 https certificates are not supported anymore in Chrome, this means that the Android version of the app won't work for your site. If your site doesn't work in desktop Chrome or Chromium it won't work in the Android app. See https://blog.chromium.org/2014/09/gradually-sunsetting-sha-1.html for more information
# If you are using IIS check that Anonymous access is not disabled for the /webservice directory.
# If you are using a web application firewall like AWS WAF, StackPath, Barracuda, Cloudflare, Juniper, etc... try to temporary disable it to check if that's the cause. If so, you'll have to whitelist these endpoints: login/token.php, webservice/*, lib/ajax/*, media/player/vimeo/wsplayer.php and /tokenpluginfile.php
You can also add WAF rules to allow traffic by detecting the app user agent such as: (http.user_agent contains "MoodleMobile")
If you still have a problem, please post in the [https://moodle.org/mod/forum/view.php?id=7798 Moodle for mobile forum].

If the issue started after updating Moodle LMS please visit [[After updating Moodle LMS to a recent version my users cannot login]].

=== I cannot access with old users, but I can with recently created ones! ===
Please, do a "Purge all caches" via the Moodle administration settings, this will solve the problem.
===I can't view the courses tab as an administrator===
The Moodle app only displays courses you are enrolled in. If you want to view a course as an admin, you need to enrol in it.
===My Moodle site uses a SSO auth method (Shibboleth, CAS, Google OAuth, etc) and the app is not working===
See the section 'Mobile authentication' in the [[Moodle app guide for admins]] for details of how to configure it.

If configured the app is still not connecting: If your site uses an SSL certificate, it must be a trusted certificate, not self-signed. Please use this tool or a similar one to check that your certificate is fine: [https://www.geocerts.com/ssl_checker SSL Checker]. All the checks must be OK, including the "Certificate Chain Complete".

If your SSO method is unable to authenticate when using an "embedded browser" (it gives an authentication error), please check if it works with a "browser window". If it does work with the browser window then it means your SSO is performing an HTTP redirect, and these kind of redirects aren't supported by the app (the request is redirected by the browser not passing the POST parameters). Unfortunately, this is something we cannot control in the Mobile app (it can't be handled via JavaScript). For further information, see http://stackoverflow.com/questions/228225/prevent-redirection-of-xmlhttprequest and http://stackoverflow.com/questions/4168784/ajax-redirection-handling

There are only 2 possible solutions: set the authentication via a "browser window" instead of an embedded one (please notice this won't work in the Linux desktop app), or remove the redirect from the SSO auth method.
===SSO is not working with my custom auth plugin===
SSO should work in any plugin if the plugin handles correctly the $SESSION->wantsurl, this is the way SSO works when it is launched via the app:
* It launchs this URL https://yourmoodle/admin/tool/mobile/launch.php?service=local_mobile&passport=abc in the device browser
* If the user is not logged in, the browser will redirect the user to the login page
* If the auth plugin used implements correctly the handling of the wantsurl session var, once the user has logged in, the browser should redirect back to the https://yourmoodle/admin/tool/mobile/launch.php?service=local_mobile&passport=abc URL that will launch the mobile app via the custom URL protocol
Custom auth plugins may be failing in the last step,not redirecting back to tool/mobile, this will happen only if the plugin does not support correctly the $SESSION->wantsurl.

The SAML plugin works correctly but some modifications of that plugin may not work if important lines are changed.
===I am having problems requesting an airnotifier access key===
If you have registered your site but are still unable to request an access key, please register your site on the Moodle Apps Portal https://apps.moodle.com once your site is registered there, an Airnotifier access key will be automatically generated for you.
=== Push notifications are not working ===
Please check [[Mobile app notifications#Troubleshooting]]
=== How notifications icon badges are updated ===
'''Android''': Not all Android devices support icon badges so in some cases badges will never display numbers, also, depending on the device only a badge indicating that there are new notifications will be displayed when receiving a Push notification when the app is not in the foreground.

'''iOS''': The icon badge counter is only updated when the app is open and it will reflect the number of notifications pending reading or the number of message senders that sent you a message you have not read yet

In general, for iOS the icon badge displayed number should match the one displayed at the bottom of the app (or it should be the sum of the notifications and messages badges) and is not an indicator of the number of Push notifications the user has received, it acts as a reminder of pending notifications to be read that only gets updated when the user open the apps

There is an open issue to improve the behaviour on iOS, please watch MDL-73707
=== I configured 'QR code access' to automatic login, but the app still asks for credentials ===
Automatic authentication only works for Pro and Premium sites. You can see the app plans [https://moodle.com/app/ in this site].

If you're getting an error saying that the device you're using to connect isn't in the same network as the device that displays the QR code but both devices are connected to the same network, please check the section: [[#ipmismatch:_.27Client_IP_address_mismatch.27|ipmissmatch: 'Client IP address mismatch']].

=== I can log in on my Moodle site but I see a blank page or the app styles broken ===
This is usually because your Moodle site has a customised CSS.

Please try leaving empty CSS (''mobilecssurl'') on Site administration > Mobile app > Mobile appearance. If that works, please read [https://docs.moodle.org/dev/Moodle_App_Remote_Themes Moodle App Remote Themes] and create a new CSS file using the variables mentioned there

===The Moodle app does not connect to MoodleBox (or other internal self-hosted systems)===
You will need to disable SSL to make the app works, please see this forum discussion for more information: https://moodle.org/mod/forum/discuss.php?d=424353#p1739474
===I think I found a bug with the app. Where can I report it?===
# Log in to the [https://tracker.moodle.org/browse/MOBILE Moodle Mobile tracker] (you'll need to [http://tracker.moodle.org/secure/Signup%21default.jspa create a tracker account] if you've not done so previously)
# Check whether the issue has already been reported by doing a [https://tracker.moodle.org/issues/?jql=project%20%3D%20MOBILE search]
# If not, report the bug by clicking the 'Create Issue' link at the top right of the page, selecting 'Moodle app' as the project
# Add a detailed description providing as much information as possible (Moodle version, app version, device model and operating system, etc...), then click the Create button
===How can I get the app in my language?===
[[File:setting the app lang.png|thumb|100px|Setting your language]]
The Moodle app automatically detects your mobile's language and displays in the same language (if the translation exists). Otherwise, you can set the app language in App settings > General.

See also a post explaining how multi-lang works in the Moodle app: [https://moodle.org/mod/forum/discuss.php?d=453445#p1825637 Re: Language selector missing in Moodle app]

If the Moodle app is not yet available in your language, please contribute a translation! See [https://docs.moodle.org/dev/Translating%20Moodle%20Mobile Translating Moodle Mobile] for details of what to do.

=== Changes made to a Moodle site URL can cause logged-in users’ data to fail when synchronising. ===
We recommend that administrators manually log out all users after a site rename. If your site URL changes and have site users that are using the mobile Moodle App we suggest the following:
* For users that have not yet logged in - we recommend sending them the new URL
* For users already using the mobile Moodle App and potentially logged in request them to:
** log out of the mobile Moodle App,
** delete the old site, and
** log in using the new URL
Logged in Moodle users can continue working with the previous URL (with cached information) but they will not be able to synchronise the new information (therefore not receiving new information from their teachers, and teachers not receiving data or submissions from those students).
* To avoid the risk of data not synchronising, we recommend the site administrator logs out all app users, by manually deleting their tokens:
** Go to Site administration
** Click Server
** Click Web services
** Click Manage tokens
** Delete the tokens
Take into account that you still need to request your users to log in using the new URL.

=== Embedded content is not working ===

This could be caused because your site is using a Content-Security-Policy that is preventing the app from embedding content.

You can easily detect this when an error like this is displayed (javascript console): Refused to load URL because it does not appear in the frame-ancestors directive of the Content Security Policy.

If that's the case, you'd need to add the following elements: http://localhost moodleappfs://localhost at the end of the "Content-Security-Policy" HTTP header:

An example of a CSP allowing embedding Vimeo videos in the site and content in the app:
Content-Security-Policy: frame-ancestors 'self' https://*.vimeocdn.com https://*.vimeows.com https://*.vimeo.com http://localhost moodleappfs://localhost ;

Other type of embedded content that does not work is content hosted by Microsoft tools that require session or any type of authentication, such as SharePoint content.

=== Some activities are displayed incorrectly (blank, just a vertical line, ..) on the app ===
Please visit the forum post [[https://moodle.org/mod/forum/discuss.php?d=461909#p1854918| Some lesson activities do not display at all]].

==Error messages==
=== 'Coding error: version.php file is missing for the component' ===
This error message indicates that that plugin is not correctly installed (or uninstalled) on the Moodle site you use (see [[Installing plugins]]). Please review the mod/certificate folder to check if the version.php file is missing (or has incorrect permissions) as well as purge cache too.
=== 'Can not find data record in database table external_functions' ===
This error usually happens due to a bad configuration or setting value in your Moodle site, please check:
# The user quota global setting should be an integer. For more details, see the discussion [https://moodle.org/mod/forum/discuss.php?d=320873 How to enable Moodle Mobile App for all accounts].
# The ''usermaxuploadfilesize'' should be an integer, please try to decrease the size. It can be configured in ''Site Administration > Security > Site Policies > Maximum uploaded file size''. The default value (Site upload limit) depends on the PHP configuration, you might have to change the value of ''upload_max_filesize'' and ''post_max_size'' in your ''php.ini'' file.
# The user "lang" field in the database is set to a correct value and existing language installed in the site. Some times the lang field is set via external systems to incorrect values or pointing to a language pack that was uninstalled. Please, note that to fix this you need direct access to the database and your 'user' and 'course' table.
==='Cannot connect: Verify that you have typed correctly the URL and that your site uses Moodle 3.5 or later'===
Take into account that the app will only connect to Moodle LMS sites version 3.5 onward.
Please also check:
# Mobile services are enabled for the site.
# The user is entering the correct URL for the site (see FAQ above)
# For https sites, the certificate is valid (see FAQ above)
==='Invalid Moodle site version. The Moodle app only supports Moodle systems 3.5 onwards'===
The app will only connect to Moodle LMS sites version 3.5 onward (see [https://docs.moodle.org/35/en/Upgrading Upgrade to 3.5] as well as [[Upgrade overview]]).
==='We lost connection; you need to reconnect. Your token is now invalid.' on my custom version of the Moodle app ===
Please check:
# You have followed all the steps listed in [https://docs.moodle.org/dev/Moodle%20Mobile%20Developing%20a%20plugin%20tutorial Moodle Mobile Developing a plugin tutorial]
# You have enabled the [[Capabilities/moodle/webservice:createtoken|moodle/webservice:createtoken]] for the authenticated user
==='No permission to create web service token for the service local_mobile' when attempting to log in (any user that it is not an admin)===
Please check you have enabled the moodle/webservice:createtoken for the authenticated user or any global role you want to allow to use the mobile app
==='No permission to create web service token for the service local_mobile' when attempting to log in as an admin===
You need to create a token for the admin account (only) as follows:
# Go to ''Site administration > Plugins > Web services > Manage tokens''
# Click Add
# Enter the admin username and select 'Moodle app additional features service' (i.e. do NOT leave it as 'Moodle app web service')
# Click the 'Save changes' button.
==='Invalid response value detected' when accessing the site ===
The user quota global setting should be an integer. For more details, see the discussion [https://moodle.org/mod/forum/discuss.php?d=320873 How to enable Moodle Mobile App for all accounts].
=== ' Invalid response value detected: Invalid external api response: the value is "", the server was expecting "raw" type" ===
This usually happens when there is a field with value NULL in a table in the database that should not be there. This may happen if your Moodle has been upgraded over many years and the database schema is broken.

To fix it, you can do the following:
* Detect the field that is causing the problem (it should be indicated before the error message)
* Fix the field, for example, for the password field in the lesson table: UPDATE mdl_lesson SET password = '' WHERE password IS NULL (remember that your table prefix can be different than mdl_)
==='Invalid response value detected' when accessing My Courses or Course Overview ===
This usually happens when a course uses a language that isn't installed in the site. Please make sure that all courses use valid languages. This can be easily checked in the database, table "course", there is a column named "lang".
==='A required parameter (username) was missing'===
This may happen if your site implements HTTP redirects; the request is redirected by the browser not passing the POST parameters.

Unfortunately, this is something we cannot control in the Mobile app (it can't be handled via JavaScript). For further information, see http://stackoverflow.com/questions/228225/prevent-redirection-of-xmlhttprequest and http://stackoverflow.com/questions/4168784/ajax-redirection-handling

The solution is to change the HTTP redirect and use an HTML page with a meta tag or JavaScript redirect.
==='Cannot get course contents'===
This usually happens when the course is using a course format plugin that was uninstalled from the server or that was not properly installed.

Please, reinstall again the course format plugin.
==='Access control exception' or 'Your authentication token is invalid or has expired'===
Please double-check that 'Enable web services for mobile devices' (''enablemobilewebservice'') is actually enabled. (It might be unabled if for example you have reseted some roles.)

If this error appears as soon as you enter the username and password for a new site, then it probably means that the token expiration time is badly configured. This is how to fix it:
# Go to ''Site administration > Security > Site security settings''.
# Find the setting named ''User created token duration''.
# If the value is set to 0 or it's too low, please set it back to a valid value (the default value is 12 weeks).
# Click the 'Save changes' button.

===ipmismatch: 'Client IP address mismatch'===
This error can appear when a user opens your site in a browser while using the app. This happens if your site is behind a proxy and you're using one of these Moodle versions o higher: 3.5.11, 3.6.9, 3.7.5, 3.8.2, 3.9.0.

To fix it:
# Go to ''Site administration > Administration > Server > HTTP''.
# Find the setting named ''Ignore reverse proxies'' (reverseproxyignore).
# Enter the IP of your proxy (or range of IPs).
# Click the 'Save changes' button.
If you are still experiencing issues please try to change this setting "getremoteaddrconf" (Logged IP address source) to the different existing values.

Finally, it is possible to disable the IP restriction checks for functionality such as the QR login, to do that, go to Site administration > Mobile app > Mobile app authentication, and disable the "QR authentication same IP check" setting.
=== 'The param "includestealthmodules" is invalid' ===
Please contact your learning organisation so they upgrade to at least Moodle 3.5.3 (see [https://docs.moodle.org/35/en/Upgrading Upgrade to 3.5] as well as [[Upgrade overview]]) or they manually apply the patch listed here [[MDL-63542]].

==Older versions of the Moodle app==
We always recommend using the last version of the Moodle App but some times users are still using older versions this is the reason we are keeping this list:

=== Some users are asked to reauthenticate too often when they browse the site (Moodle App <3.9.3) ===
This can happen if the app is sending too many variables to a WebService, e.g. because a course has a large number of sections and/or activities. This error was fixed in the 3.9.3 version of the app, but if you are using an older version of the app you can increase the value of ''max_input_vars'' in ''php.ini'' to fix it in your server.

=== After upgrading to 3.9.5 some of my plugins have stopped working ===
The Moodle App 3.9.5 version came with some breaking changes for plugins, most of the existing plugins have been updated to support the new changes.
Please check the following list of plugins that should work for 3.9.5 once you have upgraded to the latest version indicated in the document: https://docs.google.com/spreadsheets/d/1E9PqcUBpp9SAfQc_zJtX5tf9GeS3UN76A85IrrB4UDw/edit#gid=0

==Any further questions?==
Please post in the [http://moodle.org/mod/forum/view.php?id=7798 Moodle for mobile forum] on moodle.org.

[[Category:FAQ]]

[[de:Moodle Mobile - FAQ]]
[[ca:Moodle Mobile FAQ]]
[[es:Moodle app FAQ]]
[[fr:Moodle pour les mobiles]]
[[ja:バイルMoodle FAQ]]

Moodle app guide for admins

2025-01-31T11:41:50Z

Jleyva: /* Analytics and stats */

{{Mobile}}
==Enable mobile services on your site==
Your site needs to have mobile access enabled so users can use the mobile app.

For sites using https, mobile access is enabled by default in new installations of Moodle 3.0 onwards.

For http sites, mobile access can be enabled by an administrator as follows:
# In ''Site administration > Mobile app > Mobile settings'' tick the 'Enable web services for mobile devices' checkbox. (For 4.0 version: In ''Site administration > Advanced features'' tick the 'Enable web services for mobile devices' checkbox
# Click the button to save changes.
If your site uses a [https://en.wikipedia.org/wiki/Transport_Layer_Security SSL certificate], it must be a trusted certificate. For security reasons the app doesn't work with self-signed certificates.

Please, verify that your certificate is valid via: https://www.geocerts.com/ssl_checker (you shouldn't see any warning).

If your site has the /login directory protected (frequently done when using the Shibboleth authentication method), you must enable access to the login/token.php script.
===Frame embedding===
If your sites uses [https://en.wikipedia.org/wiki/ReCAPTCHA reCaptcha], Vimeo videos or custom menu items (as described bellow) you must enable the admin setting "Allow frame embedding" (allowframembedding). Please, note this is not necessary since Moodle 3.7
===Is your site behind a proxy, or load balancer or complex network infrastructure?===
In that case, you may need to configure the "Ignore reserver proxies" settings in Site administration > Administration > Server > HTTP
==Register your site on the Moodle Apps Portal==
We strongly recommend you to register your site for free on the Moodle Apps portal: https://apps.moodle.com

You will be able to retrieve statistics like the number of active user devices receiving Push Notifications and upgrade to a Pro/Premium plan for enjoying exclusive features.
==Simplify user onboarding==
Upon opening the Moodle app, first-time users encounter a "Your site" field, where they have to input the URL of their Moodle site to access their courses. To ensure a smooth onboarding experience for new users, follow these steps:
# Enable the '''Site finder''' feature that allows users to find their Moodle site by name, eliminating the need to manually enter the site URL. To enable this feature, view [[Moodle app guide for admins#Have your site listed in the Moodle app site finder|Have your site listed in the Moodle app site finder]] below.
# Enable the '''QR login''' feature (view [[Moodle app guide for admins#QR Login|instructions]] below). This feature allows users to scan a QR code available on their Moodle profile to access their Moodle site directly from the app.
# For Android users and Moodle LMS 4.3 and later: Encourage users to install the Moodle app by following the '''Get the mobile app''' link at the bottom of any Moodle page (located within the "'''?'''" icon on the desktop version). When users install the app through this link, they will be automatically redirected to their site login screen, eliminating the need to manually enter the site URL.
# Alternatively, you can create a dedicated help page for the Moodle app. This help page should include a link to the Google Play version of the app and clearly indicate the site URL referrer. For example, if your Moodle site is mymoodlesite.com the link will be https://play.google.com/store/apps/details?id=com.moodle.moodlemobile&referrer=siteurl%3Dhttps%3A%2F%2Fmymoodlesite.com
Please note that options 3&4 are not compatible with Google Workspace accounts (the installation referrer will be ignored in that case).
==Have your site listed in the Moodle app site finder==
The Moodle apps site finder enables a user to easily find their Moodle site by entering the name (no need to enter the site URL)
===How can I have my site listed in the Moodle app site finder?===
Your site will be automatically listed in the site finder if:
* either your site is registered and listed with a link on [https://stats.moodle.org/sites/ Registered sites] and has over five hundred mobile users and you have been using the Moodle app for over a year
* or you have purchased a [https://moodle.com/app/ Pro or Premium Moodle app subscription].
You can arrange for your site to be listed in the site finder as follows:
* If your site is hosted by a Moodle Partner, please contact them to request for your site to be listed.
* If you have a MoodleCloud site, please log in to the Moodle Apps Portal where you will find an option to have your site listed.
Otherwise, to have your site listed in the site finder, you need to purchase a [https://moodle.com/app/ Pro or Premium Moodle app subscription] from the Moodle Apps Portal.
===I don’t want my site listed in the Moodle app site finder. How can I remove it?===
You can remove your site from the site finder as follows:
# Log in to the [https://apps.moodle.com/ Moodle Apps Portal]. (If you don't yet have an account, you can create one for free.)
# Go to ‘App customisation’ -> ‘Site Listing’ and uncheck the option ‘Visible’ then save changes.
Your site will then be immediately removed from the site finder.

Alternatively, you can remove your site from the site finder by updating your site registration:
# Log in to your Moodle site as admin and go to ‘Site administration’ -> Registration.
# Change ‘Site listing’ to either ‘Do not list my site’ or ‘Only display my site name’.
Your site will then be removed from the site finder within 24 hours.
==Mobile authentication==

===MFA===
The Moodle mobile app does not support MFA natively yet, however, you can redirect users to a browser to force the authentication process to behave exactly as Moodle LMS. You can do the previous via Site administration > Mobile authentication > Type of login and then select any of the options that mention browser.

===SSO authentication method===
If your site uses a SSO authentication method (CAS, Shibboleth, LDAP SSO, OAuth...), then select via a browser window or via an embedded browser for 'Type of login' (typeoflogin) in 'Mobile authentication' in the Site administration. (This setting is provided for older pre-Moodle 3.2 sites via the [[Moodle Mobile additional features]] plugin.)

The options 'browser window' and 'embedded browser' are very similar; the only difference is when redirecting the user to enter their credentials in the site, the site will be opened in the device's default browser (for browser window) or the site will be opened "embedded" in the mobile app (for embedded browser). The user experience is better in embedded browser, but not all the authentication plugins will work in embedded browser (for example, if JavaScript popups are required they must use the 'browser window'). The admin should check whether both options work, and if so, choose 'embedded browser'.

If you are using Google OAuth you will have to use the 'browser window' method because Google recently blocked authentication via 'embedded browsers'.

If your organisation uses a custom branded app and 'Type of login' is set to 'Via a browser window' or 'Via embedded browser', then a URL scheme (forcedurlscheme) may be set. This will result in only the custom branded app working for the site: the official Moodle Mobile app will not work.
===QR Login===
Please note that this feature requires Moodle 3.9 and is only available if you are enjoying a [https://moodle.com/app/ Pro/Premium plan].

As a site administrator, you can enable login via QR. Please go to Site administration > Mobile app > Mobile authentication and select "QR code with automatic login" in the "QR code access" setting

Once enabled, your students will be able to login in the app by scanning a QR code available on their Moodle site profile.
===Biometric Login===
This feature is only available to Pro and [https://apps.moodle.com Premium plan customers].

Biometric login allows your users to log in to your site via the Moodle App on Android and iOS devices using their fingerprint, face recognition or any other biometric option available on their mobile device. This makes the login process simpler, faster and more secure, and is specially useful if Autologout is enabled on your site.

'''Enabling biometric login for your site'''

You can enable Biometric login as an authentication method through the Moodle Apps Portal, going to App customisation > Authentication > Biometric login, and then selecting “Enable biometric login”. Your users will then be able to choose whether they want to use Biometric login or not.

For security reasons, users may be prompted to re-enter their credentials periodically. This interval is determined by the 'User created token duration' (tokenduration) security setting, which is set to a default duration of three months.

'''Setting up biometric login as a user'''

To use biometric login in the Moodle App, users must have biometric authentication enabled in their own device's settings (e.g. FaceID or TouchID for iOs users, or Fingerprints for Android users).

The first three times users log in to the app after you enable Biometric login, they will see a notification telling them that they can activate this new authentication method to access the app (provided that they have biometric authentication enabled in their device's settings).

Users can activate and deactivate their biometric login any time in the Moodle App in User account > Preferences.
===Auto logout===
From Moodle LMS 4.3 onwards, you can enhance security by enforcing automatic logout for your users when they leave or close the app, or it goes to the background.

You can even set your own custom re-authentication time, to suit your organisation's security requirements.

To activate auto logout, go to Site administration > Mobile app > Mobile authentication.

This feature is particularly effective when paired with Biometric login, since that streamlines the login process for your users.

== Customise your app theme ==
The app can also retrieve your custom styles from your Moodle site. Since the app is a HTML5 app, you can safely apply any CSS, CSS2 and CSS3 style.

Go to ''Administration > Site administration > Mobile app > Mobile appearance'' and enter in the mobilecssurl field a valid URL pointing to a CSS file containing your custom styles.

The CSS should be placed inside your Moodle installation (in your custom theme or inside a local plugin).

'''For example:''' ''https://mymoodlesite.com/theme/mytheme/style/mymobileapp.css''

Once the user is logged in the app, remote CSS files for applying your custom styles are regularly retrieved.

Notice that on the first time a user opens the app, he will see the default "orange" style. Your custom styles will be applied once the user has added a site in the app.

For further information, see the dev docs [https://docs.moodle.org/dev/Moodle%20Mobile%20Themes Moodle Mobile Themes].

If you want your own custom branding for your organization, Moodle offers the The [https://moodle.com/branded-app Branded Moodle Mobile app] service, please visit https://moodle.com/app/ for more information.
== Moodle Mobile additional features plugin for old Moodle sites ==
For old Moodle sites it is recommended to install the [[Moodle Mobile additional features]] plugin.
== Notifications ==
You might find them annoying but push notifications keeps you and your users informed and updated on everything about the app. Moodle only send useful and important notifications such as new features or service disruptions.

Enabling push notifications is easy! An administrator can enable it by connecting their Moodle site/s to our free Notifications server available (only) for registered Moodle sites.

An access key can be obtained via ''Site administration > General > Messaging > Notification settings''. Be sure the 'Mobile' is enabled and then click the link to settings, on the next page select ''Request access key''. (For Moodle site versions 3.5 and 3.6 an access key can be obtained via ''Site administration > Plugins > Message outputs > Manage message outputs''. Then by clicking the link to the Mobile settings, on the next page select ''Request access key''.)

The full guide on enabling push notifications can be found here: [[Mobile app notifications]]
== App banners ==
[[File:app banner.png|thumb|Moodle Mobile app banner]]
App banners let your users know that there is a mobile app available for the site. App banners are only displayed when accessing the site using a mobile browser.

In Moodle 3.3 onwards, app banners for Android are supported as well as for iOS.

App banners are disabled by default. They can be enabled in 'Mobile appearance' in the Site administration.

If you are using a custom mobile app, you need to provide the unique identifier for the iOS and Android app; if you are using the Moodle Mobile app, the settings may be left as default.

Please, notice the following:
* App banners for iOS devices (iPhone, iPad or iPod) are only shown when accessing the site using the Safari browser
* App banners for Android devices are only shown in very recent Chrome browser versions and when the app is not installed. Note also that Chrome uses an engagement heuristic that will display the banner only on certain conditions, like interactions with the site, the last time you interacted with it, etc. You can remove the engagement restriction check by disabling this special chrome flag: chrome://flags/#bypass-app-banner-engagement-checks. Please notice also that certain custom Android versions (such as Samsung and Huawei ones) does not always support this feature
=='Get the mobile app' link==
In Moodle 3.4 onwards, the link 'Get the mobile app' in the footer of each page on the site encourages users to make use of the mobile app.

By default, the link is https://download.moodle.org/mobile however the setting 'App download page' can be changed e.g. for sites using a branded mobile app.

If mobile services are not enabled for the site, then the 'Get the mobile app' link is not displayed.

To prevent the 'Get the mobile app' link being displayed, simply remove the URL from the 'App download page' setting and save changes.
== Configuring the app from your site ==
'''IMPORTANT''': Please notice that the type and number of features that you can customise depend on your Moodle Apps plan, you can register for free on https://apps.moodle.com to check the different plans.

In Moodle 3.3 onwards, or with the [[Moodle Mobile additional features]] plugin, settings in the Site administration enable admins to configure the app.
* In Moodle 3.3 onwards go to ''Site administration > Mobile features''
* In sites with the Moodle Mobile additional features plugin installed, go to ''Site administration > Plugins > Local plugins > Mobile additional features''
===Force log out===
Replace the Change site option to "Log out" so that users must enter their credentials on their next access. This is useful for custom mobile apps, as there is no reason for users wanting to switch to a different site.
===Disabled features===
The mobile app may be simplified by removing unwanted features. Some items may already be not available in the app because they are not enabled on your site.

Options to remove include:

* Offline use
* Blocks (Note that from '''Moodle 4.3.1''' the Global search and Search forums blocks can be removed.)
* Comments
* Ratings
* Tags
* Create new account
* Responsive menu items
* Main menu
** Site home
** My courses
** Dashboard
** Calendar
** Notifications
** Messages
** Grades
** My learning plans
** Blog
** Files
** Web page
** Help
* Course
** Blocks
** Blog
** Search
** Competencies
** Participants
** Grades
** Course completion
** Notes
** Download course (new in 3.5)
** Download courses (new in 3.5)
* User
** Blog
** Badges
** Competencies
** Course completion
** Grades
** Send message
** Add contact
** Block contact
** Add a new note
** User picture
* Files
** Private files
** Ste files
** Upload
* Modules (Each module can be disabled separately)
* Blocks (Each block available in the app can be disabled separately)

===Custom menu items===
Additional items can be added to the app main menu (the more menu), such as a link to a different grade book.

In order to do so go to "Site administration > Mobile features > Custom menu items"

Each custom menu item should have the format: item text, link URL, link-opening method and language code (optional, for displaying the item to users of the specified language only), icon (optional, the name of the icon from https://ionicons.com) separated by pipe characters.

Possible link-opening methods are:
* app - for linking to an activity supported by the app i.e. almost all activity types, as listed in [[Moodle Mobile features]].
* inappbrowser - for linking to external URLs or site functionalities not supported by the app. The link will open in a browser inside the app overlaying the complete screen.
* browser - as for inappbrowser except that the link will instead open in the device default browser outside the app.
* embedded - as for inappbrowser except that the link will instead open in an iframe in a new page in the app. (For this option you may need to enable the admin setting "Allow frame embedding" (allowframembedding)
Tip: If you add a custom menu item and save changes, then it doesn't appear in the app main menu, double check that the item is correctly formatted.

Please, note that if custom menu items have the same URL, same link-opening method, and same language only the first custom menu item will be shown.

Please, note that if the app is using a language not indicated in the previous list, the first language in the list will be used. (So if you have a custom menu item in English (en) and French (fr), and the app is using Spanish the user will still see that custom menu item in English)

If you want options tied to a language, you can append _only to the language code, for example:
en_only
es_only, will display the custom menu item only when the app language is English or Spanish.

Example of a menu item (it will display a home icon followed by Academy information linking to the URL indicated):
Academy information|https://yoursite.com/mod/page/view.php?id=X |app|en|home

===Responsive menu items===
From 3.7 onwards menu items on bottom tabs are moved to the side of the screen on big screens. Also the number of items displayed on the menu may vary:
* On small screens (usually phones) from 2 to 5 items will be displayed depending on the size of the screen.
* On big screens (usually tablets an desktop version) more than 2 items will be displayed without limit.
If '''Responsive menu items''' is selected in Disabled features items will be displayed in side of bottom anyway but 5 items will be displayed in all cases without depending on the size of the screen.
===Custom language strings ===
Words and phrases displayed in the app can be customised via the "Site administration > Mobile app features > Custom language strings" (customlangstrings) setting.

Enter each custom language string on a new line with format: string identifier, custom language string and language code, separated by pipe characters. For example:
core.user.student|Learner|en
core.user.student|Aprendiz|es
The complete list of string identifiers is listed in https://latest.apps.moodledemo.net/assets/lang/en.json

The string identifier is before the colon.

For example:

"core.user.student": "Student",

means that the string "Student" has string identifier "core.user.student".
==Analytics and stats==

===Usage statistics from your Moodle site===

To retrieve information about the Moodle app usage, site administrators and teachers can check the system, course or activity logs.

Among the log filters, there is a field called "All sources" with an option "Web Service/ws" that can be used to filter the entry logs generated by the mobile application.

You can compare the number of log entries generated by the "Web" versus "Web Service" (mobile app) to have an overall idea about how your users use the platform.

Please, notice that if you have custom "Web Services" or an installed plugin that uses Web Services, you will also see entries for them under the same filter.

If you have access to the site database, the table "external_tokens" has a "lastaccess" timestamp field that could be used to obtain active users of the app every day.

===Integration with Matomo analytics===
Note: This feature is available for [https://apps.moodle.com Premium app plans and Branded Moodle Apps]. To use this integration, you will need to have your own instance of Matomo.

Matomo is an open source web analytics tool that helps you monitor traffic to your Moodle site, including app activity.

'''Connecting to your Matomo instance in the Apps portal'''
[[File:Captura de pantalla 2023-11-14 a las 12.03.36.png|thumb|Moodle App Matomo Integration set up]]
To use Matomo to track app activity on your Moodle site, you will need to have your own instance of Matomo analytics, and to add your Moodle site as one of your measurable websites (see instructions on [https://matomo.org/faq/how-to/create-and-manage-websites/ Matomo’s website]). Then, follow these steps:
# Log in to the [https://apps.moodle.com Apps portal].
# Go to '''App customisation''' > '''Analytics''' > '''Matomo analytics'''.
# Check '''Track app activity'''.
# Add your '''Matomo URL''' - that's the URL of your Matomo instance, for example https://yoursite.matomo.cloud.
# Add the '''Website ID''' associated with your Moodle site in Matomo. To obtain this ID:
## Log in to your Matomo account.
## Go to '''Administration''' using the gear icon on the right side of the top navigation bar.
## On the left-hand panel, select '''Websites''' > '''Manage'''.
## In your list of measurables, find the Moodle site in which you want to track app activity. The '''ID''' of the measurable is the '''Website ID''' you need to enter in the apps portal.
# Click '''Save changes''' to establish the connection and start tracking app activity.
# If you'd like to stop tracking at any time, uncheck '''Track app activity''' and then save changes.

To filter Matomo data to isolate mobile app usage from Moodle site interactions, follow these steps:
[[File:Captura de pantalla 2023-11-14 a las 12.05.05.png|thumb|Moodle App Matomo referrer set-up]]
# Log in to your Matomo account.
# Click '''All visits''' at the top of the page
# Create a custom segment by applying this configuration: “Referrer URL” “is” “https://moodlemobile”
# To only see Moodle site interactions, do the following: “Referrer URL” “is not” “https://moodlemobile”

Please notice that the integration with Matomo does not work offline.

===Google Analytics for Firebase===
Only available when purchasing a [https://moodle.com/branded-app/ Branded Moodle App].

Google Analytics for Firebase is a free tool that provides valuable insights and data about how users interact with mobile apps.

Please notice that the integration with Google Analytics for Firebase does not work offline.

===Google Play and Apple App Store statistics===

If you have a custom mobile application, you can access statistics about app downloads and user engagement such as weekly active users and devices.

Google play:
# Go to Google Play console: https://play.google.com/console
# Select your app from the list.
# Navigate to specific tabs, such as "Statistics"

Apple App Store:
# Log in to App Store Connect: https://appstoreconnect.apple.com/
# Go to "App Analytics" from the dashboard.

==Web services token duration==
From Moodle 3.4 onwards, an admin can set how long a web services token created by a user (for example via the mobile app) is valid. (In previous versions of Moodle a token was valid for 3 months.)

The setting that dictates the previous 'User created token duration' (tokenduration) can be found under the Security section.
==App's cache==
The app caches WebService requests to decrease data usage and increase the app's speed. When the app needs to get some data from Moodle, it will use a cached request as long as it isn't expired.

This cache was improved in Moodle App 3.7.0, now there are several cache times depending on the WS being called. This means that some requests will expire more often than others. Also, if the user isn't using a WiFi connection, the expiration time will also be longer to decrease the data usage. These cache times cannot be configured using a Moodle setting.
==See also==
* [https://moodle.academy/course/view.php?id=100 Moodle App Configuration]- a free self-paced course for admins on Moodle Academy.
* [[Moodle Mobile FAQ]] for other administration-related mobile app questions.
* [[Moodle app security]]
* [https://docs.moodle.org/dev/Moodle%20Mobile%20debugging%20WS%20requests dev:Moodle Mobile debugging WS requests] - a guide to helping you find and report problems with the Moodle Mobile app on your site
* [https://docs.moodle.org/dev/%20Moodle%20Mobile%20Roadmap dev: Moodle Mobile Roadmap]
* [https://docs.moodle.org/dev/Moodle%20Mobile%20release%20notes dev:Moodle Mobile release notes]
* [https://docs.moodle.org/dev/Moodle%20Mobile Moodle Mobile developer docs]
* [[Moodle Mobile availability plugin]]
* [[Mobile web services]]
[https://docs.moodle.org/fr/ Guide mobile pour administrateurs]
[https://docs.moodle.org/es/Moodle app guía para administradores]
[https://docs.moodle.org/de/Moodle App - Anleitung für Administrator/innen]

Moodle app FAQ

2024-12-20T09:57:48Z

Jleyva: /* I can't get the app to work. What can I do? */

{{Mobile}}
==Students==
===How can I log in?===
To log in to your Moodle site with the Moodle App, you need the URL (web address) of the Moodle site that you’re trying to access. If your organisation has Search enabled, you can try searching by the name of your organisation or eLearning site.

If your organisation allows you to log in via QR code, you’ll find the QR code at the bottom of your user profile on your Moodle site. You just need to press “Scan QR code” on the app, scan the QR code on your profile and you’ll be logged in automatically.

If your organisation allows you to log in using face recognition or fingerprint, you can activate this in the App, going to User account > Preferences. You’ll need to have biometric authentication enabled in your own device’s settings.
===Who can I contact for help with the app?===
If you’re a student and need help with issues related to logging in, registering to a Moodle site or trouble connecting to the app, you should contact your school or learning organisation. For example, one of your teachers, or the person who takes care of Moodle.
Moodle HQ make the Moodle software and the Moodle app, but they don’t manage nor have access to your Moodle site or your user data.
===How can I get the Moodle app?===
You can download the Moodle App for free from [https://play.google.com/store/apps/details?id=com.moodle.moodlemobile Google Play] and the Apple [https://itunes.apple.com/app/moodle-mobile/id633359593?mt=8 App Store]. You will find it by searching “Moodle”, and the author/owner is “Moodle Pty Ltd”.
If you are unable to download the app from Google play, please visit [https://download.moodle.org/mobile/ Moodle app downloads]
===I can't get the app to work. ===
To ensure that the Moodle app functions properly, please double-check that you have correctly entered the URL address of the Moodle site you are using (please visit [https://docs.moodle.org/en/Moodle_app_FAQ#I_can%E2%80%99t_find_my_Moodle_site_in_the_app. I can’t find my Moodle site in the app]). If you are experiencing difficulties connecting to your site, please contact the person or team who takes care of Moodle in your school or learning organisation. Please note the app only works with Moodle sites that have been set up to allow it, and that are running on at least Moodle 3.5.

===I can’t find my Moodle site in the app. ===
To find your Moodle site on the app login screen, try searching for the name of your school or learning organisation.

If your school or organisation doesn’t appear in the search, you can try searching by your Moodle site URL address instead. If you don’t know the address of your Moodle site, here’s how you can find it:
# Open a web browser (like Chrome or Safari) and go to your school’s Moodle site login page.
# At the top of the page in the address bar, you'll see the URL address of your Moodle site, e.g. “campus.example.edu”. [[File:FAQ I cant find my site 1.png|alt=URL|thumb|none|''campus.example.edu'']]
# Copy the URL (don’t copy the /login nor what comes after), paste it into Your site in the app, then select Connect to your site. [[File:FAQ I cant find my site 2.png|alt=Adding an URL to the app|thumb|none|Adding an URL to the app]]
# Now you can log in to your site with your username and password.

If you tried searching by URL address and still can’t find your Moodle site, please get in touch with the person who takes care of Moodle in your school or learning organisation.
===I can’t log in with the app===
To log in to your Moodle site using the app, you first need to connect to your school’s Moodle site (view [[I can’t find my Moodle site in the app]] if you can’t find your site).

Once you’ve connected to your Moodle site, you should be able to log in with your usual username and password.

If you forgot your username or password, select the option '''Forgotten your username or password?'''. If you still have trouble logging in or can’t see any options for retrieving your username or password, please get in touch with the person who takes care of Moodle in your school or learning organisation.
===I see an error message when I try to use the app===
If you see an error message that prevents you from using the app, please get in touch with the person who takes care of Moodle in your school or learning organisation.

Some of the most common errors that your school or learning organisation will be able to fix are:
* Your token is expired or not valid.
* An error mentioning the parameter “includestealthmodules”.
* The web service function is not available.
* A message about site maintenance.

If you’re experiencing any of these errors, contact your school or learning organisation for help.
===What permissions does the app require?===
The app requires the following permissions:
* Record audio - for uploading to your Moodle site
* Read and modify the contents of your SD card - for content to be downloaded to your SD Card for offline access.
* Network access - to be able to connect with your Moodle site and check if you are connected, and if not to switch to offline mode.
* Run at startup - to receive local notifications even when the app is running in the background.
* Prevent phone from sleeping - to receive push notifications anytime.
===What are the minimum device requirements to use the Moodle app?===
Android devices: Require Android 7.0 or later. (Users with Android 5 and 6 can still use version 4.3, but they will not receive any new updates.)

iOS devices (iPhones/iPads): Require iOS 13 or later. (Please note the app was only tested on versions iOS 14 and onward.)

===I can't see my course on the app. What do I do?===
Check with your course tutor that you are correctly enrolled.
=== Why can't I upload my assignment on the app?===
If you’re experiencing any issue uploading assignment, please contact your school or learning organisation for help.
===Why can't I sometimes access the app or submit anything to it?===
This could be because of interruptions in your internet connection. Wait a while and try again. If you continue to have problems, contact your school or learning organisation for help.
===Is there a space limit on my files?===
Assignments will have a size limit which you can see, those are set by your teachers. For other space limit questions, check with your your school or learning organisation .
===When are activities completed offline synchronized?===
See [[Moodle app synchronization]].
===Why the site is asking for my username and password when an activity is opened in the browser?===
For security reasons, between auto-logins you must wait 6 minutes (this should not be a problem because most of the browsers will keep your Moodle session open).
In recent Moodle versions, the previous value can be configured in Site Administration > Mobile app authentication > Minimum time between auto-login requests

=== The Moodle app might seem slow (especially on Android devices) ===
There are several factors that could be causing this issue. It could be due to outdated or underperforming devices, or perhaps there are too many applications open, causing limited memory in your mobile device.

To troubleshoot this problem, we recommend trying the application with our demo site: https://school.moodledemo.net. Simply use the username "student" and the relevant password to access the site. If you find that the navigation and overall experience with the app are improved, then the issue may be at the server level. In this case, we suggest contacting your school or learning organisation for further assistance.

=== The Moodle app restarts/ closes / reopenes itself ===
This is likely because there are too many apps opened on your mobile device. Mobile devices have a finite amount of memory, and the device's memory manager is responsible for determining which applications to keep open and which to close.
To optimise your device's performance, we recommend closing all applications that are not currently in use. This will free up valuable memory and ensure that your device runs smoothly.
===I use LineageOS and I'm having problems using the app===
LineageOS uses a different WebView implementation not compatible vith the app. You need to install "Android System WebView" from Google Play (or via a trusted apk) and enabling it via Settings > Developer options > WebView implementation.
===H5P packages and external content embedded via iframes are not working on iOS ===
This is caused by a new feature of iOS 14 called ITP that blocks cookies for external sites embedded in the app (the H5P content is played embedded in an iframe pointing to the Moodle website) unless the user enables a setting in the app to allow those cookies.

The quick workaround is to enable the setting "Allow Cross-Website Tracking" available via the Settings app (look for the Moodle app, at the bottom) on your iPhone/iPad with iOS 14.
===I cannot reproduce audio that was recorded on browser on iOS devices (iPhones and iPads)===
This behaviour is related to this Moodle LMS bug: https://tracker.moodle.org/browse/MDL-80114

=== I don't receive calendar notifications (reminders) when using Android 12 or above ===

In order to receive calendar notifications you need to allow alarms and reminders for the Moodle app. To do this:
* Open Android Settings and go to the Moodle app settings. Another way to reach these settings is by long-clicking the Moodle app icon and pressing "App info".
* Make sure that Notifications are enabled.
* If you see a section called "Alarms & reminders", make sure it is Allowed (this setting is disabled by default in Android 14+).

==Teachers==
===How can I enable videos in my course to be downloaded?===
See the section 'Media download for offline usage' in [[Creating Moodle-app-friendly courses]].
===Which course format is it best to use?===
Topics or weekly course format is best suited to mobile devices.
===How do I make YouTube links open automatically in the app?===
Add YouTube links as a [[URL resource]].
===Why can't my students see their courses?===
If you or an administrator have correctly enrolled them in a course, they can see it in their mobile app. If they are correctly enrolled but can still not see their course, ask them to check with your Moodle site administrator.
=== I can't mark assignments in the app===
If you are experiencing problems when grading, please review that you are using the correct decimal separators (if the app interface is in English, you must use a period).
===What communications tools can I use in the app to engage with my learners?===
See [[Mobile app notifications]]. Chat, forums and messaging are all supported by the app.
===My Vimeo videos are not playing in the app===
In older versions of Moodle (pre-Moodle 3.7), it may be necessary to activate the "Allow frame embedding" admin setting. However, for those using Moodle version 3.7 or later, it is important to check whether a Proxy/Firewall/Web Server security module is setting the X-Frame-Options header in your HTTP request responses. If this is the case, it is recommended to deactivate this feature as it may cause conflicts, as Moodle already sets this header by default.

This setting is typically found in any of these configuration files .htaccess, httpd.conf or VirtualHost. To disable it, you can just use: Header always unset X-Frame-Options

You may also use Bootstrap responsive classes: https://getbootstrap.com/docs/4.0/utilities/embed/, for example, <div class="embed-responsive">
For older versions, see this forum discussion with a workaround: https://moodle.org/mod/forum/discuss.php?d=327342

If the issue is with vimeo videos on Moodle sites 3.10 or 3.11, please update the Moodle site to the latest version possible (at least 3.10.10 or 3.11.6). (See https://tracker.moodle.org/browse/MDL-74042)
===ReCaptcha doesn't work on my site===
In older versions of Moodle (pre-Moodle 3.7), it may be necessary to activate the "Allow frame embedding" admin setting. However, for those using Moodle version 3.7 or later, it is important to check whether a Proxy/Firewall/Web Server security module is setting the X-Frame-Options header in your HTTP request responses. If this is the case, it is recommended to deactivate this feature as it may cause conflicts, as Moodle already sets this header by default.
===H5P packages don't work on my site===
In older versions of Moodle (pre-Moodle 3.7), it may be necessary to activate the "Allow frame embedding" admin setting. However, for those using Moodle version 3.7 or later, it is important to check whether a Proxy/Firewall/Web Server security module is setting the X-Frame-Options header in your HTTP request responses. If this is the case, it is recommended to deactivate this feature as it may cause conflicts, as Moodle already sets this header by default.

This setting is typically found in any of these configuration files .htaccess, httpd.conf or VirtualHost. To disable it, you can just use: Header always unset X-Frame-Options

This can also happen when you are using the non-official H5P plugin (mod_hvp), in that case you will see the following message: This site is not configured properly for displaying mobile H5P content. Please contact a site administrator so they can apply the above suggested configuration changes.

'''Cookies issues'''

If your site uses HTTPS please ensure that the "Secure cookies only" (cookiesecure) setting under Site administration > HTTP security is enabled.

'''Dependency errors'''

When the following error appears "Missing dependency H5P.Editor. something X required by H5P.Editor. something Y". H5P packages need to include all the libraries (dependencies) they use so the package is self-contained. But sometimes packages might be missing at least one dependency.

In order to fix this, you could do the following:

Open Moodle’s Content Bank (from the link in the problematic H5P settings page) and upload your H5P package there, once uploaded, you will see the H5P package and an “Edit” button, click on that button so the editor opens, scroll down and click “Save”.
Now, you can replace the problematic H5P with this new one, for this, you can just include it from the Content bank by opening the activity settings page and the file picker.
=== I use a Moodle plugin but the app says it is not supported ===
You should contact the plugin developer and point him to this documentation: https://docs.moodle.org/dev/Moodle_Mobile_Remote_addons where it is explained how to add support to plugins in the Mobile app.

There is a list of Moodle plugins supported by the app here: https://moodle.org/plugins/browse.php?list=award&id=6
=== I have problems playing SCORM packages ===
This might be caused because:
* The SCORM was added using an advanced option (remote imsmanifest.xml packages or file system repository unzipped SCORMS)
* The SCORM ZIP file was created using a tool that does not create standardised ZIP files (for example, zip files containing the inverted path separator "\" will not work on Android)
Please refer to [[Moodle app SCORM player]] for additional information.
=== My quizzes or lessons are not working offline ===
You need to edit the quiz or lesson activity settings and enable the "Allow lesson/quiz to be attempted offline using the mobile app" configuration option.
=== Maths notation is not displaying correctly in the app ===
If you are having issues with MathJax, please enable the [[TeX notation filter]] also.

If you have both filters enabled, please leave MathJax above TeX so it is always processed before TeX.
=== How can I disable text selection / copy in the app? ===
You can create a remote theme and add some custom CSS rules to disable it, see https://docs.moodle.org/dev/Moodle_Mobile_Themes
=== My images, videos or audios stop working after the first time ===
Please make sure the URL you're using on the media file doesn't have any redirect (e.g. http to https), always try to use the final URL. There's a bug in the library we use to download those files, it doesn't work when downloading files with redirects. We have plans to remove that library from the app, but since then please always try to use URLs without redirects.

==Administrators==
=== What plans are available for the Moodle app? ===
There are three main plans available for the Moodle app: Free, Pro, and Premium, each offering different features and benefits. In addition to the three main plans, there is also a Branded Moodle App (BMA) option. The BMA is a custom-built app that is branded to your organization. Learn more in [[Moodle app plans]].
=== How can I have my site listed in the Moodle app site finder? ===
Please refer to our [[Moodle app guide for admins]] for instructions.
=== How can I debug errors in the app? ===
Go to the More tab and then to Settings > General. Enable "Display debug messages". This will show an explanatory message when an error occurs, alternatively, you can do a full debugging via: https://docs.moodle.org/dev/Moodle_Mobile_debugging_WS_requests

=== How can I disable features in the app? ===
Please go to ''Site administration > Mobile features > Disabled features'' and select all the features you want to disable.

To select multiple features you will have to use Ctrl (Cmd in Mac) + Click

=== How can I add custom menu items in the app? ===
You can add custom additional menu items in the "more" menu of the app, the one represented by three consecutive dots.

Please go to ''Site administration > Mobile features > Custom menu items'' and follow the instructions in [[Moodle_app_guide_for_admins#Custom_menu_items|Moodle app guide for admins]] for the correct format to use.

As a quick example:
Academy information|https://yoursite.com/mod/page/view.php?id=X |app|en|home

=== How can I customise the language strings in the app? ===

Please go to ''Site administration > Mobile features > Custom language strings'' and follow the instructions in [[Moodle_app_guide_for_admins#Custom_language_strings|Moodle app guide for admins]] for the format to use.

As a quick example:
core.user.student|Learner|en
core.user.student|Aprendiz|es

=== I can connect with my iPhone (or iPad) but not with my Android phone ===
This usually happens when the site is using https and the certificate is not correctly configured or it is using an old protocol, please use these pages to check this certificate: https://www.sslshopper.com/ssl-checker.html, https://www.geocerts.com/ssl_checker, and https://www.ssllabs.com/ssltest/analyze.html

'''The certificate of this site cannot be trusted by your device: TLS connection could not be established: javax.net.ssl.SSLHandshakeException'''

This error could be caused because in any of the certification paths there is a certificate using SHA-1. Starting Android 10 this is not allowed, more information here: https://developer.android.com/privacy-and-security/security-ssl

You could easily check the previous using https://www.ssllabs.com/ssltest/analyze.html and going to the Certification Paths -> Android section, if there is any mention to SHA-1 this could be the cause. You will need to upgrade your certificates to avoid using SHA-1.

=== My certificate is fine but I still can't connect ===
This is usually a server configuration problem caused by any of the following server configuration issues:

'''"Access to XMLHttpRequest at 'https://yoursite/webservice/rest/server.php?moodlewsrestformat=json<nowiki/>...' from origin '<nowiki>http://localhost'</nowiki> has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.'''

This is because a Proxy/Firewall/Web Server security module is removing automatically the Access-Control-Allow-Origin: * header that Moodle sets to allow Web Service requests.

It is totally secure to remove that Proxy/Firewall/Web Server rule/configuration because that header is only set by Moodle when needed.

'''"access-control-allow-origin cannot contain more than one origin".'''

iOS and Android apps do not allow the following header to contain more than one item: "Access-Control-Allow-Origin". For example, a header like this: Access-Control-Allow-Origin: *, https://mydomain.com will cause problems.

This HTTP header is not valid, according to the specification you can only specify a domain or a "*":
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin

Please, review if you have a Proxy/Firewall/Web Server adding automatically values to that HTTP header.

'''Security rules are blocking requests using the Accept-Charset header'''

Some security rules, such as OWASP ModSecurity, are blocking requests with this header that is sent by the Moodle App. In future releases of the app, this problem will be fixed. But in the meantime, you should disable it. Find more about this in MOBILE-4342.
=== My certificate is fine but the Moodle app is detecting http instead of https ===
If the Moodle app is detecting http instead of https, please revise config.php (check "wwwroot" as well as "httpswwwroot")
===After updating Moodle LMS to a recent version my users cannot login===
This only applies to sites that are configured to use log in via an embedded browser pointing to their Moodle site.
This behaviour could be related to this Moodle LMS issue: https://tracker.moodle.org/browse/MDL-81897.
There are several ways to fix this issue:
# Upgrade their Moodle site to any of the indicated version in the issue that will solve the problem
# Manually apply the patch here: https://github.com/jleyva/moodle/compare/462d5f04a8...MDL-81897-master
# Immediate workaround: Change the app authentication so it will launch in a separate browser, by going to Site admin > Mobile app authentication > Type of login (and select the option that mentions external/system browser), remember to Save Changes
We’d recommend doing 3) that will immediately address the issue that is affecting new logins.
===I can't get the app to work. What can I do?===
Assuming you have enabled mobile services on your site, please check:
# If your site uses an SSL certificate, it must be a trusted certificate, not self-signed. Please use these tools or a similar one to check that your certificate is valid: [https://www.sslshopper.com/ssl-checker.html SSL Checker], [https://www.geocerts.com/ssl_checker SSL Checker], and [https://www.ssllabs.com/ssltest/analyze.html SSL Server Test]. All the checks must be ok, including the "Certificate Chain Complete". Otherwise the app might work on iOS but not on Android.
# Make sure that the "Access-Control-Allow-Origin" header only contains one item. For example, a header like this: Access-Control-Allow-Origin: *, <nowiki>https://mydomain.com</nowiki> will cause problems.
# [[Debugging]] is disabled (in ''Site administration > Development > Debugging'')
# The ADOdb debug option is disabled if you are using the external database auth or enrolment plugin (in ''Plugins > Authentication > External database'' and in ''Plugins > Enrolment > External database'').
# SHA-1 https certificates are not supported anymore in Chrome, this means that the Android version of the app won't work for your site. If your site doesn't work in desktop Chrome or Chromium it won't work in the Android app. See https://blog.chromium.org/2014/09/gradually-sunsetting-sha-1.html for more information
# If you are using IIS check that Anonymous access is not disabled for the /webservice directory.
# If you are using a web application firewall like AWS WAF, StackPath, Barracuda, Cloudflare, Juniper, etc... try to temporary disable it to check if that's the cause. If so, you'll have to whitelist these endpoints: login/token.php, webservice/*, lib/ajax/*, media/player/vimeo/wsplayer.php and /tokenpluginfile.php
You can also add WAF rules to allow traffic by detecting the app user agent such as: (http.user_agent contains "MoodleMobile")
If you still have a problem, please post in the [https://moodle.org/mod/forum/view.php?id=7798 Moodle for mobile forum].

If the issue started after updating Moodle LMS please visit [[After updating Moodle LMS to a recent version my users cannot login]].

=== I cannot access with old users, but I can with recently created ones! ===
Please, do a "Purge all caches" via the Moodle administration settings, this will solve the problem.
===I can't view the courses tab as an administrator===
The Moodle app only displays courses you are enrolled in. If you want to view a course as an admin, you need to enrol in it.
===My Moodle site uses a SSO auth method (Shibboleth, CAS, Google OAuth, etc) and the app is not working===
See the section 'Mobile authentication' in the [[Moodle app guide for admins]] for details of how to configure it.

If configured the app is still not connecting: If your site uses an SSL certificate, it must be a trusted certificate, not self-signed. Please use this tool or a similar one to check that your certificate is fine: [https://www.geocerts.com/ssl_checker SSL Checker]. All the checks must be OK, including the "Certificate Chain Complete".

If your SSO method is unable to authenticate when using an "embedded browser" (it gives an authentication error), please check if it works with a "browser window". If it does work with the browser window then it means your SSO is performing an HTTP redirect, and these kind of redirects aren't supported by the app (the request is redirected by the browser not passing the POST parameters). Unfortunately, this is something we cannot control in the Mobile app (it can't be handled via JavaScript). For further information, see http://stackoverflow.com/questions/228225/prevent-redirection-of-xmlhttprequest and http://stackoverflow.com/questions/4168784/ajax-redirection-handling

There are only 2 possible solutions: set the authentication via a "browser window" instead of an embedded one (please notice this won't work in the Linux desktop app), or remove the redirect from the SSO auth method.
===SSO is not working with my custom auth plugin===
SSO should work in any plugin if the plugin handles correctly the $SESSION->wantsurl, this is the way SSO works when it is launched via the app:
* It launchs this URL https://yourmoodle/admin/tool/mobile/launch.php?service=local_mobile&passport=abc in the device browser
* If the user is not logged in, the browser will redirect the user to the login page
* If the auth plugin used implements correctly the handling of the wantsurl session var, once the user has logged in, the browser should redirect back to the https://yourmoodle/admin/tool/mobile/launch.php?service=local_mobile&passport=abc URL that will launch the mobile app via the custom URL protocol
Custom auth plugins may be failing in the last step,not redirecting back to tool/mobile, this will happen only if the plugin does not support correctly the $SESSION->wantsurl.

The SAML plugin works correctly but some modifications of that plugin may not work if important lines are changed.
===I am having problems requesting an airnotifier access key===
If you have registered your site but are still unable to request an access key, please register your site on the Moodle Apps Portal https://apps.moodle.com once your site is registered there, an Airnotifier access key will be automatically generated for you.
=== Push notifications are not working ===
Please check [[Mobile app notifications#Troubleshooting]]
=== How notifications icon badges are updated ===
'''Android''': Not all Android devices support icon badges so in some cases badges will never display numbers, also, depending on the device only a badge indicating that there are new notifications will be displayed when receiving a Push notification when the app is not in the foreground.

'''iOS''': The icon badge counter is only updated when the app is open and it will reflect the number of notifications pending reading or the number of message senders that sent you a message you have not read yet

In general, for iOS the icon badge displayed number should match the one displayed at the bottom of the app (or it should be the sum of the notifications and messages badges) and is not an indicator of the number of Push notifications the user has received, it acts as a reminder of pending notifications to be read that only gets updated when the user open the apps

There is an open issue to improve the behaviour on iOS, please watch MDL-73707
=== I configured 'QR code access' to automatic login, but the app still asks for credentials ===
Automatic authentication only works for Pro and Premium sites. You can see the app plans [https://moodle.com/app/ in this site].

If you're getting an error saying that the device you're using to connect isn't in the same network as the device that displays the QR code but both devices are connected to the same network, please check the section: [[#ipmismatch:_.27Client_IP_address_mismatch.27|ipmissmatch: 'Client IP address mismatch']].

=== I can log in on my Moodle site but I see a blank page or the app styles broken ===
This is usually because your Moodle site has a customised CSS.

Please try leaving empty CSS (''mobilecssurl'') on Site administration > Mobile app > Mobile appearance. If that works, please read [https://docs.moodle.org/dev/Moodle_App_Remote_Themes Moodle App Remote Themes] and create a new CSS file using the variables mentioned there

===The Moodle app does not connect to MoodleBox (or other internal self-hosted systems)===
You will need to disable SSL to make the app works, please see this forum discussion for more information: https://moodle.org/mod/forum/discuss.php?d=424353#p1739474
===I think I found a bug with the app. Where can I report it?===
# Log in to the [https://tracker.moodle.org/browse/MOBILE Moodle Mobile tracker] (you'll need to [http://tracker.moodle.org/secure/Signup%21default.jspa create a tracker account] if you've not done so previously)
# Check whether the issue has already been reported by doing a [https://tracker.moodle.org/issues/?jql=project%20%3D%20MOBILE search]
# If not, report the bug by clicking the 'Create Issue' link at the top right of the page, selecting 'Moodle app' as the project
# Add a detailed description providing as much information as possible (Moodle version, app version, device model and operating system, etc...), then click the Create button
===How can I get the app in my language?===
[[File:setting the app lang.png|thumb|100px|Setting your language]]
The Moodle app automatically detects your mobile's language and displays in the same language (if the translation exists). Otherwise, you can set the app language in App settings > General.

See also a post explaining how multi-lang works in the Moodle app: [https://moodle.org/mod/forum/discuss.php?d=453445#p1825637 Re: Language selector missing in Moodle app]

If the Moodle app is not yet available in your language, please contribute a translation! See [https://docs.moodle.org/dev/Translating%20Moodle%20Mobile Translating Moodle Mobile] for details of what to do.

=== Changes made to a Moodle site URL can cause logged-in users’ data to fail when synchronising. ===
We recommend that administrators manually log out all users after a site rename. If your site URL changes and have site users that are using the mobile Moodle App we suggest the following:
* For users that have not yet logged in - we recommend sending them the new URL
* For users already using the mobile Moodle App and potentially logged in request them to:
** log out of the mobile Moodle App,
** delete the old site, and
** log in using the new URL
Logged in Moodle users can continue working with the previous URL (with cached information) but they will not be able to synchronise the new information (therefore not receiving new information from their teachers, and teachers not receiving data or submissions from those students).
* To avoid the risk of data not synchronising, we recommend the site administrator logs out all app users, by manually deleting their tokens:
** Go to Site administration
** Click Server
** Click Web services
** Click Manage tokens
** Delete the tokens
Take into account that you still need to request your users to log in using the new URL.

=== Embedded content is not working ===

This could be caused because your site is using a Content-Security-Policy that is preventing the app from embedding content.

You can easily detect this when an error like this is displayed (javascript console): Refused to load URL because it does not appear in the frame-ancestors directive of the Content Security Policy.

If that's the case, you'd need to add the following elements: http://localhost moodleappfs://localhost at the end of the "Content-Security-Policy" HTTP header:

An example of a CSP allowing embedding Vimeo videos in the site and content in the app:
Content-Security-Policy: frame-ancestors 'self' https://*.vimeocdn.com https://*.vimeows.com https://*.vimeo.com http://localhost moodleappfs://localhost ;

=== Some activities are displayed incorrectly (blank, just a vertical line, ..) on the app ===
Please visit the forum post [[https://moodle.org/mod/forum/discuss.php?d=461909#p1854918| Some lesson activities do not display at all]].

==Error messages==
=== 'Coding error: version.php file is missing for the component' ===
This error message indicates that that plugin is not correctly installed (or uninstalled) on the Moodle site you use (see [[Installing plugins]]). Please review the mod/certificate folder to check if the version.php file is missing (or has incorrect permissions) as well as purge cache too.
=== 'Can not find data record in database table external_functions' ===
This error usually happens due to a bad configuration or setting value in your Moodle site, please check:
# The user quota global setting should be an integer. For more details, see the discussion [https://moodle.org/mod/forum/discuss.php?d=320873 How to enable Moodle Mobile App for all accounts].
# The ''usermaxuploadfilesize'' should be an integer, please try to decrease the size. It can be configured in ''Site Administration > Security > Site Policies > Maximum uploaded file size''. The default value (Site upload limit) depends on the PHP configuration, you might have to change the value of ''upload_max_filesize'' and ''post_max_size'' in your ''php.ini'' file.
# The user "lang" field in the database is set to a correct value and existing language installed in the site. Some times the lang field is set via external systems to incorrect values or pointing to a language pack that was uninstalled. Please, note that to fix this you need direct access to the database and your 'user' and 'course' table.
==='Cannot connect: Verify that you have typed correctly the URL and that your site uses Moodle 3.5 or later'===
Take into account that the app will only connect to Moodle LMS sites version 3.5 onward.
Please also check:
# Mobile services are enabled for the site.
# The user is entering the correct URL for the site (see FAQ above)
# For https sites, the certificate is valid (see FAQ above)
==='Invalid Moodle site version. The Moodle app only supports Moodle systems 3.5 onwards'===
The app will only connect to Moodle LMS sites version 3.5 onward (see [https://docs.moodle.org/35/en/Upgrading Upgrade to 3.5] as well as [[Upgrade overview]]).
==='We lost connection; you need to reconnect. Your token is now invalid.' on my custom version of the Moodle app ===
Please check:
# You have followed all the steps listed in [https://docs.moodle.org/dev/Moodle%20Mobile%20Developing%20a%20plugin%20tutorial Moodle Mobile Developing a plugin tutorial]
# You have enabled the [[Capabilities/moodle/webservice:createtoken|moodle/webservice:createtoken]] for the authenticated user
==='No permission to create web service token for the service local_mobile' when attempting to log in (any user that it is not an admin)===
Please check you have enabled the moodle/webservice:createtoken for the authenticated user or any global role you want to allow to use the mobile app
==='No permission to create web service token for the service local_mobile' when attempting to log in as an admin===
You need to create a token for the admin account (only) as follows:
# Go to ''Site administration > Plugins > Web services > Manage tokens''
# Click Add
# Enter the admin username and select 'Moodle app additional features service' (i.e. do NOT leave it as 'Moodle app web service')
# Click the 'Save changes' button.
==='Invalid response value detected' when accessing the site ===
The user quota global setting should be an integer. For more details, see the discussion [https://moodle.org/mod/forum/discuss.php?d=320873 How to enable Moodle Mobile App for all accounts].
=== ' Invalid response value detected: Invalid external api response: the value is "", the server was expecting "raw" type" ===
This usually happens when there is a field with value NULL in a table in the database that should not be there. This may happen if your Moodle has been upgraded over many years and the database schema is broken.

To fix it, you can do the following:
* Detect the field that is causing the problem (it should be indicated before the error message)
* Fix the field, for example, for the password field in the lesson table: UPDATE mdl_lesson SET password = '' WHERE password IS NULL (remember that your table prefix can be different than mdl_)
==='Invalid response value detected' when accessing My Courses or Course Overview ===
This usually happens when a course uses a language that isn't installed in the site. Please make sure that all courses use valid languages. This can be easily checked in the database, table "course", there is a column named "lang".
==='A required parameter (username) was missing'===
This may happen if your site implements HTTP redirects; the request is redirected by the browser not passing the POST parameters.

Unfortunately, this is something we cannot control in the Mobile app (it can't be handled via JavaScript). For further information, see http://stackoverflow.com/questions/228225/prevent-redirection-of-xmlhttprequest and http://stackoverflow.com/questions/4168784/ajax-redirection-handling

The solution is to change the HTTP redirect and use an HTML page with a meta tag or JavaScript redirect.
==='Cannot get course contents'===
This usually happens when the course is using a course format plugin that was uninstalled from the server or that was not properly installed.

Please, reinstall again the course format plugin.
==='Access control exception' or 'Your authentication token is invalid or has expired'===
If this error appears as soon as you enter the username and password for a new site, then it probably means that the token expiration time is badly configured. This is how to fix it:
# Go to ''Site administration > Security > Site security settings''.
# Find the setting named ''User created token duration''.
# If the value is set to 0 or it's too low, please set it back to a valid value (the default value is 12 weeks).
# Click the 'Save changes' button.
===ipmismatch: 'Client IP address mismatch'===
This error can appear when a user opens your site in a browser while using the app. This happens if your site is behind a proxy and you're using one of these Moodle versions o higher: 3.5.11, 3.6.9, 3.7.5, 3.8.2, 3.9.0.

To fix it:
# Go to ''Site administration > Administration > Server > HTTP''.
# Find the setting named ''Ignore reverse proxies'' (reverseproxyignore).
# Enter the IP of your proxy (or range of IPs).
# Click the 'Save changes' button.
If you are still experiencing issues please try to change this setting "getremoteaddrconf" (Logged IP address source) to the different existing values.

Finally, it is possible to disable the IP restriction checks for functionality such as the QR login, to do that, go to Site administration > Mobile app > Mobile app authentication, and disable the "QR authentication same IP check" setting.
=== 'The param "includestealthmodules" is invalid' ===
Please contact your learning organisation so they upgrade to at least Moodle 3.5.3 (see [https://docs.moodle.org/35/en/Upgrading Upgrade to 3.5] as well as [[Upgrade overview]]) or they manually apply the patch listed here [[MDL-63542]].

==Older versions of the Moodle app==
We always recommend using the last version of the Moodle App but some times users are still using older versions this is the reason we are keeping this list:

=== Some users are asked to reauthenticate too often when they browse the site (Moodle App <3.9.3) ===
This can happen if the app is sending too many variables to a WebService, e.g. because a course has a large number of sections and/or activities. This error was fixed in the 3.9.3 version of the app, but if you are using an older version of the app you can increase the value of ''max_input_vars'' in ''php.ini'' to fix it in your server.

=== After upgrading to 3.9.5 some of my plugins have stopped working ===
The Moodle App 3.9.5 version came with some breaking changes for plugins, most of the existing plugins have been updated to support the new changes.
Please check the following list of plugins that should work for 3.9.5 once you have upgraded to the latest version indicated in the document: https://docs.google.com/spreadsheets/d/1E9PqcUBpp9SAfQc_zJtX5tf9GeS3UN76A85IrrB4UDw/edit#gid=0

==Any further questions?==
Please post in the [http://moodle.org/mod/forum/view.php?id=7798 Moodle for mobile forum] on moodle.org.

[[Category:FAQ]]

[[de:Moodle Mobile - FAQ]]
[[ca:Moodle Mobile FAQ]]
[[es:Moodle app FAQ]]
[[fr:Moodle pour les mobiles]]
[[ja:バイルMoodle FAQ]]

Moodle app security

2024-12-20T09:51:06Z

Jleyva: /* Warnings typically raised by static code analysis tools */

{{Mobile}}

The Moodle app is a hybrid app (uses web-technologies) developed on top of a well-tested widely used framework called "Cordova" that provides a robust container for HTML apps.

Security is very important to us, this is why we follow the Cordova and Moodle security recommendations:
* Cordova: https://cordova.apache.org/docs/en/latest/guide/appdev/security/
* Moodle: https://docs.moodle.org/dev/Security (when developing Web Services)

== How we approach security ==

* Login and authorisation
** Authorisation is done via temporary access tokens. The duration of the access tokens can be configured via Moodle settings.
** Single Sign-On (or auto-login) from the app to the site is done using a special private token (that is obtained and stored when the user log-in with the app)
** Single Sign-On (or auto-login) from the app to the site has several additional restrictions (like limiting it in only several times per hour)
** QR-Login is done using temporary tokens that require the user to be in the same network (IP address) and it is limited to 10 minutes time
** For retrieving files from the server (images or other assets), a different non-authentication token is used.

* Permissions
** The app only has access to a subset of Moodle functionalities (available through the Moodle App Service)
** Privileges escalation is not possible via the Web Services layer since all the operations are done in a non-privileged way, permissions are checked based on the currently authenticated user.
** Even if a temporary access token for an admin (or privileged user) was hijacked, it wouldn't be possible for the attacker to access to site administration functionality via the Moodle site.

Because the app is a Webservices client we recommend to enable it only under https and use the following settings to enforce security like:
* Enable only certain roles to be able to access via the app via system capabilities (avoid site administrators)
* Use Moodle security settings to reduce the expiration time of WebService access tokens (so the user has to authenticate again)
* Apart from that, the Cordova framework enforces security adding restrictions like avoiding connecting to sites running non-trusted certificates.

== What is the Moodle app security issues process? ==

* We follow the standard Moodle security process: https://docs.moodle.org/dev/Moodle_security_procedures
* There is only one relevant difference: security patches are applied immediately in the next app release or in an emergency release (depending the risks attached to the issue)

== Shared responsibility ==

* The organisation hosting the Moodle site is also responsible for providing secure access to the Moodle site, the site should be configured to use HTTPS (secure connection) so the connection is app-to-site encrypted.
* Apart from the previous, the Moodle site administrator can enable additional security measures such as enforcing end-to-end encryption for Push notifications via the site administration notification settings.

== Do you run security/penetration/pentest or static code analysis tests? ==

We do occasionally receive automated vulnerability reports of this nature. The issue with automated tools is that they usually output generic results that indicate where an exploit may be possible, which means the results often contain many false positives.

As mentioned above our app is built on top of Cordova, we rely on the Cordova framework developers to detect any native code issue.

You can do a search in the Cordova project tracker to see that several runs with the Static Code Analysis Veracode tool created issues that have been already solved, see: https://issues.apache.org/jira/issues/?jql=project%20%3D%20CB%20AND%20text%20~%20%22veracode%22%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC

Unfortunately, those Veracode runs are not publicly available because most of the time are run by external parties using the framework.

Please, note also that there are CVE codes for Cordova security issues: https://www.cvedetails.com/product/27153/Apache-Cordova.html?vendor_id=4

== Warnings typically raised by static code analysis tools ==

* '''Lack of Jailbreak Detection''' The Moodle app does not include jailbreak or root detection. This is due to the lack of official APIs from Google or Apple, and our testing of existing non-official plugins to support it showed a high rate of false positives, particularly on Android with budget devices or recent iOS updates. Notably, the app securely stores authentication tokens in the keystore/keychain, not in the session. The session token is used only for temporary content retrieval and has limited validity, ensuring that even on compromised devices, attackers cannot extract sensitive data to perform impersonation attacks.
* '''No Certificate Pinning''' The Moodle app does not support certificate pinning because it is designed to connect to any Moodle site globally (there are hundreds of thousands of sites, each one with its own URL, using Moodle), whether hosted on HTTPS, HTTP, or local networks. Additionally, the Cordova framework we rely on does not natively support certificate pinning.
* '''Lack of Encryption for Manifest Files''' The app does not include sensitive keys or certificates in publicly accessible files, eliminating the need for encryption of manifest files. The Firebase certificates available in the app’s GitHub repository are bound to the app’s fingerprint, ensuring they cannot be exploited.
* '''Static Web Service Authentication Tokens (Session Fixation)''' Web service tokens are not regenerated with each login by design. This aligns with how the Moodle Web Services API operates, allowing users to connect across multiple devices (e.g., phone and tablet) without invalidating tokens. Regenerating tokens would restrict multi-device access.
* '''Lack of Code Obfuscation''' The Moodle app code is open source. Since no keys or private data are generated during compilation, code obfuscation is not necessary.
* '''Improper Session Timeout & Logout Function''' The Moodle app follows a common approach used by most mobile apps on Android and iOS, where users are not prompted to log in repeatedly after short periods of inactivity. Mobile devices provide adequate protection through features such as automatic locking when inactive. However, Moodle site administrators have full control over how the app handles session timeouts and logout behavior. They can:
** Define how the logout function works (soft logout or complete session termination).
** Set a custom session timeout duration.
** Configure the duration of the Web Service authentication token.

These configurations can be managed through:
** '''Site administration > Mobile app authentication settings'''
** '''Site administration > Security settings'''

----Does this fully address your requirements? Let me know if you'd like further refinements!
[[es:Seguridad de Moodle app]]

Moodle app security

2024-12-20T09:47:27Z

Jleyva: /* Warnings typically raised by static code analysis tools */

{{Mobile}}

The Moodle app is a hybrid app (uses web-technologies) developed on top of a well-tested widely used framework called "Cordova" that provides a robust container for HTML apps.

Security is very important to us, this is why we follow the Cordova and Moodle security recommendations:
* Cordova: https://cordova.apache.org/docs/en/latest/guide/appdev/security/
* Moodle: https://docs.moodle.org/dev/Security (when developing Web Services)

== How we approach security ==

* Login and authorisation
** Authorisation is done via temporary access tokens. The duration of the access tokens can be configured via Moodle settings.
** Single Sign-On (or auto-login) from the app to the site is done using a special private token (that is obtained and stored when the user log-in with the app)
** Single Sign-On (or auto-login) from the app to the site has several additional restrictions (like limiting it in only several times per hour)
** QR-Login is done using temporary tokens that require the user to be in the same network (IP address) and it is limited to 10 minutes time
** For retrieving files from the server (images or other assets), a different non-authentication token is used.

* Permissions
** The app only has access to a subset of Moodle functionalities (available through the Moodle App Service)
** Privileges escalation is not possible via the Web Services layer since all the operations are done in a non-privileged way, permissions are checked based on the currently authenticated user.
** Even if a temporary access token for an admin (or privileged user) was hijacked, it wouldn't be possible for the attacker to access to site administration functionality via the Moodle site.

Because the app is a Webservices client we recommend to enable it only under https and use the following settings to enforce security like:
* Enable only certain roles to be able to access via the app via system capabilities (avoid site administrators)
* Use Moodle security settings to reduce the expiration time of WebService access tokens (so the user has to authenticate again)
* Apart from that, the Cordova framework enforces security adding restrictions like avoiding connecting to sites running non-trusted certificates.

== What is the Moodle app security issues process? ==

* We follow the standard Moodle security process: https://docs.moodle.org/dev/Moodle_security_procedures
* There is only one relevant difference: security patches are applied immediately in the next app release or in an emergency release (depending the risks attached to the issue)

== Shared responsibility ==

* The organisation hosting the Moodle site is also responsible for providing secure access to the Moodle site, the site should be configured to use HTTPS (secure connection) so the connection is app-to-site encrypted.
* Apart from the previous, the Moodle site administrator can enable additional security measures such as enforcing end-to-end encryption for Push notifications via the site administration notification settings.

== Do you run security/penetration/pentest or static code analysis tests? ==

We do occasionally receive automated vulnerability reports of this nature. The issue with automated tools is that they usually output generic results that indicate where an exploit may be possible, which means the results often contain many false positives.

As mentioned above our app is built on top of Cordova, we rely on the Cordova framework developers to detect any native code issue.

You can do a search in the Cordova project tracker to see that several runs with the Static Code Analysis Veracode tool created issues that have been already solved, see: https://issues.apache.org/jira/issues/?jql=project%20%3D%20CB%20AND%20text%20~%20%22veracode%22%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC

Unfortunately, those Veracode runs are not publicly available because most of the time are run by external parties using the framework.

Please, note also that there are CVE codes for Cordova security issues: https://www.cvedetails.com/product/27153/Apache-Cordova.html?vendor_id=4

== Warnings typically raised by static code analysis tools ==

* '''Lack of Jailbreak Detection''' The Moodle app does not include jailbreak or root detection. This is due to the lack of official APIs from Google or Apple, and our testing of plugins showed a high rate of false positives, particularly on Android with budget devices or recent iOS updates. Notably, the app securely stores authentication tokens in the keystore/keychain, not in the session. The session token is used only for temporary content retrieval and has limited validity, ensuring that even on compromised devices, attackers cannot extract sensitive data to perform impersonation attacks.
* '''No Certificate Pinning''' The Moodle app does not support certificate pinning because it is designed to connect to any Moodle site globally, whether hosted on HTTPS, HTTP, or local networks. Additionally, the Cordova framework we rely on does not natively support certificate pinning. While plugins exist, Moodle’s backend architecture does not accommodate their use. See Cordova Security Guide for details.
* '''Lack of Encryption for Manifest Files''' The app does not include sensitive keys or certificates in publicly accessible files, eliminating the need for encryption of manifest files. The Firebase certificates available in the app’s GitHub repository are bound to the app’s fingerprint, ensuring they cannot be exploited.
* '''Static Web Service Authentication Tokens (Session Fixation)''' Web service tokens are not regenerated with each login by design. This aligns with how the Moodle Web Services API operates, allowing users to connect across multiple devices (e.g., phone and tablet) without invalidating tokens. Regenerating tokens would restrict multi-device access.
* '''Lack of Code Obfuscation''' The Moodle app code is open source. Since no keys or private data are generated during compilation, code obfuscation is not necessary.
* '''Improper Session Timeout & Logout Function''' The Moodle app follows a common approach used by most mobile apps on Android and iOS, where users are not prompted to log in repeatedly after short periods of inactivity. Mobile devices provide adequate protection through features such as automatic locking when inactive. However, Moodle site administrators have full control over how the app handles session timeouts and logout behavior. They can:
** Define how the logout function works (soft logout or complete session termination).
** Set a custom session timeout duration.
** Configure the duration of the Web Service authentication token.

These configurations can be managed through:
** '''Site administration > Mobile app authentication settings'''
** '''Site administration > Security settings'''

----Does this fully address your requirements? Let me know if you'd like further refinements!
[[es:Seguridad de Moodle app]]

Moodle app security

2024-12-20T09:37:19Z

Jleyva: /* Warnings typically raised by static code analysis tools */

{{Mobile}}

The Moodle app is a hybrid app (uses web-technologies) developed on top of a well-tested widely used framework called "Cordova" that provides a robust container for HTML apps.

Security is very important to us, this is why we follow the Cordova and Moodle security recommendations:
* Cordova: https://cordova.apache.org/docs/en/latest/guide/appdev/security/
* Moodle: https://docs.moodle.org/dev/Security (when developing Web Services)

== How we approach security ==

* Login and authorisation
** Authorisation is done via temporary access tokens. The duration of the access tokens can be configured via Moodle settings.
** Single Sign-On (or auto-login) from the app to the site is done using a special private token (that is obtained and stored when the user log-in with the app)
** Single Sign-On (or auto-login) from the app to the site has several additional restrictions (like limiting it in only several times per hour)
** QR-Login is done using temporary tokens that require the user to be in the same network (IP address) and it is limited to 10 minutes time
** For retrieving files from the server (images or other assets), a different non-authentication token is used.

* Permissions
** The app only has access to a subset of Moodle functionalities (available through the Moodle App Service)
** Privileges escalation is not possible via the Web Services layer since all the operations are done in a non-privileged way, permissions are checked based on the currently authenticated user.
** Even if a temporary access token for an admin (or privileged user) was hijacked, it wouldn't be possible for the attacker to access to site administration functionality via the Moodle site.

Because the app is a Webservices client we recommend to enable it only under https and use the following settings to enforce security like:
* Enable only certain roles to be able to access via the app via system capabilities (avoid site administrators)
* Use Moodle security settings to reduce the expiration time of WebService access tokens (so the user has to authenticate again)
* Apart from that, the Cordova framework enforces security adding restrictions like avoiding connecting to sites running non-trusted certificates.

== What is the Moodle app security issues process? ==

* We follow the standard Moodle security process: https://docs.moodle.org/dev/Moodle_security_procedures
* There is only one relevant difference: security patches are applied immediately in the next app release or in an emergency release (depending the risks attached to the issue)

== Shared responsibility ==

* The organisation hosting the Moodle site is also responsible for providing secure access to the Moodle site, the site should be configured to use HTTPS (secure connection) so the connection is app-to-site encrypted.
* Apart from the previous, the Moodle site administrator can enable additional security measures such as enforcing end-to-end encryption for Push notifications via the site administration notification settings.

== Do you run security/penetration/pentest or static code analysis tests? ==

We do occasionally receive automated vulnerability reports of this nature. The issue with automated tools is that they usually output generic results that indicate where an exploit may be possible, which means the results often contain many false positives.

As mentioned above our app is built on top of Cordova, we rely on the Cordova framework developers to detect any native code issue.

You can do a search in the Cordova project tracker to see that several runs with the Static Code Analysis Veracode tool created issues that have been already solved, see: https://issues.apache.org/jira/issues/?jql=project%20%3D%20CB%20AND%20text%20~%20%22veracode%22%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC

Unfortunately, those Veracode runs are not publicly available because most of the time are run by external parties using the framework.

Please, note also that there are CVE codes for Cordova security issues: https://www.cvedetails.com/product/27153/Apache-Cordova.html?vendor_id=4

== Warnings typically raised by static code analysis tools ==

* '''Lack of Jailbreak Detection''' The Moodle app does not include jailbreak or root detection. This is due to the lack of official APIs from Google or Apple, and our testing of plugins showed a high rate of false positives, particularly on Android with budget devices or recent iOS updates. Notably, the app securely stores authentication tokens in the keystore/keychain, not in the session. The session token is used only for temporary content retrieval and has limited validity, ensuring that even on compromised devices, attackers cannot extract sensitive data to perform impersonation attacks.
* '''No Certificate Pinning''' The Moodle app does not support certificate pinning because it is designed to connect to any Moodle site globally, whether hosted on HTTPS, HTTP, or local networks. Additionally, the Cordova framework we rely on does not natively support certificate pinning. While plugins exist, Moodle’s backend architecture does not accommodate their use. See Cordova Security Guide for details.
* '''Lack of Encryption for Manifest Files''' The app does not include sensitive keys or certificates in publicly accessible files, eliminating the need for encryption of manifest files. The Firebase certificates available in the app’s GitHub repository are bound to the app’s fingerprint, ensuring they cannot be exploited.
* '''Static Web Service Authentication Tokens (Session Fixation)''' Web service tokens are not regenerated with each login by design. This aligns with how the Moodle Web Services API operates, allowing users to connect across multiple devices (e.g., phone and tablet) without invalidating tokens. Regenerating tokens would restrict multi-device access.
* '''Lack of Code Obfuscation''' The Moodle app code is open source. Since no keys or private data are generated during compilation, code obfuscation is not necessary.
* '''Improper Session Timeout & Logout Function''' The Moodle app follows a common approach used by most mobile apps on Android and iOS, where users are not prompted to log in repeatedly after short periods of inactivity. Mobile devices provide adequate protection through features such as automatic locking when inactive. However, Moodle site administrators have full control over how the app handles session timeouts and logout behavior. They can:
** Define how the logout function works (soft logout or complete session termination).
** Set a custom session timeout duration.
** Configure the duration of the Web Service authentication token. These configurations can be managed through:
** '''Site administration > Mobile app authentication settings'''
** '''Site administration > Security settings'''

----Does this fully address your requirements? Let me know if you'd like further refinements!
[[es:Seguridad de Moodle app]]

Moodle app security

2024-12-20T09:36:05Z

Jleyva:

{{Mobile}}

The Moodle app is a hybrid app (uses web-technologies) developed on top of a well-tested widely used framework called "Cordova" that provides a robust container for HTML apps.

Security is very important to us, this is why we follow the Cordova and Moodle security recommendations:
* Cordova: https://cordova.apache.org/docs/en/latest/guide/appdev/security/
* Moodle: https://docs.moodle.org/dev/Security (when developing Web Services)

== How we approach security ==

* Login and authorisation
** Authorisation is done via temporary access tokens. The duration of the access tokens can be configured via Moodle settings.
** Single Sign-On (or auto-login) from the app to the site is done using a special private token (that is obtained and stored when the user log-in with the app)
** Single Sign-On (or auto-login) from the app to the site has several additional restrictions (like limiting it in only several times per hour)
** QR-Login is done using temporary tokens that require the user to be in the same network (IP address) and it is limited to 10 minutes time
** For retrieving files from the server (images or other assets), a different non-authentication token is used.

* Permissions
** The app only has access to a subset of Moodle functionalities (available through the Moodle App Service)
** Privileges escalation is not possible via the Web Services layer since all the operations are done in a non-privileged way, permissions are checked based on the currently authenticated user.
** Even if a temporary access token for an admin (or privileged user) was hijacked, it wouldn't be possible for the attacker to access to site administration functionality via the Moodle site.

Because the app is a Webservices client we recommend to enable it only under https and use the following settings to enforce security like:
* Enable only certain roles to be able to access via the app via system capabilities (avoid site administrators)
* Use Moodle security settings to reduce the expiration time of WebService access tokens (so the user has to authenticate again)
* Apart from that, the Cordova framework enforces security adding restrictions like avoiding connecting to sites running non-trusted certificates.

== What is the Moodle app security issues process? ==

* We follow the standard Moodle security process: https://docs.moodle.org/dev/Moodle_security_procedures
* There is only one relevant difference: security patches are applied immediately in the next app release or in an emergency release (depending the risks attached to the issue)

== Shared responsibility ==

* The organisation hosting the Moodle site is also responsible for providing secure access to the Moodle site, the site should be configured to use HTTPS (secure connection) so the connection is app-to-site encrypted.
* Apart from the previous, the Moodle site administrator can enable additional security measures such as enforcing end-to-end encryption for Push notifications via the site administration notification settings.

== Do you run security/penetration/pentest or static code analysis tests? ==

We do occasionally receive automated vulnerability reports of this nature. The issue with automated tools is that they usually output generic results that indicate where an exploit may be possible, which means the results often contain many false positives.

As mentioned above our app is built on top of Cordova, we rely on the Cordova framework developers to detect any native code issue.

You can do a search in the Cordova project tracker to see that several runs with the Static Code Analysis Veracode tool created issues that have been already solved, see: https://issues.apache.org/jira/issues/?jql=project%20%3D%20CB%20AND%20text%20~%20%22veracode%22%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC

Unfortunately, those Veracode runs are not publicly available because most of the time are run by external parties using the framework.

Please, note also that there are CVE codes for Cordova security issues: https://www.cvedetails.com/product/27153/Apache-Cordova.html?vendor_id=4

== '''Warnings typically raised by static code analysis tools''' ==

# '''Lack of Jailbreak Detection''' The Moodle app does not include jailbreak or root detection. This is due to the lack of official APIs from Google or Apple, and our testing of plugins showed a high rate of false positives, particularly on Android with budget devices or recent iOS updates. Notably, the app securely stores authentication tokens in the keystore/keychain, not in the session. The session token is used only for temporary content retrieval and has limited validity, ensuring that even on compromised devices, attackers cannot extract sensitive data to perform impersonation attacks.
# '''No Certificate Pinning''' The Moodle app does not support certificate pinning because it is designed to connect to any Moodle site globally, whether hosted on HTTPS, HTTP, or local networks. Additionally, the Cordova framework we rely on does not natively support certificate pinning. While plugins exist, Moodle’s backend architecture does not accommodate their use. See Cordova Security Guide for details.
# '''Lack of Encryption for Manifest Files''' The app does not include sensitive keys or certificates in publicly accessible files, eliminating the need for encryption of manifest files. The Firebase certificates available in the app’s GitHub repository are bound to the app’s fingerprint, ensuring they cannot be exploited.
# '''Static Web Service Authentication Tokens''' Web service tokens are not regenerated with each login by design. This aligns with how the Moodle Web Services API operates, allowing users to connect across multiple devices (e.g., phone and tablet) without invalidating tokens. Regenerating tokens would restrict multi-device access.
# '''Lack of Code Obfuscation''' The Moodle app code is open source. Since no keys or private data are generated during compilation, code obfuscation is not necessary.
# '''Improper Session Timeout & Logout Function''' The Moodle app follows a common approach used by most mobile apps on Android and iOS, where users are not prompted to log in repeatedly after short periods of inactivity. Mobile devices provide adequate protection through features such as automatic locking when inactive. However, Moodle site administrators have full control over how the app handles session timeouts and logout behavior. They can:
#* Define how the logout function works (soft logout or complete session termination).
#* Set a custom session timeout duration.
#* Configure the duration of the Web Service authentication token. These configurations can be managed through:
#* '''Site administration > Mobile app authentication settings'''
#* '''Site administration > Security settings'''

----Does this fully address your requirements? Let me know if you'd like further refinements!
[[es:Seguridad de Moodle app]]

Privacy in the Moodle app

2024-12-04T07:36:45Z

Jleyva:

{{Mobile}}
The Moodle Mobile App is designed with user privacy in mind, ensuring data security and control for all users. Below is a summary of how the app handles user data and privacy-related concerns:

== Communication Between the App and Moodle Site ==

The Moodle app communicates directly with the Moodle site selected by the user.

'''No data is sent to third parties''' during interactions between the user and the mobile app. All communication initiated by the app happens securely between the app and the Moodle site.

There are some scenarios that might involve third-party servers processing data when certain functionality is enabled in the Moodle site such as Push Notifications as described below.

=== Push Notifications ===

When enabled on the Moodle site, Push notifications may involve third-party servers like Moodle Airnotifier, Google (for Android) or Apple (for iOS). For example, a forum post message may travel through these servers for delivery.

To enhance privacy, we recommend enabling '''[[Moodle app notifications|end-to-end encryption for Push Notifications]]''' via Moodle site settings. This ensures data is encrypted before leaving the site and decrypted only upon reaching the user’s device.

Users can disable push notifications at anytime:
* In their device settings.
* While the app is launched for first time.
* Through the Moodle app settings.
* Directly within the Moodle site settings.

Please check Moodle Data Processing Agreement available at https://moodle.com/privacy-notice/ for additional information.

== App Permissions ==

The Moodle Mobile App uses only the '''minimum permissions''' required for its functionality.

Users are prompted to allow specific permissions only when necessary. For example: If a user wants to update their profile picture, the app will request permission to access the photo gallery at that time. Users have full control over granting or denying these permissions.

== Policies and Age Verification ==

The Moodle app supports the Moodle built-in [[Policies|policies]] functionality. If configured by the site administrators, before being able to access a Moodle site:
* Users will be shown all applicable policies, including mandatory and optional policies.
* If the site has an [[Privacy|age verification]] policy, the app will ensure users confirm their compliance before they can proceed.

This ensures that all users are fully informed and consent to the terms set by the Moodle site.

== Embedded Content from External Services ==

Teachers and content creators may embed external content, such as videos or widgets. Such embedded content may allow third parties to set cookies or track users.

'''Recommendations for privacy-friendly embedding:'''
* Use YouTube’s no-cookie feature when embedding videos.
* For Vimeo, enable the [https://help.vimeo.com/hc/en-us/articles/12426260232977-About-Player-parameters “privacy dnt” parameter] to reduce tracking.
* For other content providers, please check their documentation.

== Accessibility Features ==

On Android and iOS devices, some features like accessibility services or password auto-fill may involve data processing by Google and/or Apple services (for text processing and reading and storage).

These functionalities are part of their operating system and are not controlled by the Moodle app. We do not prevent its usage by default as they might be necessary in different types of scenarios or by certain organisations using the standard Moodle app.

Users can manage or disable these features directly through their device settings.

== Use of Firebase Framework ==

The Moodle app uses Google’s Firebase framework to enable Push Notifications.

After launching the app the Firebase framework generates a unique identifier (a random string of letters and numbers) to recognise the app for sending notifications. This identifier:
* Is used solely for basic functionality.
* Does not contain any private or personal data.

As mentioned earlier, users can opt out of Push Notifications entirely if they prefer. It will prevent the Firebase framework from generating additional ids or processing any type of information from the user or the site.

== Cookies ==

The Moodle app does not require cookies to function.

When content is embedded from external sites, such as videos or widgets, those providers may set cookies. Those cookies will not persist between app sessions, as they are not stored in the app itself, they run in an isolated environment.

== Responsibility ==

Moodle provides tools and features to implement privacy practices effectively but at the same time offers flexibility to integrate and embed content from various external providers and total freedom to the end-user to opt-in to use whatever additional features they want to enable in their devices (such as password manager, accessibility features, auto-completion, etc..)

Responsibility of the organisation:
* The organisation hosting the Moodle site must ensure they provide clear and comprehensive privacy policies to their users.
* Users must accept these policies before gaining access to the site via the Moodle site or the mobile app.
* It is the hosting organisation's duty to evaluate external content providers and ensure compliance with their local regulations.

[[es:Privacidad en la Moodle app]]

Privacy in the Moodle app

2024-12-04T07:28:13Z

Jleyva:

Privacy in the Moodle app

2024-12-04T07:25:38Z

Jleyva:

{{Mobile}}
The Moodle Mobile App is designed with user privacy in mind, ensuring data security and control for all users. Below is a summary of how the app handles user data and privacy-related concerns:

== Communication Between the App and Moodle Site ==

The Moodle app communicates directly with the Moodle site selected by the user.

'''No data is sent to third parties''' during interactions between the user and the mobile app. All communication initiated by the app happens securely between the app and the Moodle site.

There are some scenarios that might involve third-party servers processing data when certain functionality is enabled in the Moodle site such as Push Notifications as described below.

=== Push Notifications ===

When enabled on the Moodle site, Push notifications may involve third-party servers like Moodle Airnotifier, Google (for Android) or Apple (for iOS). For example, a forum post message may travel through these servers for delivery.

To enhance privacy, we recommend enabling '''[[Moodle app notifications|end-to-end encryption for Push Notifications]]''' via Moodle site settings. This ensures data is encrypted before leaving the site and decrypted only upon reaching the user’s device.

Users can disable push notifications at anytime:
* In their device settings.
* While the app is launched for first time.
* Through the Moodle app settings.
* Directly within the Moodle site settings.

Please check Moodle Data Processing Agreement available at https://moodle.com/privacy-notice/ for additional information.

== App Permissions ==

The Moodle Mobile App uses only the '''minimum permissions''' required for its functionality.

Users are prompted to allow specific permissions only when necessary. For example: If a user wants to update their profile picture, the app will request permission to access the photo gallery at that time. Users have full control over granting or denying these permissions.

== Policies and Age Verification ==

The Moodle app supports the Moodle built-in policies functionality. If configured by the site administrators, before being able to access a Moodle site:
* Users will be shown all applicable policies, including mandatory and optional policies.
* If the site has an age verification policy, the app will ensure users confirm their compliance before they can proceed.

This ensures that all users are fully informed and consent to the terms set by the Moodle site.

== Embedded Content from External Services ==

Teachers and content creators may embed external content, such as videos or widgets. Such embedded content may allow third parties to set cookies or track users.

'''Recommendations for privacy-friendly embedding:'''
* Use YouTube’s no-cookie feature when embedding videos.
* For Vimeo, enable the [https://help.vimeo.com/hc/en-us/articles/12426260232977-About-Player-parameters “privacy dnt” parameter] to reduce tracking.
* For other content providers, please check their documentation.

== Accessibility Features ==

On Android and iOS devices, some features like accessibility services or password auto-fill may involve data processing by Google and/or Apple services (for text processing and reading and storage).

These functionalities are part of their operating system and are not controlled by the Moodle app. We do not prevent its usage by default as they might be necessary in different types of scenarios or by certain organisations using the standard Moodle app.

Users can manage or disable these features directly through their device settings.

== Use of Firebase Framework ==

The Moodle app uses Google’s Firebase framework to enable Push Notifications.

After launching the app the Firebase framework generates a unique identifier (a random string of letters and numbers) to recognise the app for sending notifications. This identifier:
* Is used solely for basic functionality.
* Does not contain any private or personal data.

As mentioned earlier, users can opt out of Push Notifications entirely if they prefer. It will prevent the Firebase framework from generating additional ids or processing any type of information from the user or the site.

== Cookies ==

The Moodle app does not require cookies to function.

When content is embedded from external sites, such as videos or widgets, those providers may set cookies. Those cookies will not persist between app sessions, as they are not stored in the app itself, they run in an isolated environment.

[[es:Privacidad en la Moodle app]]

Privacy in the Moodle app

2024-12-03T14:41:41Z

Jleyva: /* Android Accessibility Features */

{{Mobile}}
The Moodle Mobile App is designed with user privacy in mind, ensuring data security and control for all users. Below is a summary of how the app handles user data and privacy-related concerns:

== Communication Between the App and Moodle Site ==

The Moodle app communicates directly with the Moodle site selected by the user.

'''No data is sent to third parties''' during interactions between the user and the mobile app. All communication initiated by the app happens securely between the app and the Moodle site.

There are some scenarios that might involve third-party servers processing data when certain functionality is enabled in the Moodle site such as Push Notifications as described below.

=== Push Notifications ===

When enabled on the Moodle site, Push notifications may involve third-party servers like Moodle Airnotifier, Google (for Android) or Apple (for iOS). For example, a forum post message may travel through these servers for delivery.

To enhance privacy, we recommend enabling '''[[Moodle app notifications|end-to-end encryption for Push Notifications]]''' via Moodle site settings. This ensures data is encrypted before leaving the site and decrypted only upon reaching the user’s device.

Users can disable push notifications at anytime:
* In their device settings.
* While the app is launched for first time.
* Through the Moodle app settings.
* Directly within the Moodle site settings.

Please check Moodle Data Processing Agreement available at https://moodle.com/privacy-notice/ for additional information.

== App Permissions ==

The Moodle Mobile App uses only the '''minimum permissions''' required for its functionality.

Users are prompted to allow specific permissions only when necessary. For example: If a user wants to update their profile picture, the app will request permission to access the photo gallery at that time. Users have full control over granting or denying these permissions.

== Embedded Content from External Services ==

Teachers and content creators may embed external content, such as videos or widgets. Such embedded content may allow third parties to set cookies or track users.

'''Recommendations for privacy-friendly embedding:'''
* Use YouTube’s no-cookie feature when embedding videos.
* For Vimeo, enable the [https://help.vimeo.com/hc/en-us/articles/12426260232977-About-Player-parameters “privacy dnt” parameter] to reduce tracking.
* For other content providers, please check their documentation.

== Accessibility Features ==

On Android and iOS devices, some features like accessibility services or password auto-fill may involve data processing by Google and/or Apple services (for text processing and reading and storage).

These functionalities are part of their operating system and are not controlled by the Moodle app. We do not prevent its usage by default as they might be necessary in different types of scenarios or by certain organisations using the standard Moodle app.

Users can manage or disable these features directly through their device settings.

== Use of Firebase Framework ==

The Moodle app uses Google’s Firebase framework to enable Push Notifications.

After launching the app the Firebase framework generates a unique identifier (a random string of letters and numbers) to recognise the app for sending notifications. This identifier:
* Is used solely for basic functionality.
* Does not contain any private or personal data.

As mentioned earlier, users can opt out of Push Notifications entirely if they prefer. It will prevent the Firebase framework from generating additional ids or processing any type of information from the user or the site.

== Cookies ==

The Moodle app does not require cookies to function.

When content is embedded from external sites, such as videos or widgets, those providers may set cookies. Those cookies will not persist between app sessions, as they are not stored in the app itself, they run in an isolated environment.

[[es:Privacidad en la Moodle app]]

Privacy in the Moodle app

2024-12-03T14:38:20Z

Jleyva:

{{Mobile}}
The Moodle Mobile App is designed with user privacy in mind, ensuring data security and control for all users. Below is a summary of how the app handles user data and privacy-related concerns:

== Communication Between the App and Moodle Site ==

The Moodle app communicates directly with the Moodle site selected by the user.

'''No data is sent to third parties''' during interactions between the user and the mobile app. All communication initiated by the app happens securely between the app and the Moodle site.

There are some scenarios that might involve third-party servers processing data when certain functionality is enabled in the Moodle site such as Push Notifications as described below.

=== Push Notifications ===

When enabled on the Moodle site, Push notifications may involve third-party servers like Moodle Airnotifier, Google (for Android) or Apple (for iOS). For example, a forum post message may travel through these servers for delivery.

To enhance privacy, we recommend enabling '''[[Moodle app notifications|end-to-end encryption for Push Notifications]]''' via Moodle site settings. This ensures data is encrypted before leaving the site and decrypted only upon reaching the user’s device.

Users can disable push notifications at anytime:
* In their device settings.
* While the app is launched for first time.
* Through the Moodle app settings.
* Directly within the Moodle site settings.

Please check Moodle Data Processing Agreement available at https://moodle.com/privacy-notice/ for additional information.

== App Permissions ==

The Moodle Mobile App uses only the '''minimum permissions''' required for its functionality.

Users are prompted to allow specific permissions only when necessary. For example: If a user wants to update their profile picture, the app will request permission to access the photo gallery at that time. Users have full control over granting or denying these permissions.

== Embedded Content from External Services ==

Teachers and content creators may embed external content, such as videos or widgets. Such embedded content may allow third parties to set cookies or track users.

'''Recommendations for privacy-friendly embedding:'''
* Use YouTube’s no-cookie feature when embedding videos.
* For Vimeo, enable the [https://help.vimeo.com/hc/en-us/articles/12426260232977-About-Player-parameters “privacy dnt” parameter] to reduce tracking.
* For other content providers, please check their documentation.

== Android Accessibility Features ==

On Android devices, some features like accessibility services or password auto-fill may involve data processing by Google services (for text processing and reading and storage).

These functionalities are part of Android's operating system and are not controlled by the Moodle app. We do not prevent its usage by default as they might be necessary in different types of scenarios.

Users can manage or disable these features directly through their Android device settings.

== Use of Firebase Framework ==

The Moodle app uses Google’s Firebase framework to enable Push Notifications.

After launching the app the Firebase framework generates a unique identifier (a random string of letters and numbers) to recognise the app for sending notifications. This identifier:
* Is used solely for basic functionality.
* Does not contain any private or personal data.

As mentioned earlier, users can opt out of Push Notifications entirely if they prefer. It will prevent the Firebase framework from generating additional ids or processing any type of information from the user or the site.

== Cookies ==

The Moodle app does not require cookies to function.

When content is embedded from external sites, such as videos or widgets, those providers may set cookies. Those cookies will not persist between app sessions, as they are not stored in the app itself, they run in an isolated environment.

Privacy in the Moodle app

2024-12-03T14:28:47Z

Jleyva: /* Use of Firebase Framework */

Privacy in the Moodle app

2024-12-03T14:27:35Z

Jleyva: /* App Permissions */