[x-license] License of MUI X Premium license shows as MUI expired package version

[sbitenc]

The problem in depth

I purchased the license recently, and now upgraded to latest package and under my license it says:

Here is more information about your MUI X Premium license.

Development use, support, and updates expiry date:
Jan 11, 2025

However, mui datagrid says MUI expired package version. Can you re-activate the license to work?

Your environment

`npx @mui/envinfo`

``` Don't forget to mention which browser you used. Output from `npx @mui/envinfo` goes here. ```

Search keywords: MUI X Premium license shows as MUI expired package version Order ID: 82010

[zannager]

@sbitenc can you please share the license key you are using in sales@mui.com? Thanks.

[sbitenc]

hi @zannager email with key sent to the sales email

[sbitenc]

Hi @michelengelen could this be looked into, it's blocking my production release?

[michelengelen]

Hey @sbitenc I did just try your key in a production environment and it does work just fine for me. Could you share with us how you registered the license key in code and what kind of setup you use? nextjs, SSR, browser and version, etc.

[sbitenc]

Hi, we use react (latest), with vite. I'm using latest brave browser (the issue is browser agnostic), and the value is injected via

import { LicenseInfo } from '@mui/x-data-grid-premium';

LicenseInfo.setLicenseKey(environmentConfig.REACT_APP_DATAGRID_PRO_KEY);

i now see that the fn is deprecated. Could this be the issue?

But we get the expired license issue when done so (we're using env to inject it)

[michelengelen]

is the component you are injecting this a client component?

[sbitenc]

i'm injecting it right into the app. I'll see how to update the deprecated call first. But here's the code i have

import { mixpanelCookiesManagement } from '@/global/components/cookies-consent-dialog/helpers/mixpanel-cookies-management';
import { removeExpiredCookiesConsent } from '@/global/components/cookies-consent-dialog/helpers/remove-expired-cookies-consent';
import { LicenseInfo } from '@mui/x-data-grid-premium';
import { environmentConfig } from '../environment-config';
import './App.css';
import { AppContent } from './app-content';
import { AppWrapper } from './app-wrapper';
import { tracker } from '@/global/helpers/tracker';

tracker.init();
removeExpiredCookiesConsent();
mixpanelCookiesManagement();

LicenseInfo.setLicenseKey(environmentConfig.REACT_APP_DATAGRID_PRO_KEY);

export const App: React.FC = () => {
  return (
    <AppWrapper>
      <AppContent />
    </AppWrapper>
  );
};

I'm switching over to @mui/x-license to see if this solves the issue

[michelengelen]

let me quickly set up a vite project and test it there... In the meantime could you try and test this approach?

I think we should add a section on vite as well ... wdyt @joserodolfofreitas ?

[sbitenc]

I've changed from import { LicenseInfo } from '@mui/x-data-grid-premium'; to import { LicenseInfo } from '@mui/x-license';

And it seems to be working. I didn't add the use client though, but it looks good on local, i'm deploying right now to see if it works on stage. But otherwise it seems to fix the issue 🤞

[joserodolfofreitas]

let me quickly set up a vite project and test it there... In the meantime could you try and test this approach?

I think we should add a section on vite as well ... wdyt @joserodolfofreitas ?

That sounds like a good idea, @michelengelen! Let's do it!

[michelengelen]

OK @sbitenc I just tested it with a production build and it works fine for me. Sry for didn't noticing you were importing LicenseInfo from the premium package. This should be marked as deprecated, is it not?

Did it work after importing from the license package?

[sbitenc]

Hi, yes that resolved the issue!

Thanks for the help!

[michelengelen]

Great that we could help! 👍🏼

[github-actions[bot]]

:warning: 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.

@sbitenc: 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.