In some cases, a certain requested permission may not be required for your app to function. In this case, the simpliest thing to do is to respect permission decline and continue to lead them into the app. But since the person declined that permission, Flick Finder just presents more generic recommendations.
This is the simplest option, and provides a great respectful experience to people who choose to decline certain permissions. People may decline a permission because they don't understand why your app needs that information. In this case, your app could display a dialog explaining why you need the information and how it'll be used to enhance the experience. In the example below Flick Finder displays a dialog explaining that with an email address, the app can send you updated when new movies become available.
Note that in this example, the person still has the opportunity not to grant the email permission. This strategy can be used for permission which is critical or highly desirable for the functionality of your app. In this example, Flick Finder wants to collect a person's birthday so it can recommend age-appropriate movies.
If a person has declined to share their birthday when they logged in with Facebook, Flick Finder can still create a place to collect the information inside the app, separate from the Facebook Login flow. Found it The method was failing because context. Email, "Facebook" ;. Improve this answer. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog.
Does ES6 make JavaScript frameworks obsolete? Podcast Do polyglots have an edge when it comes to mastering programming Featured on Meta. Now live: A fully responsive profile. Linked 3. Related Hot Network Questions. Did this problem crop up recently? You might be able to address the issue by following the steps in the KB article.
As a first step I'd recommend adding the aspnet:UseHostHeaderForRequestUrl configuration variable mentioned in the beginning of the article, particularly if you're relying on a third party library. Otherwise you may have to look further into the way your application generates the URL. If that doesn't help, feel free to send over more information about where the logic responsible for that resides in your repository if you'd like me to take a closer look.
By the way, also take a look at this recent discussion regarding a similar issue. Discussions are closed to public comments. If you need help with AppHarbor please start a new discussion. This discussion is private. Only AppHarbor support staff and members of AppHarbor can see and reply to it.
0コメント