9.2.0 Latest Release Issues #9705

Hi ANZ Team,

• What is your product version? 9.2.0 (Latest)
• What is your product type (Angular or MVC)? Angular
• What is product framework type (.net framework or .net core)? Core

I'm not sure if I am jumping the gun now due to a release mail not being sent yet, but it has been available for download for 2 days now and quite a few days past the due date so I downloaded this to test it.

So far this is 3 versions with issues in a row. 9.1 Xamarin Issues (Same issue in latest version as well) 9.2.0 RC1 Xamarin Issues (Same issue in latest version as well) & Master Detail issues 9.2.0 Xamarin Issues & Latest issue with angular brings us to this Ticket being logged.

As far as I understood 9.2 RC1 is supposed to be the test version and 9.2 the release is final version which is stable then.

I can't test any of the 9.2 RC1 issues if they are resolved as there are now issues with Angular side of the app.

Angular Issue:

PS C:\Users\NopeNope\Documents\BRM (5)\BRM\angular> npm start

[email protected] start C:\Users\NopeNope\Documents\BRM (5)\BRM\angular gulp buildDev && ng serve --host 0.0.0.0 --port 4200

[11:21:47] Using gulpfile ~\Documents\BRM (5)\BRM\angular\gulpfile.js [11:21:47] Starting 'buildDev'... [11:21:47] 'buildDev' errored after 37 ms [11:21:47] Error: Invalid glob argument: at Gulp.src (C:\Users\NopeNope\Documents\BRM (5)\BRM\angular\node_modules\vinyl-fs\lib\src\index.js:20:11) at createStyleBundle (C:\Users\NopeNope\Documents\BRM (5)\BRM\angular\gulpfile.js:100:23) at createStyleBundles (C:\Users\NopeNope\Documents\BRM (5)\BRM\angular\gulpfile.js:88:13) at buildDev (C:\Users\NopeNope\Documents\BRM (5)\BRM\angular\gulpfile.js:133:22) at buildDev (C:\Users\NopeNope\Documents\BRM (5)\BRM\angular\node_modules\undertaker\lib\set-task.js:13:15) at bound (domain.js:430:14) at runBound (domain.js:443:12) at asyncRunner (C:\Users\NopeNope\Documents\BRM (5)\BRM\angular\node_modules\async-done\index.js:55:18) at processTicksAndRejections (internal/process/task_queues.js:75:11) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! [email protected] start: gulp buildDev && ng serve --host 0.0.0.0 --port 4200 npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\NopeNope\AppData\Roaming\npm-cache_logs\2020-10-06T09_21_47_243Z-debug.log

Log details of above issue:

0 info it worked if it ends with ok 1 verbose cli [ 1 verbose cli 'C:\Program Files\nodejs\node.exe', 1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js', 1 verbose cli 'start' 1 verbose cli ] 2 info using [email protected] 3 info using [email protected] 4 verbose run-script [ 'prestart', 'start', 'poststart' ] 5 info lifecycle [email protected]~prestart: [email protected] 6 info lifecycle [email protected]~start: [email protected] 7 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true 8 verbose lifecycle [email protected]~start: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\NopeNope\Documents\BRM (5)\BRM\angular\node_modules.bin;;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Windows\System32\OpenSSH;C:\Program Files\NVIDIA Corporation\NVIDIA NvDLISR;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn;C:\Program Files\Microsoft SQL Server\140\Tools\Binn;C:\Program Files (x86)\Microsoft SQL Server\140\DTS\Binn;C:\Program Files\Microsoft SQL Server\140\DTS\Binn;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn;C:\Program Files (x86)\Microsoft SQL Server\150\DTS\Binn;C:\Program Files\dotnet;C:\Program Files\Microsoft SQL Server\130\Tools\Binn;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn;C:\Program Files\SAP\SAP Business One DI API\JCO\LIB;C:\Program Files\SAP\SAP Business One DI API\DI API 90;C:\Program Files (x86)\SAP\SAP Business One DI API\JCO\LIB;C:\Program Files (x86)\SAP\SAP Business One DI API\DI API 90;C:\Program Files\SAP\SAP Business One;C:\Program Files (x86)\SAP\SAP Business One ServerTools\LicenseHTTPS\webapps\lib;C:\Program Files (x86)\SAP\SAP Business One ServerTools\Common\sapjvm_8\jre\bin;C:\Program Files (x86)\SAP\SAP Business One ServerTools\Common\tomcat\bin;C:\Program Files (x86)\SAP\SAP Business One;C:\Program Files (x86)\SAP\SAP Business One ServerTools\Common\sapjvm_8\jre\bin\server;C:\Program Files (x86)\dotnet;C:\Program Files\nodejs;C:\Program Files (x86)\Yarn\bin;C:\Users\NopeNope\AppData\Local\Microsoft\WindowsApps;C:\Users\NopeNope.dotnet\tools;C:\Users\NopeNope\AppData\Roaming\npm;C:\Users\NopeNope\AppData\Local\Yarn\bin;C:\Users\NopeNope\AppData\Local\GitHubDesktop\bin 9 verbose lifecycle [email protected]~start: CWD: C:\Users\NopeNope\Documents\BRM (5)\BRM\angular 10 silly lifecycle [email protected]~start: Args: [ '/d /s /c', 'gulp buildDev && ng serve --host 0.0.0.0 --port 4200' ] 11 silly lifecycle [email protected]~start: Returned: code: 1 signal: null 12 info lifecycle [email protected]~start: Failed to exec start script 13 verbose stack Error: [email protected] start: gulp buildDev && ng serve --host 0.0.0.0 --port 4200 13 verbose stack Exit status 1 13 verbose stack at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16) 13 verbose stack at EventEmitter.emit (events.js:314:20) 13 verbose stack at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14) 13 verbose stack at ChildProcess.emit (events.js:314:20) 13 verbose stack at maybeClose (internal/child_process.js:1047:16) 13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5) 14 verbose pkgid [email protected] 15 verbose cwd C:\Users\NopeNope\Documents\BRM (5)\BRM\angular 16 verbose Windows_NT 10.0.19041 17 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "start" 18 verbose node v14.10.1 19 verbose npm v6.14.8 20 error code ELIFECYCLE 21 error errno 1 22 error [email protected] start: gulp buildDev && ng serve --host 0.0.0.0 --port 4200 22 error Exit status 1 23 error Failed at the [email protected] start script. 23 error This is probably not a problem with npm. There is likely additional logging output above. 24 verbose exit [ 1, true ]

Is there a manual way to resolve this as I would like to test the Master Detail pages again in order to determine if we can start upgrading or have to wait till 15th/20th for the next version.

Regards, AuroraBMS