1

I've built and been using a Sharepoint hosted app which uses a Client side people picker which all worked correctly until today. No when using them I get the following error.

There is no trusted URLs configured for the app deployment.

I have made no code changes in the last week so can only assume there is an issue with SP2013 online? Anyone else seen this?

  • This part is still in your Manifest I guess? <AppPrincipal> <Internal AllowedRemoteHostUrl="~remoteAppUrl"/> </AppPrincipal> – Robert Lindgren Feb 26 '14 at 17:12
  • Yeah i have that in place...for Sharepoint hosted we use. – Stephen Feb 26 '14 at 17:12
  • for Sharepoint hosted we use. <AppPrincipal> <Internal /> </AppPrincipal> – Stephen Feb 26 '14 at 17:18
1

For Posterity the workaround to fix this is as follows.

// Old Method which gives the above error
var executor = new SP.RequestExecutor(appweburl);
// Workaround as suggested by Microsoft
var executor = new SP.RequestExecutor("/");

This will get things back up and running again until Microsoft resolve the issue.

Regards,

S

UPDATE: The lastest advice from MS is

'This is currently a known issue in the SPO environment and is being investigated and looked into. The work around you have to change the URL to lower case is mentioned and you can continue using it till a fix is applied.'

... the to lower-case workaround being:

var executor = new SP.RequestExecutor(appWebUrl.toLowerCase()); 
1

I was playing with some sample app code and came across this same issue, but mine is a little bit different:

var factory = new SP.ProxyWebRequestExecutorFactory(appWebUrl.toLowerCase());

In any case, adding the toLowerCase() method allows the code to execute properly.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.