no MEDIA response when ask "play news" - media

I'm doing test google-assistant-sdk(python) on our Arm linux platform, use same credentials.json and same device-model-id on Raspberry, but have not same result with raspberry when test "play news" command. On raspberry, sdk will output
ON_CONVERSATION_TURN_STARTED
ON_END_OF_UTTERANCE
ON_RECOGNIZING_SPEECH_FINISHED:
{"text": "play news"}
ON_RESPONDING_STARTED:
{"is_error_response": false}
ON_RESPONDING_FINISHED
ON_CONVERSATION_TURN_FINISHED:
{"with_follow_on_turn": false}
ON_MEDIA_TRACK_LOAD:
{
"metadata": {
"album": "Reuters TV 5-minute briefing (U.S.)",
"album_art": "http://lh6.googleusercontent.com/proxy/WA10gikNluFtl4dkyHvP3h42oPBqjROLOQDQg0r6NTWyYvXF5OFY-XounxWKanpfRLMsS_oStiFqyAc90O8459WVEDiSQ63TGhmtQqozEi5vgBj8tKBlmf6JO-dqJabzIiKh=s128",
"title": "Reuters TV (U.S.)"
},
"track_type": 1
}
ON_MEDIA_TRACK_PLAY:
{
"metadata": {
"album": "Reuters TV 5-minute briefing (U.S.)",
"album_art": "http://lh6.googleusercontent.com/proxy/WA10gikNluFtl4dkyHvP3h42oPBqjROLOQDQg0r6NTWyYvXF5OFY-XounxWKanpfRLMsS_oStiFqyAc90O8459WVEDiSQ63TGhmtQqozEi5vgBj8tKBlmf6JO-dqJabzIiKh=s128",
"title": "Reuters TV (U.S.)"
},
"track_type": 1
}
But no ON_MEDIA_TRACK_LOAD and ON_MEDIA_TRACK_PLAY on my arm platform.
I use python 3.6.3 on my arm platform. and no error show after
ON_CONVERSATION_TURN_STARTED
ON_END_OF_UTTERANCE
ON_RECOGNIZING_SPEECH_FINISHED:
{"text": "play news"}
ON_RESPONDING_STARTED:
{"is_error_response": false}
ON_RESPONDING_FINISHED
ON_CONVERSATION_TURN_FINISHED:
{"with_follow_on_turn": false}
it just no these MEDIA event output, it seems like sdk can't process this MEDIA event on my arm platform, but no error and other things to check. Do anyone can give me some suggest? thanks!
BTW, When I test "play music" on raspberry, and get response "Sorry, I can't do that on this device." is it right? I use google_assistant_library-1.0.0 to test, and it support to play news and music in its release note, but only "play news" seems to work on raspberry?

Related

Teams Message Card Post Action Ignoring event from domain not in allow-list

