React PCF creation not working

[Ionavoss]

PAC PCF INIT stopped working for React

What did I do?

I opened up Visual Studio Code, created a folder and started a new terminal.
Inside the terminal I typed:

pac pcf init -ns textarea -n textarea -t field -fw react -npm

The result:

I got the following error:

Unfortunately, an unrecoverable error has occurred in the app and it needs to be closed. The details of the exception have been recorded and will be sent to the development team if telemetry is enabled. Exception ID: b17b8e38-61f1-4b36-a9ab-8b3719222d42, Exception Type: System.ArgumentException. The diagnostic logs can be found at: c:\Users\Me\AppData\Roaming\Code\User\globalStorage\microsoft-isvexptools.powerplatform-vscode\pac\tools\logs\pac-log.txt.

I looked into the log file where it is outputting to, and the funniest thing? The ID isn't registered in any of the logs...

Tools

I use Visual Studio Code, and run the command pac returns the following:

Microsoft PowerPlatform CLI Version: 1.24.3+g95fc6ea

Alternative

I tried running it from PowerShell as well on version 1.24.3+g95fc6ea and version 1.23.3+ga05f0df and it's giving the same error and no traces are being saved.

Have you tried turning it off and on?

Yes, I rebooted multiple times, uninstalled and installed and rebooted, again and again. Nothing seems to work.

Need a working tool

It's not the first time the pac pcf init function is behaving weirdly, maybe you guys need to take a look into the stability of the PCF generation?

[BetimBeja]

@Ionavoss

The problem is the following: The value 'textarea' passed for argument is or includes a reserved word.

2023-07-04 13:51:41.9516 | INF | bolt.Session :: Product Version: 1.24.3+g95fc6ea; File Version: 1.24.3
2023-07-04 13:51:41.9936 | INF | bolt.Session :: Start new session. (sessionId: 99ee26b0-a243-4bee-8ca5-0c4e71f4fee7; operationId: bd9e2dc0468a860bb786b998fd98a859; userId: a9080f69-33f2-46e1-9180-7b31b55861dd)
2023-07-04 13:51:42.3706 | INF | bolt.cli.CommandProcessor :: StartExecutingVerb (Verbs: ["pcf","init"])
2023-07-04 13:51:42.3956 | INF | bolt.cli.Verb :: Executing 'init' verb
2023-07-04 13:51:42.4266 | INF | bolt.cli.CommandProcessor :: EndExecutingVerb (Success: False, Execution Time(ms): 46)
2023-07-04 13:51:42.4586 | FTL | bolt.Session :: The value 'textarea' passed for argument is or includes a reserved word.|EXCEPTION: System.ArgumentException: The value 'textarea' passed for argument is or includes a reserved word.
   at bolt.module.pcf.PcfInitVerb.Execute(IContext context, Command command)
   at bolt.cli.LegacyVerbExecuteFn.<>c__DisplayClass3_0.<.ctor>b__0(IContext context, Command command, CancellationToken cancellationToken)
   at bolt.cli.LegacyVerbExecutor.ExecuteAsync(IContext context, Command command, CancellationToken cancellationToken)
   at bolt.cli.Verb.<>c__DisplayClass11_0.<<RunVerbExecutorAsync>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at bolt.cli.Verb.<RunVerbExecutorAsync>d__11.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at bolt.cli.Verb.<ExecuteWithOutputAsync>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at bolt.cli.Verb.Execute(IProcessCommandContext context, Command command, Queue`1 nextCommands)
   at bolt.cli.CommandProcessor.ProcessCommands(Queue`1 commands, IVerbFactory factory)
   at bolt.cli.CommandProcessor.LaunchCommand(IReadOnlyList`1 args, UserHelpText userHelpText, Boolean isNonInteractiveModeEnabled)
   at bolt.Session.Run(ProgramArguments args)
2023-07-04 13:51:42.4656 | ERR | bolt.Session ::    at bolt.module.pcf.PcfInitVerb.Execute(IContext context, Command command)
   at bolt.cli.LegacyVerbExecuteFn.<>c__DisplayClass3_0.<.ctor>b__0(IContext context, Command command, CancellationToken cancellationToken)
   at bolt.cli.LegacyVerbExecutor.ExecuteAsync(IContext context, Command command, CancellationToken cancellationToken)
   at bolt.cli.Verb.<>c__DisplayClass11_0.<<RunVerbExecutorAsync>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at bolt.cli.Verb.<RunVerbExecutorAsync>d__11.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at bolt.cli.Verb.<ExecuteWithOutputAsync>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at bolt.cli.Verb.Execute(IProcessCommandContext context, Command command, Queue`1 nextCommands)
   at bolt.cli.CommandProcessor.ProcessCommands(Queue`1 commands, IVerbFactory factory)
   at bolt.cli.CommandProcessor.LaunchCommand(IReadOnlyList`1 args, UserHelpText userHelpText, Boolean isNonInteractiveModeEnabled)
   at bolt.Session.Run(ProgramArguments args)
2023-07-04 13:51:42.5656 | INF | Microsoft.PowerPlatform.Tooling.BatchedTelemetry :: BatchedTelemetryChannel.StartUploadProcess Started uploader with process id: 20044
2023-07-04 13:51:42.5736 | INF | bolt.Session :: End session. (ResponseCode: 500)

[BetimBeja]

@petrochuk @davidjenni
Maybe expose this error in the command line instead of the cryptic message that it is throwing currently?

[petrochuk]

Agree, this error should be improved and made more clear

[petrochuk]

@BetimBeja @Ionavoss thanks for reporting. This is fixed in version 1.25