[license] Expired license key

[ASMalakhovv]

Steps to reproduce

Link to live example: (required)
Exmaple
Steps:

1. Import the LicenseInfo method from @mui/x-license and call the setLicenseKey() function with mine license key.
2. Open developer tools and look for errors in the console

Current behavior

1. An error message appeared in the developer tools in the console: MUI X: Expired license key. Your annual license key to use MUI X Pro in non-production environments has expired.
   
2. An error has appeared that blocks the operation of the application, containing the following text: The above error occurred in the <ForwardRef(DesktopDateRangePicker)> component.
   

Expected behavior

An error indicating that the license key has expired in development mode, but does not block work with the component.

Context

The version of the mui -x package that I added to myself was released during the validity period of my license, based on the documentation I should be able to use it, but in practice I get a blocking error.

Your environment

npx @mui/envinfo

 Browsers:
    Chrome: Not Found
    Edge: Chromium (123.0.2420.81)
  npmPackages:
    @emotion/react:  11.11.4 
    @emotion/styled:  11.11.5 
    @mui/base:  5.0.0-beta.40 
    @mui/core-downloads-tracker:  5.15.17 
    @mui/icons-material: 5.11.9 => 5.11.9 
    @mui/material: 5.15.15 => 5.15.15 
    @mui/private-theming:  5.15.14 
    @mui/styled-engine:  5.15.14 
    @mui/styled-engine-sc: 5.11.11 => 5.11.11 
    @mui/styles: 5.11.9 => 5.11.9 
    @mui/system:  5.15.15 
    @mui/types:  7.2.14 
    @mui/utils:  5.15.14 
    @mui/x-data-grid:  6.2.0
    @mui/x-data-grid-premium: 6.2.0 => 6.2.0
    @mui/x-data-grid-pro:  6.2.0
    @mui/x-date-pickers:  7.1.1
    @mui/x-date-pickers-pro: 7.1.1 => 7.1.1
    @mui/x-license:  7.1.1
    @mui/x-license-pro: 6.0.4 => 6.0.4
    @mui/x-tree-view: 6.17.0 => 6.17.0
    @types/react: 17.0.6 => 17.0.6
    react: 17.0.2 => 17.0.2
    react-dom: 17.0.2 => 17.0.2
    styled-components: 5.3.5 => 5.3.5
    typescript: 5.2.2 => 5.2.2

Search keywords: ForwardRef, expired, license, key

[flaviendelangle]

Hi,

Your annual license is valid for one year in development, regardless of the version used.
See the following description in our pricing page:

[ASMalakhovv]

Hey @flaviendelangle

After reading the documentation and not finding a clear explanation there, I tested various versions of commercial packages after my license expired and came up with the following:

1. I can use in development indefinitely the version that I managed to install during the active period of my license.
2. I cannot update and use in development a version of a commercial package after the license has expired, even if the version was released during the time period when my license was active.
3. If I update the version of a commercial package after the license expires for a version that was released during the period when my license was active, I can only use it in production mode.

Correct me if I'm wrong about something. Thank you.

[flaviendelangle]

I can use in development indefinitely the version that I managed to install during the active period of my license.

No, if you have an annual license, you will get a warning in dev once it becomes expired, even if the version we installed during the active period of your license.
You can see the logic here.

---

Annual: valid for 1 year in any version, then you have a warning in dev for any version / no warning in prod unless you install a version released after the expiry of your license
Perpetual: valid forever, can be updated to versions released up to 1 year after the license generation, if you update after you get a warning both in dev and prod

We should clearly do a better job at documenting those with real world examples

[ASMalakhovv]

Now I understand, thanks

[LukasTy]

We're closing the issue as the problem seems to have been clarified.
If you feel that the issue is not resolved yet, feel free to reopen it. 😉

[github-actions]

⚠️ This issue has been closed. If you have a similar problem but not exactly the same, please open a new issue.
Now, if you have additional information related to this issue or things that could help future readers, feel free to leave a comment.

@ASMalakhovv: How did we do? Your experience with our support team matters to us. If you have a moment, please share your thoughts in this short Support Satisfaction survey.