Searched almost all the web ... last hope here ... ;-)
Connectors: Ignoring event from domain not in allow-list << see debug log below
Problem description:
We have developed an teams office 365 connector. This connector sends a message card using the incoming web hook configured by the manifest. On this message card we have a POST action defined. When we press on this action a REST API call should be executed to a custom REST end point. The issue currently is that we are able to successful add the connector using the manifest and configuration page and we are able to successfully send an message card to the channel. But when we press the action the REST end point is not called at all and we get a "Forbidden message".
We have registered the connector using the portal: https://outlook.office.com/connectors/home/login/#/publish
And we have specified:
"Do you want to enable actions on your Connector cards?" -> YES
"Actions URL" -> "https://teamsrestapi.ngrok.io/RestAPI/Action"
We have created a manifest with the correct whitelisting as:
"validDomains": [
"teamsrestapi.ngrok.io"
]
And we are using the correct connector ID got from the connector portal.
Configurations tried so far without luck:
We have enabled in the Teams 'Org-wide setting' -> Users can communicate with other Skype for Business and Teams users
We have enabled in the Teams 'Org-wide setting' -> Users can communicate with Skype users
We have added in the Teams 'Org-wide setting' the whitelisted Domain -> teamsrestapi.ngrok.io is Allowed
We have tried to deploy the app as an organisation wide app by putting it into the store
We checked all other network blocks whitelists etc.
We tried not to use ngrok but a Azure Webapp
Question:
Does anybody has an idea on how to put the domain into the correct allow list ? We also have tried to use a non ngrok address as a Azure Webapp but same error.
Debug Logs:
Below i pasted a part of the TEAMS debug log:
020-08-27T11:43:49.581Z Inf [Scenario]ext_actionable_card_http_post [step](1)stop (173ms/173ms)
2020-08-27T11:43:49.580Z Err [O365ActionPaneController.makeHttpPOSTRequestForConnector()] Http invoke failed: {"data":{"errorCode":"Forbidden"},"status":403,"config":{"method":"POST","transformRequest":[null],"transformResponse":[null],"url":"https://teams.microsoft.com/api/mt/part/emea-02/beta/users/connectors/19:aaaaef3d98aaacfa817e3524bf5784f0#thread.tacv2;messageid=1598528625119/1598528625119/executeAction","data":{"inputParameters":[],"actionId":"aaaa4501-c054-49f4-b377-dc2b3f26c7d0","potentialAction":"{\"#type\":\"HttpPOST\",\"#i...
2020-08-27T11:43:49.579Z War HTTP request failed: POST "https://teams.microsoft.com/api/mt/part/emea-02/beta/users/connectors/19:aaaaaf3d98f34cfa817e3524bf5784f0#thread.tacv2;messageid=1598528625119/1598528625119/executeAction", status: 403, response: {"errorCode":"Forbidden"}, errorCode: Forbidden, requestId: undefined, correlationId: undefined, afdCorrelationId: Ref A: FB26054A0C7546D48003683B610E009D Ref B: AM3EDGE0714 Ref C: 2020-08-27T11:43:49Z
2020-08-27T11:43:49.578Z Inf [Scenario]ext_actionable_card_http_post [step](0)error (164ms)
2020-08-27T11:42:57.574Z Inf [Scenario]ext_sdkHelper_created [step](4)ext_sdkHelper_apiInvoked (2057ms)
2020-08-27T11:42:57.477Z Err ngClickDecorator: value not found in enum type. value:
2020-08-27T11:42:55.529Z Inf Connectors: Ignoring event from domain not in allow-list - https://teamsrestapi.ngrok.io
2020-08-27T11:42:55.517Z Inf [Scenario]ext_sdkHelper_created [step](3)ext_sdkHelper_apiInvoked (82ms)
2020-08-27T11:42:55.487Z Inf Connectors: Ignoring event from domain not in allow-list - https://teamsrestapi.ngrok.io
2020-08-27T11:42:55.474Z Inf Connectors: Ignoring event from domain not in allow-list - https://teamsrestapi.ngrok.io
2020-08-27T11:42:55.453Z Inf Connectors: Ignoring event from domain not in allow-list - https://teamsrestapi.ngrok.io
2020-08-27T11:42:55.444Z Inf Connectors: Received event - handleMessageSuccess
2020-08-27T11:42:55.436Z Inf Connectors: Received event - unhandledMessage
2020-08-27T11:42:55.435Z Inf [Scenario]ext_sdkHelper_created [step](2)ext_sdkHelper_apiInvoked (53ms)
2020-08-27T11:42:55.427Z Inf Connectors: Received event - unhandledMessage
2020-08-27T11:42:55.418Z Inf Connectors: Received event - handleMessageSuccess
2020-08-27T11:42:55.406Z Inf Connectors: Received event - handleMessageSuccess
2020-08-27T11:42:55.386Z Inf Connectors: Ignoring event from domain not in allow-list - https://teamsrestapi.ngrok.io
Manifest used:
{
"$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.6/MicrosoftTeams.schema.json",
"manifestVersion": "1.6",
"id": "aaf6fb9b-5d8c-4c12-b5e1-3ea8c5d8a7d1",
"version": "1.0.14",
"packageName": "com.Teams.Connector.WEB",
"developer": {
"name": "Developer",
"websiteUrl": "https://www.xxxx.com",
"privacyUrl": "https://www.xxxx.com",
"termsOfUseUrl": "https://www.xxxx.com"
},
"description": {
"full": "OpsLogix Teams Connector WEB",
"short": "Connector WEB"
},
"icons": {
"color": "color.png",
"outline": "outline.png"
},
"connectors": [
{
"connectorId": "aaaaabc5-8b41-41b3-94f1-1bdb70e2cb84",
"scopes": [
"team"
],
"configurationUrl": "https://teamsrestapi.ngrok.io/configuration"
}
],
"name": {
"full": "Teams.Connector.WEB",
"short": "Teams.Connector.WEB"
},
"accentColor": "#FFFFFF",
"validDomains": [
"teamsrestapi.ngrok.io"
]
}

Mozilla Firefox extension: Creating a new alarm

I am working on a Mozilla Firefox extension that is creating a new alarm.
Here is the code in the manifest.json file:
{
"manifest_version": 2,
"name": "alarms-test",
"version": "1.0",
"content_scripts":
[
{
"matches": ["https://developer.mozilla.org/*"],
"js": ["alarms-test.js"]
}
],
"permissions":
[
"alarms"
]
}
Here is the code in the alarms-test.js file:
console.log("alarms-test: start");
const delayInMinutes = 1;
browser.alarms.create({delayInMinutes});
console.log("alarms-test: end");
Here are the steps that I am following:
In Mozilla Firefox, go to about:debugging
Click on This Firefox then Load Temporary Add-on...
Browse your local files to select the manifest.json file
Go to https://developer.mozilla.org/en-US/
Press F12 then click on the Console tab
See the output
Expected output:
alarms-test: start
alarms-test: end
Current output:
alarms-test: start
It means that something went wrong with the lines 2 and 3 of alarms-test.js.
Do you see what I forgot please?
Thank you.
Best regards.

Invalid Container 'DOMAIN_INSTALLABLE' in manifest

I am getting the following error message when trying to publish an app to G Suite Marketplace from Chrome developer dashboard. I am following this documentation.
Below is my manifest.json file.
{
"name": "Test Publishing",
"version": "1.0",
"manifest_version": 2,
"api_console_project_id": "poj_id",
"container": ["DOMAIN_INSTALLABLE"],
"app": {
"urls": [
"https://example.com/"
],
"launch": {
"web_url": "https://example.com"
}
},
"icons": {
"128": "example_icon_128.png"
}
}
Any idea on how to fix this? Is this now changed?
As you may know, G Suite extensions are being migrated from the Chrome Web Store to the G Suite Marketplace.
Web apps can now be published to the G Suite Marketplace directly from the Cloud Console without having to publish them in the Chrome Web Store. See the note at the top of https://developers.google.com/gsuite/marketplace/listing-gsm.

How to update self-hosted firefox webExtension

How do I configure my self-distrubuted firefox webExtension to auto-update, I have tried following MDN update doc but still unable to update.
My web Extension is hosted on a sub-domain name like
"https://files.example.com/myfile/extension.xpi"
My updates.json file resides at the same location with my .xpi file
This is a prototype of my updates.json
{
"addons": {
"updates": [ { "version": "1.2",
"update_link": "https://files.abc.com/myfiles/extension-1.2-an+fx.xpi" },
{ "version": "1.3",
"update_link": "https://files.abc.com/myfiles/extension-1.3-an+fx.xpi" }
]
}
}
This is the gibberish I get from browser console
1535658478365 addons.update-checker WARN onUpdateCheckComplete failed
to parse update manifest: [Exception... "Update manifest is missing a
required addons property." nsresult: "0x80004005 (NS_ERROR_FAILURE)"
location: "JS frame ::
resource://gre/modules/addons/AddonUpdateChecker.jsm ::
getRequiredProperty :: line 120" data: no] Stack trace:
getRequiredProperty()#resource://gre/modules/addons/AddonUpdateChecker.jsm:120
parseJSONManifest()#resource://gre/modules/addons/AddonUpdateChecker.jsm:130 onLoad()#resource://gre/modules/addons/AddonUpdateChecker.jsm:309 UpdateParser/<()#resource://gre/modules/addons/AddonUpdateChecker.jsm:241
It looks like your 'updates.json' is missing the add-on name and XPI hash. I would also test without the "+" in the file name, I think that caused me issues (Due to hosting server).
To view your add-ons UUID (ex "ADDONNAME#test.com") log into the developer hub, click edit information, then look under technical information. To generate an update_hash of your XPI file I would recommend VSCryptoHash, but any other program that generates a cryptographic hash will work.
{
"addons": {
"ADDONNAME#test.com": {
"updates": [
{ "version": "1.0.0",
"update_link": "https://files.abc.com/myfiles/extension-1.2-fx.xpi" ,
"update_hash": "sha256:blahblah" }
]
}
}
}
The console error says your manifest is missing something too. Here is an example based on mine that works.
"applications": {
"gecko": {
"id": "ADDONNAME#test.com",
"strict_min_version": "50.0",
"update_url": "https://webpage/Updatefile.json"
}
},

Pebble sdk 2.x unable to load resource

I know pebble 2.x is a bit outdated, but that's the watch that I recently got and am interested in writing a small app on this.
I am unable to load the resource files (images and font) in my pebble app. Below is the error message when I try to run pebble build:
Setting top to : /home/mixi/Documents/pebble-dev/helloworld
Setting out to : /home/mixi/Documents/pebble-dev/helloworld/build
Checking for program gcc,cc : arm-none-eabi-gcc
Checking for program ar : arm-none-eabi-ar
Found Pebble SDK in : /home/mixi/.pebble-sdk/SDKs/current/sdk-core/pebble/aplite
'configure' finished successfully (0.220s)
Waf: Entering directory `/home/mixi/Documents/pebble-dev/helloworld/build'
Error Generating Resources: File: bt-icon.png has specified invalid type: bitmap
Must be one of (raw, png, png-trans, font)
Generating resources failed
My appinfo.json:
{
"uuid": "93c49fe2-0b1e-44b8-8fff-22d9c87adab9",
"shortName": "helloworld",
"longName": "helloworld",
"companyName": "MakeAwesomeHappen",
"versionLabel": "1.0",
"sdkVersion": "2.9",
"targetPlatforms": ["aplite", "basalt", "chalk"],
"watchapp": {
"watchface": true
},
"appKeys": {
"dummy": 0
},
"resources": {
"media": [
{
"type": "bitmap",
"name": "IMAGE_BT_ICON",
"file": "bt-icon.png"
}
]
},
"versionCode": 1
}
My Pebble version:
Pebble Tool v4.0 (active SDK: v2.9)
I also tried creating a test app on pebblecloud with their sample. The sample runs fine without resource, but also fails when I add a new resource to the project. Is there a fix to this?
Apparently, pebble 2.x does not like "bitmap" type. All I had to do was change resource type to "png" in the JSON file:
"media": [
{
"type": "png",
"name": "IMAGE_BT_ICON",
"file": "bt-icon.png"
}
]
OMG =A=..
As for CloudPebble, the drop down for Resource Type doesn't seem to show up and it seems to select Bitmap by default.. Maybe it'll be fixed in the near future idk.

Resources