App manifest links
path (/.*)
Users will not go directly to your app from links associated with this path, but will see the app picker or be directed to the web browser. Once you have fixed these issues and published a new version, users need to update their app before the links will work.
Domains
error
Domain non-redirect failed: Ensure your domain is accessible without any redirects for all of the failed website domains
error
JSON content type failed: Make sure the content type is "application/json" for all the failed domains
Because of above errors my app is just opening in home page instead of desired web path link please help me by guiding its solution..
Related
I am going through the kentico11 developer essential training and the first requirement is to setup a kentico11 site. I followed the instructions and when done this is all I get
Error Message:
Either the website is stopped or the requested domain name is not configured for any website: http://localhost/Kentico11/CMSMessages/invalidwebsite.aspx
If you're an administrator of this site, you need to go to Sites and make sure the following domain name is configured either in the site properties or a domain alias of a running web site: localhost
How do I proceed? I applied the license in the training package
Once you have added the license for the domain you are using to run the site, you need to add the domain to the Site domain name field in the Sites application in Kentico.
Open the Sites application.
Edit (pencil icon) the site.
Type the domain into the Site domain name property on the General tab - since you are running the site under localhost, simply add localhost to the field.
Click Save.
Now when you visit the homepage, the error message should no longer appear.
Documentation reference:
https://docs.xperience.io/k11/configuring-kentico/managing-sites/setting-domain-names-for-sites
My problem is similar to this one. But I need to make one step further.
I whant to publish my website webview on google play. Google Play have rejected my submission but after I send them a email they respond and said that they will allow app publication if I send them pdf with distribution agreement, authorization contract, website domain information or something like that prooving my website ownership. My website hosted on azure. I have domain name like xxxxx.azurewebsites.net. Please help me to understand how can I make pdf document that prooves my website owership.
Will be very greatfull for help!
First, about how to verify your Azure Website ownership, you can refer to these Google documents as below.
Handling Android App Links
Secure and specific: Android App Links use HTTP URLs that link to a website domain you own, so no other app can use your links. One of the requirements for Android App Links is that you verify ownership of your domain through one of our website association methods.
and
Add verification for your deep links: Configure your app to request verification of app links. Then, publish a Digital Asset Links JSON file on your websites to verify ownership through Google Search Console. Learn more in Verify App Links.
Verify Android App Links
To verify ownership of both your app and your website, the following steps are required:
Request automatic app link verification in your manifest. This signals to the Android system that it should verify your app belongs to the URL domain used in your intent filters.
Declare the relationship between your website and your intent filters by hosting a Digital Asset Links JSON file at the following location:
https://domain.name/.well-known/assetlinks.json
The section Verify your website of App Indexing on Google Search in Play Console Help introduces the steps
Sign in to your Play Console.
Click All Applications All applications.
Select the application you'd like to verify.
On the left menu, click Development tools > Services & APIs.
Under "App Indexing from Google Search," click Verify website.
Type your website address.
Click Verify.
Go to Google Search Console.
On the left menu, click All Messages.
Open the verification request message (example: "Google Play: Link http://www.yourwebsite.com to android-app://example.com.yourpackage.name").
Click Approve the request.
Review the information and click Approve. Once approved, your app will appear on the
Search Console Home Page for your account. Be sure that your app enables deep links.
If you have a Google Search Console account or not, here is two links of Verify your site ownership of Search Console Help for old and new Search Console will be helpful.
Tip: Only Google Search Console users with "Owner" permissions can view and approve site verification requests. If you don't see your site verification request, make sure you're signed in using an account with "Owner" permissions.
Second, the xxxx.azurewebsits.net is just a subdomain of azurewebsites.net which be registed by Azure and you can lookup the related info via https://www.whois.net/ as the figure below, so it's not belong to you.
Therefore, you need to register a domain name like abc.com in the Domain Name Registrar like GoDaddy or others, and add a CNAME record with it into DNS server like Azure DNS, then to follow the above steps required by Google to verify your website ownership and collect the necessary information to make a PDF document to send to Google.
I am working on Azure App service API apps.
I followed the steps available in the below link, for implementing user authentication concept to the ToDoListAngular project and successfully deployed in azure, but when i test with the ToDoListAngluar project azure url to add the todoitem it shows error on Google Chrome Address bar "This page is trying to load scripts from unauthenticated sources".
https://azure.microsoft.com/en-us/documentation/articles/app-service-api-dotnet-user-principal-auth/#overview
Please tell me how to resolve the above error.
It sounds like one of your API Urls does not have https:// at the beginning.
My best bet is the "toDoListAPIURL" in your front end site's application settings on the portal. There are a ton of API urls in the source code to check if that doesn't do it. Going back through the getting started tutorial should have them all.
I'm developing a site on a shared hosting company (asp.net/c#). I'm on a Windows 2012 server. I'm using IIS7. I'm trying to install blogengine.net, which requires the app_code folder to have write permissions.
I can find nowhere in my control panel where it lets me grant write permissions anywhere.
Likewise, I see no option for this in IIS7.
Can anybody offer me guidance on how to grant write permissions to the app_code folder if I'm with a shared hosting company? Thanks!
Here's what my shared hosting control panel looks like. But I thought there would be a way to grant write permissions via IIS7:
EDIT:
Here's my specific error:
HTTP Error 404.0 - Not Found
The resource you are looking for has been removed, had its name changed, or is
temporarily unavailable.
Most likely causes:
The directory or file specified does not exist on the Web server.
The URL contains a typographical error.
A custom filter or module, such as URLScan, restricts access to the file.
Things you can try:
Create the content on the Web server.
Review the browser URL.
Create a tracing rule to track failed requests for this HTTP status code and see which
module is calling SetStatus. For more information about creating a tracing rule for
failed requests, click here.
Detailed Error Information:
Module IIS Web Core
Notification MapRequestHandler
Handler StaticFile
Error Code 0x80070002
Requested URL http://domain.org:80/blog/account/login
Physical Path E:\web\controlpanelusername\htdocs\blog\account\login
Logon Method BlogEngine.NET Custom Identity
Logon User Anonymous
I just got an answer back from the hosting company and here's what they said:
"Your IIS and aspnet users are granted full set of permissions on your site root and all subsequent directories by default. Your and your web applications should be able to write to any directory. The permissions of those users cannot be altered, and that's why they are not listed in permissions manager. Permission manager is for additional users that you create in User/Quota Manager only. "
For anybody who has a similar issue, this may be a solution:
I had an IIS7 rewrite rule that was removing .aspx extensions. So if I went to domain.org/about.aspx, it would rewrite to domain.org/about
This was messing up the application I was trying to install. Removing this rewrite rule solved my issue.
I have a domain at http://qotr.net that I'm trying to set up as an app so that I can use OAuth. It was set up a few weeks ago, and we just now finished implementing the OAuth hooks on our application, when Facebook started giving us errors.
Now, when I go to the settings page, and edit anything, I get:
Error
App Domain: qotr.net is not a valid domain.
Site URL is not a valid URL.
I have: qotr.net for the app domain and http://qotr.net for the site url.
http://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fqotr.net
Tells me that it can't parse qotr.net. The site is clearly up and usable, and Google OAuth works.
I can't find anything online on why it might not parse correctly; any ideas?
in the App Domain, enter your site domain without the http:// or the www. Just put in, say for my website iamzang.com
For the site URL below the page, enter http://iamzang.com/
That will do the trick. I got the same error before and with this the domain is no longer invalid.
You need to add a platform first. There you enter the full domain, e.g. http://www.yourdomain.com.
Then set the App Domain to yourdomain.com!
On facebook app registration page, under Settings -> Basic -> Basic Info try entering both domains in the App Domains space (with and w/o www)
Don't write anything in the App Domain under "Basic Info". Instead under "Select how your app integrates with Facebook" click on the check: Website with Facebook Login, which will give you a space to write in your website url (http://qotr.net).
I just got this working by using 'domain.com' in the App domain field & 'http://www.domain.com' in the Site URL field.
Hope that helps.