SharePoint Hosted Add-ins are hosted inside SharePoint environment, it uses SharePoint JSOM code (JavaScript Object Model) to access list/library items in add-in web or Host web.
They can contain SharePoint lists, Web Parts, workflows, custom pages, and other components, which are usually installed on a subweb, called the add-in web, of the Host SharePoint website where the add-in is installed.
Here are some common issues customers encountered for SharePoint hosted Add-ins:
I. Sharepoint hosted app not working after publish.
The Sharepoint hosted add-in works okay when deploy with F5 from Visual Studio, but after publish and add it to App Catalog, try to add it to Site, get error says: “The page can't be displayed, make sure web address is correct”,
Sometimes, the error is:
Fiddler trace shows:
The cause of this is the app’s URL cannot be resolved with DNS.
The solution is to set up the app domain in DNS and creating a forward lookup zone and a CNAME alias (because each app web's URL will contain a unique hash). These steps are described in detail in this TechNet article.
II. Problems only when host site’s Web Application is Host Header Web Application:
There are various kinds of symptoms of this category, for example,
a. 404 Not Found
Fiddler trace shows:
b. Blank page
c. HTTP 403 Forbidden:
In IE:
In Chrome:
d. Multiple Line of Text field in Add-in web (app web) is blank in form pages:
If the Add-in works in a non-host header web application, verify following configurations:
1. A SharePoint Web Application without host header on default port (80 or 443 depending on whether the hosting web application is on SSL or not).
I will call this Web Application “PlaceHolder Web Application” in this article.
