This error occurs when the Angular/Ionic application's typescript version is older than the minimum required by the Mobiscroll. Mobiscroll will need at least typescript 2.2.0 or newer.

Solution: Update typescript version: npm install typescript@latest --save-dev 

The above errors are usually occurring when the MbscModule is not exported by the *.module.ts file. Most likely the MbscModule import is missing or is not correct  in the module file.

Solution: Make sure that the Mobiscroll is installed and the MbscModule is loaded correctly in the module.
​
​Note:  If you are using lazy loading, the MbscModule has to be imported into every module separately.

Error message:

mobiscroll is not a function

The above error is occurring when the Mobiscroll is not loaded or it is loaded in the wrong place. When the JS code runs it tries to call a mobiscroll function, but it's not finding it.

Solution: Make sure Mobiscroll is loaded correctly where you want to use it. Also, our getting started guides can be really helpful in solving this issue.

Note: This error message occurs when you try to use Mobiscroll together with jQuery or Javascript.

Contact us if something is unclear or just need a little bit more help with solving this problem.
​

This error appears in an alert when the the Mobiscroll trial doesn't have access to the internet. It usually occurs when the application is deployed to a device which is not connected. The trial needs an active internet connection to work.

Solution: Make sure to have an active internet connection during trial and your project's configuration doesn't block the Mobiscroll external API call.
​
Make sure that the  https://trial.mobiscroll.com url is white-listed in the CSP settings and in case of Cordova/Phonegap applications added to the cordova-plugin-whitelist plugin's  settings.
​
​Note:  This is not a requirement of the licensed version. You can use the non-trial products offline.

Learn more about the limitations of the trial in this article.

Here are the error messages with a range component example:

The above errors are occurring when the component was downloaded from the Download builder and the specific component wasn't included into the downloaded package.

Solution: Download resources again and update your local package. Make sure to check all the components you need in the 1. Choose Components section. Updating the local Mobiscroll package should solve the problem.

Here is how a Calendar and Date component looks like without styles:

A few things to check to solve this problem:

If there is a typo in the theme name that could cause this problem.  If you are using a custom theme, make sure that you pass the generated UniqueID name to the components. The UniqueID will be auto-generated after you named your custom theme on the Theme builder.

This might be a project related manner, but here are some tips you might check. In case of:

    - Ionic 4/ Angular cli based app  make sure that the css is loaded into the angular.json file's styles  section. Or if you use scss then check if  there is a mobiscroll scss import in the global.scss. In case of an Angular app you should check the styles.scss  file for scss import.

    - Ionic 3 make sure that the css is included into the index.html  and an Ionic_copy  section is specified in the package.json  file which describes where to copy the css form the node_modules. Or if you use scss then check if  there is a mobiscroll import in the variable.scss file.
​
    - JavaScript, jQuery, AngularJs  make sure that the css is loaded in the index.html  and there isn't any css related console errors.

This section is only valid for the licensed users because only they can use the Download Builder to specify which Mobiscroll resource would they want to use. (The trial users have all the resources included in their packages)
There might be a chance that you missed including the specific theme when you created your Mobiscroll package. 

Solution: Download resources again and update your local package. Make sure to check all the themes you need in the 2. Choose Themes section. Updating the local Mobiscroll package should solve the problem.

There are differences on the package update process in case of React, Angular 2+ / Ionic 2+ frameworks. You'll need to use the Mobiscroll CLI's config  command  with the --no-npm  flag. You should be prompted with a detailed step by step install/update guide on the download page after you downloaded your new package.
​
In case of other frameworks just simply updating the local Mobiscroll files should solve the problem.

If you are facing with this error message, here's the solution: 

It's because some of our demos use remote API for loading external data. In this case make sure to load the Jsonp module in your app's module file.

Solution: 

Note: This issue could come up when you use Angular or Ionic.

If you are trying to get/load data/events from an external link to the Event Calendar and the result is that the events are not shown in the calendar:

The problem might be that you are returning a simple JSON, while the demo URL return the values in JSONP format which is a little different.

The JSONP is used for sending JSON data without worrying about cross-domain issues and internally it uses the <script> tag instead of the XMLHttpRequest object.

Also, the JSONP request requires a different response from the server that's why it was not working for you when you returned a normal JSON data

Solution:

If you don't need to handle cross-domain requests you are good with serving plain JSON. If this is the case, in our example you just need to change the second parameter of the getJson function.
​

