Unable to install SharePoint Apps

%3CLINGO-SUB%20id%3D%22lingo-sub-168172%22%20slang%3D%22en-US%22%3EUnable%20to%20install%20SharePoint%20Apps%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-168172%22%20slang%3D%22en-US%22%3E%3CP%3ESince%20friday%20we've%20been%20unable%20to%20install%20our%20SharePoint%20App%20(AddIns).%20The%20installation%20fails%20with%20a%20message%20%3CEM%3E%22The%20remote%20event%20receiver%20callout%20failed%22%3C%2FEM%3E.%20This%20happened%20on%20multiple%20tenant%2C%20including%20those%20where%20we%20previously%20could%20install%20the%20app.%3CBR%20%2F%3E%3CBR%20%2F%3EUnon%20investigating%20it%20appears%20that%20Microsoft%20has%20made%20a%20change%20in%20the%20remote%20event%20receiver%20request%2C%20causing%20%3CEM%3ETokenHelper.cs%3C%2FEM%3Eto%20fail%20because%20the%20%22intended%20audience%22%20is%20not%20valid.%20This%20is%20because%20the%20request%20has%20changed%20format%20of%20the%20url%2C%20adding%20%3CEM%3Eazurewebsites.net%3C%2FEM%3Eto%20it%20(or%20whatever%20host%20you%20are%20using).%3CBR%20%2F%3E%3CBR%20%2F%3EI%20found%20the%20following%20fix%20until%20we%20know%20more%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EAdd%20an%20application%20setting%20called%20%22HostedAppHostNameOverride%22.%3C%2FLI%3E%0A%3CLI%3EIf%20your%20app%20is%20located%20at%20myapp.azurewebsites.net%20then%20set%20the%20value%20to%20%22myapp%3Bmyapp.azurewebsites.net%22.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EIf%20anyone%20knows%20more%20about%20this%2C%20please%20share!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-168172%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-168385%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20install%20SharePoint%20Apps%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-168385%22%20slang%3D%22en-US%22%3EYep%2C%20many%20customers%20are%20having%20this%20problem%20and%20while%20there%20are%20some%20workarounds%20described%20in%20GitHub%2C%20you%20could%20face%20under%20a%20scenario%20that%20is%20not%20covered%20by%20this%20workarounds%3A%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FSharePoint%2Fsp-dev-docs%2Fissues%2F1409%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2FSharePoint%2Fsp-dev-docs%2Fissues%2F1409%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-168227%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20install%20SharePoint%20Apps%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-168227%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20ran%20into%20this%20issue%20as%20well.%20There%20is%20already%20another%20topic%20on%20this%20issue%3A%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSharePoint-Developer%2FInvalid-issuer-o-signature-error-in-SPO-Provider-Hosted-AddIns%2Fm-p%2F165204%2Fhighlight%2Ffalse%23M4433%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSharePoint-Developer%2FInvalid-issuer-o-signature-error-in-SPO-Provider-Hosted-AddIns%2Fm-p%2F165204%2Fhighlight%2Ffalse%23M4433%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Since friday we've been unable to install our SharePoint App (AddIns). The installation fails with a message "The remote event receiver callout failed". This happened on multiple tenant, including those where we previously could install the app.

Unon investigating it appears that Microsoft has made a change in the remote event receiver request, causing TokenHelper.cs to fail because the "intended audience" is not valid. This is because the request has changed format of the url, adding azurewebsites.net to it (or whatever host you are using).

I found the following fix until we know more:

  • Add an application setting called "HostedAppHostNameOverride".
  • If your app is located at myapp.azurewebsites.net then set the value to "myapp;myapp.azurewebsites.net".

If anyone knows more about this, please share!

 

2 Replies

We ran into this issue as well. There is already another topic on this issue:

https://techcommunity.microsoft.com/t5/SharePoint-Developer/Invalid-issuer-o-signature-error-in-SPO-...

Yep, many customers are having this problem and while there are some workarounds described in GitHub, you could face under a scenario that is not covered by this workarounds: https://github.com/SharePoint/sp-dev-docs/issues/1409