-
Notifications
You must be signed in to change notification settings - Fork 25
Alexa Smart Screen SDK make error #41
Comments
Got exactly the same error. 2020-09-04T15_50_33_863Z-debug.log I'm working on Ubuntu 16.04. |
Thank you for raising this issue, it appears that an upgrade to one of our node dependencies has caused the build fail. We will be resolving these issues by locking the dependency versions in our next release. In the meantime please can you use the attached package-lock.json file. |
Hi Powj, Thanks for the swift response. I will give it a try the fix you mentioned. I will keep you posted with the progress. Thanks, |
Hi Powj, quick update, after replacing the file it all works fine now. I have another question. How can I enable the "Wake" Alexa feature on Screen SDK |
Hi Ali, Also make sure to apply the same flags on the Smart-screen-sdk
|
Hi Lynx-arul, Thanks for the info. I will give it a try. Thanks, |
Hi Lynx-Arul, so got the AVS working with wake word turned on but I got AlexaClientSDK 1.20.1 instead of 1.20.0 so now when try to make config for screen then it fails as it is looking for 1.20.0. Is there a way to change the AlexaClientSDK version check to 1.20.1 below is the error details:
-- Configuring incomplete, errors occurred! |
One more question how can I start Wake word along with smart screen cd $HOME/sdk_folder/ss-build I tried adding ../third-party/alexa-rpi/models at the end of AlexaClientSDKConfig.json but that didnt work |
For your first question, please use v1.20.0. The current Smart Screen SDK (v2.2.1) is only compatible with Device SDK v1.20.0 - Here is the repo link - avs-device-sdk. As far as your second question, you should be able to run the Sample App the same way with or without the wake-word. The only difference is how you build the Sample App. As long as you create a new build folder and add the flags mentioned above you should be fine. |
Hi Lynx-arul, Thanks for the help. I will give it a try with AVS SDK version v1.20.0 and let you know if it works. Thanks, |
Thank you, it worked for me too. |
Hi, so I have now everything up and working except the wake word. when I run the following command then I still have to use "A" to talk to alexa. if i run AVS independently with following command then the Wake word works so the additional call in this case is "../third-party/alexa-rpi/models" which makes the wake word works. now i dont know how to make this work with screen SDK, could you please help me to launch the wake word with screen as well thanks. |
You will need to pass in the models using the -K (keyword) flag: |
Hi Powj, Thank you very much for your help. Its all working nicely. Regards, |
hi using same environment (raspberry pi, buster, node 12.8.3, wakeword) with provided
build succeeds after changing
to
br, uberl |
I too am having the exact same problem. Has a solution to this been discovered yet? As of the last time that I reinstalled raspbian and started from scratch, my OS is whatever the raspberry pi had for the noobs full download as of this morning. I am trying to install the Alexa Smart Screen SDK on my Raspberry Pi 4. I make it all the way without any issues to step 9. The second part of step 9 is the make portion of the code, upon completion I get the following errors and logfile (Attached Doc) At this point of have completely erased and started from scratch at least 10 times in the past week, not to mention the countless retrys and fixes in between, so any help would be greatly appreciated. After following the above guidance replacing the package-lock.json as instructed above, it still is not working for me. This is what comes out in the terminal, however I still can't access the HTTP file via the web browser. |
Hi @CAG5 - Please send us a log file in plain text as I am unable to open docx files. |
Sure, I can try anyway. Hope that this helps |
@CAG5
In your In your Please go through these steps:
|
@ulrich-berl Please delete your |
When I followed the above steps this time. I recieved errno 2 ELIFECYCLE error, so I went to the /modules/gui/js/ folder and deleted all contents of the node-js folder and manually copy and pasted the unzipped package-lock json there and ran the make command again and it finally worked. However separate but related issue, even after going to sudo raspi-config and changing the speaker output and selecting analog from the desktop, it only plays out of my monitor speakers and not the speakers that I have plugged into the 3.5mm jack, and I still have not been able to get the wakeword to work so it is completely voice activated. |
@CAG5 great! Please paste this to your ${HOME}/.asoundrc file:
Copied from https://iotbytes.wordpress.com/connect-configure-and-test-usb-microphone-and-speaker-with-raspberry-pi/ |
Please edit values as applicable to your setup. |
Awesome, didn't fix it at first, so did the raspi-config, and desktop and the ~/.asoundrc file and then rebooted it and now the speaker and mic work. Any suggestions on how to get it to recognize the wakeword so I can stop holding down the "A" key everytime I want to interact with it? |
negative, already replaced
builds only if changing type of |
Thanks for trying it out, yes it's resolving it to the wrong namespace. Can you please print your nodejs version? in the meanwhile, you an explicitly add |
v12.18.4 |
IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
Briefly summarize your issue:
while trying to make screen SDK gui error occurred.
What is the expected behavior?
What behavior are you observing?
Provide the steps to reproduce the issue, if applicable:
make AVS screen SDK
Tell us about your environment:
Raspberry piWhat version of the AVS Device SDK are you using?
Tell us what hardware you're using:
Tell us about your OS (Type & version):
Have you tried the same use case with AVS Device SDK SampleApp?
[X ] The issue is not applicable to the AVS Device SDK SampleApp.
The issue is not reproducible on the AVS Device SDK SampleApp.
[ 98%] Building CXX object modules/Alexa/SampleApp/src/CMakeFiles/SampleApp.dir/PortAudioMicrophoneWrapper.cpp.o
[100%] Linking CXX executable SampleApp
[100%] Built target SampleApp
Scanning dependencies of target GUIClient
npm WARN deprecated tslint-loader@3.6.0: TSLint is deprecated. As such migrate from tslint-loader to eslint-loader.
npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN notsup Unsupported engine for watchpack-chokidar2@2.0.0: wanted: {"node":"<8.10.0"} (current: {"node":"12.18.3","npm":"6.14.6"})
npm WARN notsup Not compatible with your version of node/npm: watchpack-chokidar2@2.0.0
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/watchpack-chokidar2/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
npm WARN gui@1.0.0 No repository field.
npm WARN gui@1.0.0 license should be a valid SPDX license expression
added 508 packages from 334 contributors and audited 510 packages in 170.708s
22 packages are looking for funding
run
npm fund
for detailsfound 0 vulnerabilities
Hash: 01b181f7dc8bb2a86259
Version: webpack 4.44.1
Time: 110762ms
Built at: 09/04/2020 15:38:02
34 assets
Entrypoint main = main.bundle.js
[1] /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/apl-client/index.js 607 KiB {0} [built]
[4] ./lib/config/IDeviceAppConfig.ts 794 bytes {0} [built]
[5] ./lib/messages/messages.ts 1.73 KiB {0} [built]
[10] ./lib/displayCards/AVSDisplayCardHelpers.ts 2.86 KiB {0} [built]
[11] ./main.tsx 563 bytes {0} [built]
[12] ./app.tsx 17.9 KiB {0} [built]
[25] ./lib/messages/NavigationEvent.ts 637 bytes {0} [built]
[26] ./lib/messages/client.ts 3.51 KiB {0} [built]
[30] ./lib/messages/sdkLogTransport.ts 1.7 KiB {0} [built]
[31] ./lib/focus/FocusManager.ts 3.03 KiB {0} [built]
[32] ./lib/activity/ActivityTracker.ts 2.38 KiB {0} [built]
[37] ./lib/config/GuiConfigHelpers.ts 8.14 KiB {0} [built]
[38] ./lib/messages/UWPClient.ts 1.67 KiB {0} [built]
[46] ./main.css 1.05 KiB {0} [built]
[47] ../node_modules/css-loader/dist/cjs.js!./main.css 735 bytes {0} [built]
+ 33 hidden modules
ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/base.d.ts
[tsl] ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/base.d.ts(10,1)
TS1084: Invalid 'reference' directive syntax.
ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/base.d.ts
[tsl] ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/base.d.ts(11,1)
TS1084: Invalid 'reference' directive syntax.
ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/base.d.ts
[tsl] ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/base.d.ts(12,1)
TS1084: Invalid 'reference' directive syntax.
ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/base.d.ts
[tsl] ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/base.d.ts(13,1)
TS1084: Invalid 'reference' directive syntax.
ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/assert.d.ts
[tsl] ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/assert.d.ts(2,68)
TS1144: '{' or ';' expected.
ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/assert.d.ts
[tsl] ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/assert.d.ts(22,68)
TS1144: '{' or ';' expected.
ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/assert.d.ts
[tsl] ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/assert.d.ts(31,94)
TS1144: '{' or ';' expected.
ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/assert.d.ts
[tsl] ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/assert.d.ts(31,101)
TS1005: ';' expected.
ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/assert.d.ts
[tsl] ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/assert.d.ts(31,104)
TS1005: ';' expected.
ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/assert.d.ts
[tsl] ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/assert.d.ts(33,98)
TS1144: '{' or ';' expected.
ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/assert.d.ts
[tsl] ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/assert.d.ts(33,105)
TS1005: ';' expected.
ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/assert.d.ts
[tsl] ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/assert.d.ts(33,108)
TS1005: ';' expected.
ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/assert.d.ts
[tsl] ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/assert.d.ts(41,47)
TS1144: '{' or ';' expected.
ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/assert.d.ts
[tsl] ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/assert.d.ts(41,53)
TS1005: ';' expected.
ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/assert.d.ts
[tsl] ERROR in /home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/js/node_modules/@types/node/assert.d.ts(41,56)
TS1005: ';' expected.
Child html-webpack-plugin for "index.html":
1 asset
Entrypoint undefined = index.html
4 modules
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! gui@1.0.0 build:
npm run lint && webpack --config webpack.config.js "--output-path" "/home/pi/sdk_folder/ss-build/modules/GUI" "--define" "DISABLE_WEBSOCKET_SSL=true" "--define" "USE_UWP_CLIENT=false"
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the gui@1.0.0 build 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! /home/pi/.npm/_logs/2020-09-04T14_38_02_946Z-debug.log
make[2]: *** [modules/GUI/CMakeFiles/GUIClient.dir/build.make:59: modules/GUI/CMakeFiles/GUIClient] Error 2
make[1]: *** [CMakeFiles/Makefile2:2468: modules/GUI/CMakeFiles/GUIClient.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
The text was updated successfully, but these errors were encountered: