We are getting the errors while working with the client/contracts when managing it with API’s
Here is the scenario that we are facing:
We have an Api that we have created and added a contract to it:
Upon checking of API Contract, we are getting the following error:
Contract API Error
But the same with given endpoint is working fine while working it with key/client app using programmatically in our application, But when we are checking it with client's menu,
White Page Error
we are having totally blank white page ahead
Bug reports relating to Apiman should be filed in the "issues" section on the GitHub Apiman repository: https://github.com/apiman/apiman
The 'discussions' section is also available for more general help questions and topics if you are struggling with your configuration or migration (i.e. not really within Stack Overflow's area).
(Disclosure: I am Apiman's principal maintainer).
Related
I am a dev trying to make a whatsapp based relationship management system. I had successfully submitted 3 templates but from about 2 weeks now cant seem to get my new templates approved. They are rejected with a commerce policy issue but I am clueless.
This is one of the rejected templates based on commerce policy
Just want to know any of you guys face the same problem and have you found any work around.
Resubmitting, adding samples did not work. Still waiting for a response from Meta.
Thank you fellow devs
I am trying to understand what the problem is and what template text format meta like, so I can get my templates approved
So this has been such an annoying issue I've been having with facebook.
We :
created a messenger app
verified the web-hook
submitted the app for review
got approval from Facebook
Everything works perfectly if we use the developers and users associated with the app, but for some reason any other user will not work at all!
The only explanation I see why it isn't work is because the app is in development mode, but apparently facebook removed that and replaced it with Access Levels.
I've been looking at documentation and can't find anything! Any directional help that I may have missed would be greatly appreciated!
The only explanation I see why it isn't work is because the app is in development mode, but apparently facebook removed that and replaced it with Access Levels.
You are indeed completely right!
The old system, consisting of Development Mode and Live Mode, has been replaced by respectively Standard Access and Advanced Access (cf. this documentation).
Apps in Development Mode can only request Permissions from app users who have a Role on the app or in a Business that has claimed the app. This is the same as Standard Access. Apps in Live Mode can request Permissions from anyone, but only if the Permissions have been approved through App Review. This is the same as Advanced Access. Features, although they cannot be requested from app users but are instead active/inactive, behave the same way.
This snippet was taken from this post.; Side note: They even wrote a paragraph about why they decided to switch and which features/improvements the new update brings - it's on the same site, just below the quote above
Anyhow, due to logistic reasons (supposedly) the update is only being pushed gently into the broad mass:
Access Levels are gradually being applied to all existing Business apps automatically.
You can find the banner on the previously mentioned site:
Summing up: Yes - the modes are actually replaced by their new "level system", though the update might haven't covered your Business app yet (but will so in the near future).
I got this message from API, maybe this covers the reason:
"(#10) Cannot message users who are not admins, developers or testers
of the app until pages_messaging permission is reviewed and the app is
live.", "type":"OAuthException", "code":10, "error_subcode":2018028, "fbtrace_id":"AL....i9"}}
I have installed the Google assistant service by following the guide in the official documentation. Now, I want to add custom actions in the SDK.
Just to test, I used the same action and code they have given. But, as it runs, it just says Sorry, your app is not supported on this device . I then wandered around in the troubleshooting page to find out that this was already addressed by Google. They have mentioned just about the issues caused due to triggering surface capabilities related to the screen ON. But in my case, all the surface capabilities are turned OFF. But, I'm still facing the same issue. Can anyone please help..?
I am dual-posting this here while I wait for DocuSign support to get around to assisting in the hopes someone here has some more insight.
Our application uses the DocuSignConnect API to manage brands. It has been in production for years and worked without issues. Sometime last week, our API calls to create brands began failing, but only on the Demo system. This functionality is continuing to work fine in the Production system. There are no code differences between our Demo and Prod environments.
In the past, we have seen issues (of a different kind) when changes are rolled out to the DocuSign Demo system. I wonder if this could be one of those scenarios.
The details are limited. Our API calls to create a brand are met with a failure with the following properties:
ErrorCode: 309
ErrorReason: Brands could not be created.
faultString: Brands could not be created. Unable to upload brand, error: Must specify valid information for parsing in the string.
As I mentioned above, our application has not changed recently with respect to the DocuSignConnect API. I have noticed, however, that the Signing and Email resource xml files appear to be undergoing a change (they differ significantly between DocuSign's Prod and Demo sites.) Perhaps this is a clue behind the fairly unhelpful "...specify valid information for parsing..." message.
My concern is that something is soon to be deployed to Production that will break our application.
I should add that our other API calls seem to be ok (sending envelopes, for example)
Has anyone experienced this type of problem creating brands?
The update on this from DocuSign support is that the 'type' attribute on the 'logo' element that is part of the XML schema defined in the 'CreateBrand' API call has changed from optional (in their PROD environment) to required (in their DEMO environment).
They are probably going to be changing their DEMO code to revert this attribute back to 'optional' before it is deployed to their PROD system.
But in any event, our code is going to change to start including the 'type' attribute on the 'logo' elements to ensure success going forward regardless.
I understand this isn't a typically appropriate question for Stack Exchange but the Nest customer service has basically no information whatsoever on developer support, and the Works with Nest support contact form recommends using Stack Exchange tagged with nest-api. Anyway, I have created an application in the developer portal I need to submit for a user limit increase, and I have been unable to submit the form for the last 3 days. I receive a generic error that says:
We're sorry. Something went wrong. Please try again later. The backend responded with an error
As I said, I contacted every customer support outlet Nest offers and have yet to get any assistance. If anyone has encountered this error or has the proper avenue to reach out to Nest's developer support team, please let me know. Thank you in advance, again I apologize for the narrow scope of this question.
If anyone else runs into this issue, my final resolution was to re-create a second application on a different developer account, and then migrate my web service to use the new application's client secret, API tokens etc.. Albeit a huge hassle, the submission (using the exact same form data as before) worked on the new application.