Where:
In build -> Actions -> Upload content via Google Sheets
Problem: I have the trivia template selected. I've already created a sheet and uploaded and deployed my action. Now I figured out that one of my questions had a wrong answer. So I updated the sheet and then went back to the actions tab to upload content via google sheets
Then I clicked on UPDATE TEST and tested my app in the simulator. The changes were reflected.
Then I clicked on UPDATE PROD and I get the following message
On doing further investigation I found out that the GET request is returning a 403 error
and in the Network tab, this is the response I'm getting:
I'm not sure what is going on.
I have encountered the same situation.
However, there is a workaround or it must be the right action when upgrading your Q&A Sheet. It is to use "submit for production" in Deploy>Release sidebar. See [attached image].1
I also had the same problem. I think you have changed the Google Sheet's name and questions per page, so it gives an error. If you give the same name and questions per page it is taking i.e. updating.
Related
Keep receiving “(my app name) isn't responding right now. Please try again soon” on my actions on google simulator, I’ve tried almost all the solution that I found on the internet and ended up with this, I decided to copy the code from google https://developers.google.com/assistant/df-asdk/helpers#calling_the_helper it works just the permission one , for the permission handler it doesn’t work it seems like if I do not put the default response in dialogflow It wouldn’t work so I don’t want that default response because it keeps saying that response, and when I removed it , it gave me an error ,but in the debug tap it shows everything(display name, location etc.)
I am importing/creating drafts in Gmail using the Gmail API. After creation I'd like to redirect the user to the Gmail UI with the opened Draft in the composer window.
I made it work properly for https://mail.google.com/mail/#drafts?compose=[MESSAGE ID]. Other urls I found here also worked well. Gmail is doing some redirects and eventually the composer window is opened with the draft.
Now my issue:
If the user has not enabled "Conversation view" this will not work at all. The redirect will then result in https://mail.google.com/mail/u/0/#drafts?compose=new and only an empty, new composer window is shown and a new draft is created by the UI.
If I open the draft directly the ID-format is different. https://mail.google.com/mail/u/0/#drafts?compose=hJzgZpSqgLQcCWgZqnlNRzRBfMbjZVnZklzvcFxhQCdwT... and I have no idea if this format can be generated somehow.
Does anybody has an idea or experience to also make it work with this UI setting. How I can force Gmail to load the draft into the composer window?
Thanks in advance.
If you have Email Threading > Conversation View enabled
Make use of the following URL
https://mail.google.com/mail/u/0/#inbox?compose=DRAFT_MESSAGE_ID
If you have disabled the Email Threading > Conversation View option
Make use of the following URL
https://mail.google.com/mail/u/0/#inbox/DRAFT_MESSAGE_ID
Additional information
The main difference between them is that the first is treated as a conversation while the second example is not.
You can use #drafts instead of #inbox in the URL.
The number after .../mail/u/ is the session you have opened
You can retrieve the DRAFT_MESSAGE_ID by making a request to the API
You can approximately generate the compose ID by yourself, there are some examples out there (not recommended). I strongly recommend you to use the DRAFT_MESSAGE_ID instead.
This appears to still be an issue the one solution I did find was that you can find your draft directly (even though it would be the last draft) and go through multiple accounts by redirecting to
https://accounts.google.com/AccountChooser?authuser={user account}&Email={email account}&continue=https://mail.google.com/mail/#search/rfc822msgid:CAMU-31NcJCVHyGNsAycRKfuS0nMonoaZ6wFMD90Sej996qjuPQ#mail.gmail.com
You need to get your message id toi replace the area from <> from your draft. So you'll have to create the draft first. Get the google message ID, then use that with messages/get to get the Global Message Id (also referred to as message id) and then use that with a search. At this point you'll open a page with a search to a single draft but it will not be opened. Your users will have to click on the one message. Unfortunately there does not seem to be a way to have the good way work for conversation view, and this way work for non.
I tried many different URLS and nothing worked. As noted in the original question, it might work that you could link to the full URL but I see no way to get that. If you spend long enough working with an email you'll even find that ID changes so they aren't even stable within a single day.
Another solution that could work is as explained:
https://mail.google.com/mail/u/0/#inbox/DRAFT_MESSAGE_ID
But as noted this does not open the draft on the first time you go there. It seems you have to travel to that link 2 times in a row to get the message to appear. I guess you could go to the page maybe inject some javascript to go to the page again but I don't know how to do that.
The problem is that in Manage Clients at https://www.instagram.com/developer/clients/manage/ client was created,
but it became invalid, the id did not work, i.e. instagram disabled it, the inscription was disabled.
We decided to delete the old client and create a new One, but instagram does not register it. The line of consent and the captcha does not issue. Respectively writes 2 errors:
1.Incorrect Captcha. Try again.
2.Error sending: fill in all required fields.
How can this be corrected?
I've had this same issue, and haven't been able to get anywhere with it. The support page for Instagram says to report a bug using the "Report Bug" button on the Developer Dashboard (http://instagram.com/developer/clients/manage/). If you click that button it takes you to a form that asks if you want to report a bug for the old API or new API. If you select the old API it says "we're not taking bug reports for the old API", if you select new API it takes you to Facebook's developer support page. I created a ticket there, and they told me I had to report it through Instagram's support links. WTF?? That's what I did .....
Anyways, the problem is related to a bunch of javascript errors on that client registration page. I first encountered this problem about 3-4 weeks ago, and it's still around. Feels like IG really doesn't give a crap about their developer community ....
We are using docusign for more than 3 years, We have several demo accounts as well as we have paid account too.
we are using the following docusign rest service
https://demo.docusign.net/restapi/v2/accounts/*****/envelopes
In our local environment we are using the above demo rest service, Till last month (August) we were able to post the document into docusign without any issues. The Problem now is that we are not able to post a document to docusign.
we getting the exception like
"errorCode": "UNABLE_TO_LOAD_DOCUMENT", "message": "Unable to load the document. Unable to load Document(1;CONSENT FORM). Error: Cannot add the widget (connected to field: ColombiaCurrentlyresideYes) to page -1, because it's already added to page -1. If you want to re-use this widget, please remove it from the current page first
Same data worked till last month (August) and it's working fine now in docusign production account(paid). we are not sure what went wrong in demo accounts. Any release are done in demo accounts?
I tired using the same template in web console too, same error throws in browser console
Please help me to resolve this issues.
We require your guidance regarding this issue!
I suggest first trying to load the documents into an envelope by using the DocuSign Web tool (NDSE). If that doesn't work then the document is the issue.
Has the document changed?
Re changes: Yes, the demo system is changed each month. Then the changes are applied to the production systems. While we do have thousands of automatic regression tests, problem can creep through the system.
I suggest you contact DocuSign customer support to give them the document which is failing to load.
Background
I have an ASP.Net Core v2.0 web application that has the [HttpGet] attribute above action results that don't need to accept a post.
I created a spreadsheet with a list of pages on the website to my marketing team, along with a column of hyperlinks that link directly to each page on the website.
Example Spreadsheet:
Issue
Once the marketing team started clicking on the links in the spreadsheet, I started to receive 404 errors via email (configured using NLog) although the page did still load for the user.
Troubleshooting
I troubleshooted this and uncovered that the issue was down to the [HttpGet] attribute. If I take the [HttpGet] attribute out, clicking on the links in the spreadsheet doesn't generate a 404 error.
The site doesn't generate 404 errors when loading the page (s) via the browser.
I installed fiddler and it looks as though Excel is using the "CONNECT" method.
Fiddler screenshot:
I thought this could be the issue as it's not a GET but when I access a page within Chrome, it also shows using the "CONNECT" method in fiddler.
I'm looking to see if anyone else has had this issue and if they got around it? Do I need to add another attribute alongside [HTTPGet] to stop Excel or other 3rd party software causing a 404?
I've resolved my own issue.
For anyone else that has this issue the fix is to put [HttpGet, HttpHead] as the attribute. If you have a custom route then add another attribute underneath:
[Route("[controller]/custom-action")].
For info, I got to the bottom of this by using the logs from the drop down ASP.Net Core Web Server in the output window in Visual Studio. I could see that when the link was first being requested by Excel, it was using the HEAD method rather than the GET which is why a 404 error was being fired.
Hope that helps someone down the line.