Getting a error while updating an existing app(WP8SL app) in the store saying "There is a CN mismatch between the authenticated push notification certificate associated with your app and the one in this update". We using new MPNS certifcate for update.
Please help, do we need to change some thing in the app client code/manifest or in the certificate.
Found the ans.
Below is a msdn forum link.
https://social.msdn.microsoft.com/Forums/en-US/b1ebe4da-9eed-45bd-a82f-d32596998102/error-updating-the-wp8-sl-app-cn-mismatch?forum=wpdevelop
Related
[{error: 'idpiframe_initialization_failed', details: 'You have created a new client application that use…i/web/guides/gis-migration) for more information.'}
details: "You have created a new client application that uses libraries for user authentication or authorization that will soon be deprecated. New clients must use the new libraries instead; existing clients must also migrate before these libraries are deprecated. See the Migration Guide for more information."
error: "idpiframe_initialization_failed"]1
i do not know why these mrfkers software engineers are not fixing their sofware properly we are getting many errors while installig the software.they should leave the job if they do not know how to code..and there are many errors if we are trying to use google login API for our project i do not really like the rules of google and the software developers and engineers of google...but i do really like Facebook coz there is no restriction we can easily use Facebook login Ai for Our Application..
I have just followed the tutorial video here:
https://www.youtube.com/watch?v=QOm0dHgwvbM
And after starting a trial on a newly-activated Forge account, have I thought followed every step in the .NET instructions to the letter.
However, when I run the application, and attempt to upload a file, I receive the following error on the Console:
An unhandled exception has occurred while executing the request.
Autodesk.Forge.Client.ApiException: Error calling GetManifest: { "developerMessage":"The client_id specified does not have access to the api product", "moreInfo": "https://forge.autodesk.com/en/docs/oauth/v2/developers_guide/error_handling/", "errorCode": "AUTH-001"}
Does anyone have any suggestions on how to remedy this?
Thanks,
Alex.
Did you select the Model Derivative API while creating an app in https://forge.autodesk.com/myapps? If not, please go there, then edit the app, select Model Derivative API, and save the change. Afterward, restart your .NET app to fetch a new access token.
ref: https://petrbroz.github.io/forge-samples-docs/#provision-access-in-other-products
So, it turns out my issue stemmed from having previously setup a FORGE_CLIENT_ID and FORGE_CLIENT_SECRET system variables on a previous, unsuccessful trial of Forge. This meant that the Visual Studio solution I created was reading those values instead of the ones I had input in code. Thanks to Cyrille Fauvel of Autodesk for helping me figure this out.
Cyrille says he is going to feed back to the rest of the Forge team that they ought to report back on the console the details of both ID and SECRET to prevent this happening in future.
I'm attempting to connect to Office 365's Exchange Web Services, but it keeps coming up with a 404 error. I'm pretty sure the issue is with the credentials, but I seem to lack the knowledge to resolve it.
I performed a test via testconnectivity.microsoft.com (Service Account Access test under the Office 365 tab) and it is also getting a 404 error. I know from searching online that the format of the credentials is a common problem, however it is in the 'user#company.com' format.
I think the problem may have something to do with the domain or that the authentication goes through my company's server. For example, if I log into outlook.office365.com with the 'user#company.com' format, it forwards me to my company's log on portal (I believe this is a typical setup). In order to log in, I first have to change the user name from the 'user#company.com' format to 'user#domain' or 'domain\user' (the domain is different from the company name).
My question is, since the authentication goes through my company's server, do I need to authenticate to Exchange Web Services in a different manner? (Currently I'm using a WebCredential)
Alternatively, if my company's portal were to accept user#company.com as a valid user name, would that allow me to connect to EWS using a WebCredential?
This is the code I'm using for the connection, however I don't think it is the problem given that Microsoft's test site was also getting a 404 error.
service = new ExchangeService();
service.Credentials = new WebCredentials("user#company.com", "password");
service.Url = "https://outlook.office365.com/ews/exchange.asmx";
I am trying to get access token using WebAuthenticationCoreManager for my native UWP application (Windows 10), am using https://www.onenote.com as the resource.
Before requesting for the token I have associated my app with azure and using client id generating from it.
I have also provided necessary delegated permissions for office365api to my application on azure.
I am getting error with code AADSTS65005 with a message "he request has failed because the client has not specified this resource in its requiredResourceAccess list".
Am I missing some steps that needs to be followed?delegated permission snapshot
The resource URI is https://onenote.com/
Please try with that.
I've created my app and SQL container on Google App Engine. All is ready to go, I just need to grant network access to the SQL server from the application. When clicking the Add Item button, then entering the Application ID (I verified through what appears to be an ancient deprecated interface) then clicking save I get the following error:
Could not complete the operation. Dismiss
I've read the instructions and as far as I can tell this is the correct method. It's the same region as the App. Tried us-east and us-west.
I created another SQL instance just in case with the same results.
I checked the dns records of the provided application URL and added the 4 IPv4 and IPv6 addresses that were returned just in case I could do it that way. The app still can't connect to the database.
I'm not sure what to try next, does anybody have an idea how to allow access in this situation?
I created my Project in US-east1 originally, had the same problem as above. Went back and created another project in US-central. This problem "Could not complete the operation. Dismiss" went away. Easy way to tell that it is working, the "Preferred location" will auto populate with "Follow App Engine app", the "App Engine application id" will auto populate with your project app id, the "Authorized App Engine applications" will auto populate with the project app id as well.