Bug report: Unable to create the appcatalog

Thank you for reporting an issue. Please complete the below template to ensure we have the necessary details to assist you.

Description

Provide a short description of the issue you are facing

I am using CLI for Microsoft 365 v3.5.0 and wanted to create a new app catalog using CLI script as a part of my development work. I used this command with valid parameters m365 spo tenant appcatalog add

Steps to reproduce

Provide the steps you have taken so that we can reproduce the error open command prompt and write m365 login --authType password --userName $Username --password $Password set the admin url m365 spo set -u $Url to create the app catalog, I used this command m365 spo tenant appcatalog add --url $url --owner $owner -z 10

Expected result

Provide a description of what you expect to happen App catalog created with no error

Actual result

Provide a description of what actually happens, please provide any screenshots or error logs here

got this error (node:32788) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'length' of undefined at SpoTenantAppCatalogUrlGetCommand.getUsedCommandName (C:\Users\PandeyB\AppData\Roaming\npm\node_modules\@pnp\cli-microsoft365\dist\Command.js:47:37) at SpoTenantAppCatalogUrlGetCommand.initAction (C:\Users\PandeyB\AppData\Roaming\npm\node_modules\@pnp\cli-microsoft365\dist\Command.js:219:24) at Auth_1.default.restoreAuth.then (C:\Users\PandeyB\AppData\Roaming\npm\node_modules\@pnp\cli-microsoft365\dist\Command.js:59:18) at process._tickCallback (internal/process/next_tick.js:68:7) (node:32788) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1) (node:32788) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Environment

Provide details of the environment in which this issue was discovered, please include the operating system, shell and version of CLI used (m365 version), for example, “MacOS Catalina, bash, 2.0.0”

CLI for Microsoft 365 v3.5.0, Platform Windows Node Version V10.22.1

[waldekmastykarz]

Interesting, so perhaps something has changed in the underlying API. Let us investigate the issue and get back to you as soon as we know more, ok? Thanks again for all the details, it’s very helpful 👍

[waldekmastykarz]

We’ve just released a preview version 3.6 with the issue fixed. Once again, sorry for the trouble and thank you for reporting the issue.