I saw similar post previously but there was no solution provided, resubmitting the same issue here asking for help please.
When signing in DocuSign, most of the time it just times out (spinning circle) or I will get the error below:
dsPrepare is not defined.
This happens when I connect to corporate network but seems ok when i switch to my own hotspot.
Any idea what might be causing the error above?
thanks
Your corporate network may have a filter applied that blocks traffic from certain unknown IP Addresses. This would usually cause regular DocuSign processes from completing successfully. You can ask your IT Team to allowlist DocuSign's domains which are listed here and see if that helps.
Related
I'm trying to create a webhook that updates the envelope on my system, but I'm having this issue:
Docusign Issue
Has anyone ever had something similar?
I took a look about this error and I found a bug with connect from last year where there was a special character in the document causing the error. In one of the examples, there was a newline character in the name of the document which caused the error. I would suggest creating a case on the DocuSign support site for further investigation (support.docusign.com).
An internal issue ticket has been opened on this matter. When you do contact DocuSign Support, please reference issue number EC-4887.
For the past several months I have a native iOS application that uses the embedded signing API to generate an embedded signing URL. My parameter for returnUrl uses a URL with a custom scheme, say, for example, foo. I was using this custom scheme to intercept when the signing is complete and transition to another part of my application. This is now broken and get the following response:
{
"errorCode": "INVALID_REQUEST_PARAMETER",
"message": "The request contained at least one invalid parameter. 'returnUrl' parameter must be an absolute URL."
}
When I try using the schemes http or https the request works just fine. For example:
https://docusign/complete works
http://docusign/complete works
foo://docusign/complete broken
bar://docusign/complete broken
This is in the dev sandbox and I am not aware of this being broken in production. Is this change intentional or a bug? If intentional, why are you breaking the behavior of the client being able to choose their own URL for redirection? Using this custom scheme, I am able to unequivocally determine that my application is responding to a completion event, without having to introspect any other parts of the URL.
This breaking change is a bug that was introduced by mistake. Thank you for your report on it. I'm escalating it.
This issue is now tracked internally as DocuSign IM-32736
Please contact DocuSign customer support and ask them to add your contact information to IM-32736. Thank you.
This bug has now been declared as a release blocker. It will not go to production. The bug is being fixed and tested. It will probably arrive on demo.docusign.net sometime on Friday. I will update this answer as more progress is made.
Update
The bug has been fixed and the fix has been pushed to demo.docusign.net.
Please advise if this is still an issue. Thank you again for reporting it.
I am using sandbox account for docusign everything is working fine. Now I want do this for LIVE account for this I have followed this URL https://developers.docusign.com/esign-rest-api/guides/go-live-steps#review-failed.
While I am going send request to review my AIP transaction. I am getting response Review did not pass.Error in 3rd step. Compliance with [[linkstart]]API rules and limits[[linkEnd]].
Here is a snap shot of error page
https://drive.google.com/open?id=1O7zCfDGHf5YIbZ0EtnWmr7N3hKjvmApG
I have downloaded a error logs. No error found in this log
https://drive.google.com/open?id=1jXxkf53g9_ELsRnEjF44qrMkDpIuV-dt
This review failed due to a known issue in the automated review process (tracked under DCM-3308). In short, the GetEnvelopes call isn't properly tracked, so the review cannot correctly distinguish between valid traffic that complies with the Polling rule and invalid traffic that does not.
For anyone else who encounters this issue (Specifically, with the GetEnvelopes call appearing in the traffic CSV): First confirm your traffic is not polling for the same resource more than once every fifteen minutes, then reach out to go-live#docusign.com: provide your integration key and the CSV of review traffic.
I am using the node-whatsapi library
I am getting the number blocked. I am following the exact protocol as mentioned in the WIKI.
The flow that i follow is:
Create Adapter
Connect()
On Connect - Login
On Login
sendIsOnline()
requestPrivacySettings()
requestServerProperties()
requestContactsSync()
For Each Contact sendPresenceSubscription(), getStatus() and getProfilePicture()
And when i receive a message:
adapter.requestContactsSync('1234567890', 'delta', 'background');
getProfilePicture()
Save to DB
Now, what we do and why do we use WhatsApi
We enable our existing Customers to talk to their internal teams on WhatsApp. So, a customer initates a chat and a help desk team responds to them on an application.
Got the number blocked now. Unable to understand where am i going wrong.
Also, the total number of messages exchanged between the customer and the helpdesk team is around 1k a day.
What you're "doing wrong" is using a third party API which is against WhatsApp's terms of service and, if detected, will get your relevant accounts blocked. It's not a fault with WhatsAPI itself or how you are using it.
WhatsApp openly publishes the only approved/compliant way to programmatically interact with their network.
http://www.whatsapp.com/faq/en/iphone/23559013
http://www.whatsapp.com/faq/en/android/28000012
Outside of that, you are going to get blocked whenever you are detected as using an unapproved means of interacting with their network.
In your particular example you're using a Node.js port of the original WhatsAPI. As of May 2015 this is the kind of pressure they are dealing with from WhatsApp (despite many years of trying to negotiate an amicable compromise with them around things like message limits and identity verification):
It sucks but that's just how it is. You can look at some alternatives which are still actively updated and may continue working for a while, but given that WhatsApp is now owned by Facebook and considering the kind of legal resources at their disposal, you should be able to see why one might be reluctant to continue updating a rogue API.
Well, got a satisfactory answer from WhatsApi collaborator matteocontrini.
Here is the answer that i got, if somebody is intrested.
It says:
the reason of getting blocked doesn't have to be because you wrote
wrong code. It could be a filter on the kind of messages you send or a
report from someone about your number.
I need some advice on setting up merchant account in google.
When I try to set up merchant account, account signing up page shows me an error.
The error code is shown as "An error occurred {"type":"PLATFORM_ERROR", "payload":"0"}"
I've tried to resolve this issue with Google support team, but they keep sending me general information and manual..
Please give me suggestions on this issue. (I already finished developing my commercial application, but can't set the price because of this issue. )
Thanks in advance.
I had the same issue.
What I did to resolve it was to flush the browser cookies, history and cache. After that, I opened a new browser tab and logged in to my Google Wallet account (the one I set up previously to BUY apps on the play store). As I was logging in, I noticed there was some error but it quickly resolved itself - I successfully logged in and could see what I previously bought.
After that, I closed and re-opened my Google Dev Console, and tried to setup a Merchant Account again and it worked.
I experienced the same problem and I finish solved changing my address length, uou can't use more than 64 characters. see https://stackoverflow.com/a/21412790/2359141
clear cache and everything by using ctl+alt+delete
keep only one tab
Select proper product type , I selected Computer software its worked for me
Do sign out and login in wallet google
I found the solution.
You just have to let the VAT number empty during registration, fill it later.
It worked for me.
I got the payload error as well, what resolved my problem was changing my PO Box address to a physical address. Google chat support figured it out.