The askToDeeplink helper function seems to be broken a couple of days ago. Prior to March 28th I was able to invoke askToDeeplink from my unpublished action in test mode. However, something happened since the 28th and now invoking the helper gives me the following error message :
{
insertId: "1ckduv6g8muy3da"
labels: {
channel: "preview"
querystream: "GOOGLE_USER"
source: "JSON_RESPONSE_VALIDATION"
}
logName: "projects/androidlinktest2/logs/actions.googleapis.com%2Factions"
receiveTimestamp: "2018-03-30T01:24:52.261359446Z"
resource: {
labels: {
action_id: ""
project_id: "androidlinktest2"
version_id: ""
}
type: "assistant_action"
}
severity: "ERROR"
textPayload: "MalformedResponse at expected_inputs[0].possible_intents[0].input_value_data.open_url_action.open_url_action.android_app: Android app must be connected to the agent"
timestamp: "2018-03-30T01:24:52.253875989Z"
trace: "projects/435016350697/traces/1522373084415"
}
Could someone please help?
Android app must be connected to the agent
Have you gone into the actions on google console & associated your android app with the assistant? See: "Connected properties" section.
https://developers.google.com/actions/console/brand-verification
Related
I have a dialogflow bot that upon welcome makes a fulfillment call to app engine. This works except that during a review of the logs, I notice that there was an error. The fulfillment webhook failed. The raw interaction log shows:
"diagnosticInfo": {
"webhook_latency_ms": "2008.0"
},
"webhookStatus": {
"webhookStatus": {
"code": 7,
"message": "Webhook call failed. Error: PERMISSION_DENIED, State: URL_REJECTED, Reason: REJECTED_CREDENTIAL_ERROR."
},
"webhookUsed": true
},
Note that if this is a permission issue, it should happen all the time and not just once. What could be the cause? There isn't anything in app engine log, which would make sense if it can't even connect to it and the app engine was working at the time of the call.
enter image description hereI need to allow the notification for the chrome browser to get incoming message notifications on my PC.
I have tried this code in the protractor.config file. It was still displaying the pop
capabilities: {
browserName: 'chrome',
'chromeOptions':{
'prefs' : {'profile.default_content_setting_values.geolocation': }
},
I have also tried using the following code in spec, it is not working
browser.switchTo().alert().accept()
for this code, I am getting an error as No such alert was found and the scripts fail.
Is there any provision to allow notification pop in the protractor for the chrome browser?
geolocation has nothing to do with it. You need to try these options https://chromium.googlesource.com/chromium/src/+/7e762c1f17514a29834506860961ba2f24e7e6e5/components/content_settings/core/common/pref_names.cc#36 Most likely these 3
"profile.default_content_setting_values.media_stream";
"profile.default_content_setting_values.media_stream_mic";
"profile.default_content_setting_values.media_stream_camera";
try these capabilities
{
browserName: 'chrome',
chromeOptions: {
prefs: {
'profile.default_content_setting_values.media_stream': 2,
"profile.default_content_setting_values.media_stream_mic": 2,
"profile.default_content_setting_values.media_stream_camera": 2
},
},
}
I am trying to convert a simple webpage I have into a PWA in case the site it uses goes down.
I think I have done the majority of the work. The page is installable on my phone and passes all the Chrome lighthouse tests. But I get the following warning,
Web app manifest meets the installability requirements
Warnings: Page does not work offline. The page will not be regarded as installable after Chrome 93, stable release August 2021.
I also get the following warning and error in console,
The FetchEvent for "https://dannyj1984.github.io/index.html" resulted in a network error response: the promise was rejected.
Promise.then (async)
(anonymous) # serviceWorker.js:30
serviceWorker.js:1 Uncaught (in promise) TypeError: Failed to fetch
There is then a warning saying the site cannot be installed as does not work offline. I have read the chrome dev article which says from the chrome release in Aug21 apps that dont work offline wont be installable. But I am stuck on which part of my fetch is causing an issue. The code in my service worker is,
const TGAbxApp = "TG-ABX-App-v1"
const assets = [
//paths to files to add
]
self.addEventListener("install", installEvent => {
installEvent.waitUntil(
caches.open(TGAbxApp).then(cache => {
cache.addAll(assets)
})
)
})
self.addEventListener('fetch', function(event) {
event.respondWith(
caches.match(event.request)
.then(function(response) {
// Cache hit - return response
if (response) {
return response;
}
return fetch(event.request);
}
)
);
});
The above code for the fetch part of the service worker I took from Google and as I understand it, it first checks if there is data in the cache stored on install, if not it will request it from the network.
https://developer.chrome.com/blog/improved-pwa-offline-detection/
From Chrome 89 March 2021, it gives a warning if this check does not pass:
The installed service worker fetch event returns an HTTP 200 status code (indicating a successful fetch) in simulated offline mode.
So, in your case, the service worker should return a cached 'index.html' when fetch(event.request) is failed.
I've had the same problem. I re enabled the cache through the developer console->network. fixed
I installed Rundeck v3.3.5 (on CentOS 7 via RPM) to replace an old Rundeck instance that was decommissioned. I did the export/import of projects (which worked brilliantly) while connected to the new server as the default admin user. The imported jobs run properly on the correct schedule. I subsequently configured the new server to use LDAP authentication and configured ACLs for users/roles. That also works properly.
However, I see an error like this in the service.log:
ERROR services.NotificationService - Error sending notification email to foo#bar.com for Execution 9358 Error executing tag <g:render>: could not initialize proxy [rundeck.Workflow#9468] - no Session
My thought is to switch job owners from admin to a user that exists in LDAP. I mean, I would like to switch job owners regardless, but I'm also hoping it addresses the error.
Is there a way in the web interface or using rd that I can bulk-modify jobs to switch the owner?
It turns out that the error in the log was caused by notification settings in an included job. I didn't realize that notifications were configured on the parameterized shared job definition, but there were; removing the notification settings caused the error to stop being added to /var/log/rundeck/service.log.
To illustrate the problem, here are chunks of YAML I've edited to show just the important parts. Here's the common job:
- description: Do the actual work with arguments passed
group: jobs/common
id: a618ceb6-f966-49cf-96c5-03a0c2efb9d8
name: do_the_work
notification:
onstart:
email:
attachType: file
recipients: ops#company.com
subject: Actual work being started
notifyAvgDurationThreshold: null
options:
- enforced: true
name: do_the_job
required: true
values:
- yes
- no
valuesListDelimiter: ','
- enforced: true
name: fail_a_lot
required: true
values:
- yes
- no
valuesListDelimiter: ','
scheduleEnabled: false
sequence:
commands:
- description: The actual work
script: |-
#!/bin/bash
echo ${RD_OPTION_DO_THE_JOB} ${RD_OPTION_FAIL_A_LOT}
keepgoing: false
strategy: node-first
timeout: '60'
uuid: a618ceb6-f966-49cf-96c5-03a0c2efb9d8
And here's the job that calls it (the one that is scheduled and causes an error to show up in the log when it runs):
- description: Do the job
group: jobs/individual
name: do_the_job
...
notification:
onfailure:
email:
recipients: ops#company.com
subject: '[Rundeck] Failure of ${job.name}'
notifyAvgDurationThreshold: null
...
sequence:
commands:
- description: Call the job that does the work
jobref:
args: -do_the_job yes -fail_a_lot no
group: jobs/common
name: do_the_work
If I remove the notification settings from the common job, the error in the log goes away. I'm not sure if sending notifications from an included job is not supported. It would be useful to me if it was, so I could place notification settings in a single location. However, I can understand why it presents a problem for the scheduler/executor.
Ok, so I am using home assistant to automatically send myself a message at certain times of the day using the twilio api.
https://home-assistant.io/getting-started/troubleshooting-configuration/
It is all done in the configuration.yaml file, so here is what mine looks like:
notify:
- name: Cody Wirth
platform: twilio_sms
account_sid: AC8a4f2f40331bdad5c95265f2cefe26a2
auth_token: 33a693e18dcad513d4791c51f1071227
from_number: "+16142896777"
automation:
- alias: Send message at a given time
trigger:
platform: time
hours: 24
minutes: 47
seconds: 15
action:
service: notify.twilio_sms
data:
message: 'The sun has set'
target:
- "+16147059227"
Is there anything wrong with my syntax? Is there something I need to configure on Twilio's end to make the messages come through to my phone? Nothing at all is happening when I automate the messages to send.
Ok, so this is the error that it returns:
"17-01-12 08:17:44 WARNING (MainThread) [homeassistant.core] Unable to find service notify/twilio_sms"
To be able to use twilio, you first need to enable/configure the twilio component.
The automation does not configure or start the twilio component, it just uses it.
You can find the configuration documentation on the twilio component page:
twilio:
account_sid: ACCOUNT_SID_FROM_TWILIO
auth_token: AUTH_TOKEN_FROM_TWILIO
After you configured it (and restarted home-assistant), your automation should be able to send notifications over it.