Evaluating user permissions with useIsAuthorized yields unexpected results (development)

[emmenko]

In my Custom Application I check the user permissions using the useIsAuthorized hook from the @commercetools-frontend/permissions package. Even though the user is supposed to have the right permissions (being an admin) the function returns false.

This behavior can be observed in development but not in production.

Additional information

The Custom Application is located in a monorepository alongside other Custom Applications.

[emmenko]

This looks like a problem with different versions of packages being installed in the monorepo, in particular related to React context.

You can check that with yarn why <package-name>, for example yarn why @commercetools-frontend/permissions.

In a monorepo, you need to make sure that packages use the same versions (if possible) especially if they rely on React context.

If different versions are installed, it can happen that a package writes the data into a React context but the other package that reads from the context uses a different React context.