Sharepoint-hosted app on-premise 2013

Question

We have been developing SharePoint-hosted apps for SP online with great success, but seems like developing SharePoint-hosted apps for the on-premise 2013 is not so intuitive process.

Questions:

1. As a rule of thumb, should we NOT create sharepoint-hosted apps on the on-premise?

2. For every new deployment version, unless users go to Site Content and Trust the app, it wont appear on the with X-Frame-Option = SAME ORIGIN error. Note that all of my ClientWebParts include the AllowFraming tag. We also use plenty of the AppContextSite Lists. Isn't there any way to set my app as trusted, so that any user visiting the page hosting the AppPart, be able to see the content of my app?

   • None of this issues exist on the online version and i was wondering if the sharepoint-hosted apps are not meant to be deployed on the on-premise.

** This thread is based on another thread i raised recently, but I thought to create a new one for narrowing the problems I have! Do not down-vote for duplication ! https://sharepoint.stackexchange.com/questions/115708/sharepoint-hoted-apps-for-sharepoint-2013-x-frame-options-error

UPDATE 1: point 2 revised

In point 2 I mentioned that my app requires Trust from all users. The correct is that the app requires login from all users visiting Site Contents before they can view it on the page. Here is the revised point 2.

2. For every new deployment version, unless users go to Site Content open the app and insert their credentials, it wont appear on the page with X-Frame-Option = SAMEORIGIN error. Note that all of my ClientWebParts include the AllowFraming tag. We also use plenty of the AppContextSite Lists. Isn't there any way to login without going to the Site Contents or event better to use the Site credentials and login directly without extra effort from the user?

Answer 1

1. Yes, SharePoint-hosted app can possibly be created in on-premise environment.
2. To trust an app is meant for one time at the time of installation of an app.

What type of user is trying to visit your page containing the clientwebpart? Do the users have read permission to visit your page?

Try to first publish the app having read permission at site collection level and then upload to app catalog and install at a specific site. Then try to visit the page with another user permission. The only possible obstacle that can occur is it will require your credendials once again to visit the page where client webpart is stuck into it.