The actual demo on our webpage uses JSONP, so the code looks like this:
​

mobiscroll.util.getJson('yourURL', function (events) {

// ...

}, 'jsonp');

BUT you will need:
​

mobiscroll.util.getJson('yourURL', function (events) {

// ...

}, 'json'); // change this parameter from 'jsonp' if you want to use simple JSON data

Note:

Some of our demos use remote API for loading external data. For example, in case of Mobiscroll Event Calendar (in most cases) the events are loaded from an external link with the help of getJson function.

If you are using Mobiscroll components and you notice that certain things don't appear on iOS however the same things work/ show up in Chrome and Android: such as events, `marked` or `invalid` options that are associated with a given date - this is most likely the problem.

Based on conversations with our customers in many cases they try to create javascript Date objects from non-standard formats, for example: `new Date('10/29/2020')`.
​
So, the problem is that some non-standard formats will work in some browsers (e.g. Chrome), but in others (e.g. Safari) the result will be an invalid date.

Solutions:

We had an issues with our private npm registry on May 31, 2023 that has been fixed. New tokens will be needed since the private npm registry had to be rebuilt internally.

First thing’s first, the CLI: Make sure to have the Mobiscroll CLI installed. More info on it here - https://docs.mobiscroll.com/cli (make sure that you have at least Node.js 11 installed).

In case of NPM and Yarn 1: Call a mobiscroll login in your application root folder (use the email address and password of the licensed account) followed by pushing the .npmrc into your repository for CI/CD.

In case of Yarn 2+: Call mobiscroll logout followed by a mobiscroll config {framework} to install the latest version or specify the exact version like mobiscroll config {framework} --version 5.22.3. This will take care of refreshing the tokens after which you can push the .yarnrc.yml into your repository for CI/CD.

Caching and checksum issues: Since the npm packages were rebuilt, the checksum of the packages changed and in some CI/CD environments this causes problems.

If that’s the case try deleting the package-lock.json (in case of NPM) or yarn.lock (in case of Yarn) files, and run npm install / yarn install again, and push the updated files to the repository.

In some cases, when using Yarn, running yarn cache clean --all is also necessary (locally and on the server).

If cleaning the cache does not work, try setting the YARN_CHECKSUM_BEHAVIOR=update env variable on the CI/CD environment.

This error usually occurs when the Mobiscroll npm package couldn't authenticate. There can be multiple causes:

This error message usually occurs when you're using an older Node.js version. The CLI requires at least Node.js 11.

Solution: Please try to upgrade at least to Node.js 11.

This error message usually occurs when your email address contains a specific character for example '+' . The NPM registry has some issue with this character.

Solution: You can use the account's username for the login and you can also change if you want from the accounts page https://mobiscroll.com/account.

The npm packages contains the full set of Mobiscroll controls. This error usually occurs when the user has a component license and tries to install it using NPM. The error also occurs if the user doesn't have a license assigned. 

Solution: Download the package manually.

This error is thrown by the Mobiscroll NPM registry and as the error message indicates this might be either because you mistyped your login information or  your account does not exist.
​
​Solution: 

If you're behind a proxy, the installation process might not be able to send the necessary requests. The following errors indicate that there's a problem with the proxy configuration:

Solution:

In certain environments, behind a strict firewall, the config may fail with one of the following errors:

Solution:

For more details on the topic please read this article.

When running the config command, you might run into errors indicating the the config command is unable to write in the project directory:

Make sure that the project folder is writable by the user running the mobiscroll config command.

On Windows client computers, the execution of PowerShell scripts is disabled by default. When installing the Mobiscroll CLI on Windows using a PowerShell you might run into the following error:

Solution: to allow the execution of PowerShell scripts, which is needed for npm global binaries, you must set the following execution policy:

Carefully read the message displayed after executing the command and follow the instructions. Make sure you understand the implications of setting an execution policy.

A function's this  keyword behaves a little differently in JavaScript compared to other languages. The problem usually occurs with those frameworks where the this keyword is used to access the app's methods and properties. 

If the mobiscroll events are defined the following way: 

In Mobiscroll event handlers that are defined like above, this keyword points to the element where the component was initialized.
​
​Solution: The easiest way to solve this problem is to use ES6 arrow functions where this retains the value of the enclosing lexical context's this: