eriksendc
commented
5 years ago Since submitting my original issue yesterday I tested this and proved that this is an issue with the "File New" experience. If you create a new ASP.NET MVC app and enable Facebook, I'm getting the exact same results... desktop / laptop is fine, but signing in with the Facebook button from /Identity/Account/Login doesn't work. The versions of things from my "File New" test and the updated startup.cs code to enable Facebook is below.
public void ConfigureServices(IServiceCollection services)
{
services.Configure<CookiePolicyOptions>(options =>
{
// This lambda determines whether user consent for non-essential cookies is needed for a given request.
options.CheckConsentNeeded = context => true;
options.MinimumSameSitePolicy = SameSiteMode.None;
});
services.AddDbContext<ApplicationDbContext>(options =>
options.UseSqlServer(
Configuration.GetConnectionString("DefaultConnection")));
services.AddDefaultIdentity<IdentityUser>()
.AddRoles<IdentityRole>()
.AddEntityFrameworkStores<ApplicationDbContext>()
.AddDefaultTokenProviders();
services.AddAuthentication()
.AddFacebook(options =>
{
options.AppId = Configuration["Authentication:Facebook:AppId"];
options.AppSecret = Configuration["Authentication:Facebook:AppSecret"];
});
services.AddMvc().SetCompatibilityVersion(CompatibilityVersion.Version_2_1);
}
PackageReference Include="Microsoft.AspNetCore" Version="2.1.3"
PackageReference Include="Microsoft.AspNetCore.Authentication.Cookies" Version="2.1.2"
PackageReference Include="Microsoft.AspNetCore.Authentication.Facebook" Version="2.1.2"
PackageReference Include="Microsoft.AspNetCore.CookiePolicy" Version="2.1.2"
PackageReference Include="Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore" Version="2.1.1"
PackageReference Include="Microsoft.AspNetCore.HttpsPolicy" Version="2.1.1"/>
PackageReference Include="Microsoft.AspNetCore.Identity.UI" Version="2.1.3"
PackageReference Include="Microsoft.AspNetCore.Identity.EntityFrameworkCore" Version="2.1.3"
PackageReference Include="Microsoft.AspNetCore.Mvc" Version="2.1.2"
PackageReference Include="Microsoft.AspNetCore.StaticFiles" Version="2.1.1"
PackageReference Include="Microsoft.EntityFrameworkCore.SqlServer" Version="2.1.3"
PackageReference Include="Microsoft.EntityFrameworkCore.Tools" Version="2.1.3" PrivateAssets="All"
PackageReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Design" Version="2.1.4" PrivateAssets="All" 
blowdart
Tratcher
Eilon
NOTE: See my second comment on this issue. This isn't just an issue with my app (getyourpet.com). It can be reproduced with a "File New Project" web app. Someone needs to tell Apple what they broke fast!
Hi All,
I upgraded my iPhone 6s to iOS 12.0 yesterday (I was on 11.x), and I found that after the upgrade I couldn't sign in to getyourpet.com (my production site) using the Facebook button on the sign in page (/account/login) when using the Safari app. Tapping the Facebook button displayed the spinner on that button for a brief moment, but then you're just back at /account/login (though some amount of redirecting seemed to be happening behind the scenes). That led me to do a lot of experimenting. Here are some other findings:
I had a colleague who was still on iOS 11x try signing in with Facebook. She could sign in over and over using Facebook without any issue. I then had her upgrade to iOS 12 and now both of our experiences are identical. Tapping the Facebook button displays the spinner, there's some redirecting going on, but when the spinner stops spinning you're at /account/login.
Signing in with Facebook or Google on Chrome, Firefox, Edge and Opera are fine on my laptop.
I tried signing in with the Google Chrome and Firefox apps. In both cases the behavior was the same as with Safari. I'm just back at /account/login.
If I clear browser history and cookies for any of the browser apps, then signing with Facebook or Google works once. You're redirected to either the Facebook or Google authentication pages, then you're redirected back to getyourpet.com and you're signed in. But if you sign out and try signing in again, you're back at 3: tapping Facebook or Google the second time after clearing history and cookies you're just left at /account/signin.
If I sign in using email / password then go and manage my login providers (on getyourpet.com this is in the user menu as Sign In With...) and then select to enable signing in with Facebook or Google on an account, if I've just cleared browser cache / cookies, then the user is brought to Facebook or Google to authenticate, and returned to getyourpet.com's Sign In With... page successfully. If you try enabling signing in with Facebook or Google and there's already a cookie, then you're signed out!
I've reproduce this in all of our environments (local development on my laptop and in our QA environment).
I'm trying to dig up another iPhone to reproduce this on. I won't have this until later tonight, but I did feel this is such a potentially giant issue that I thought I'd raise it quickly. Unfortunately I'm not a mobile developer, and don't have any clue as to how to get started with using some kind of tool like Fiddler to watch the traffic to/from the browser apps on my phone.
Anyways, it seems like once there is an authentication cookie, somehow that's not correctly being sent to getyourpet.com?
I'm sure this is the kind of issue where it's like "oh boy, this probably isn't even real, and there's not enough to go on". If there are things I can provide that would make further investigation possible let me know.
We're running a fairly basic ASP.NET web app that's been migrated all the way from pre-1.0 through to the latest version of 2.1 (2.1.4). I've included the relevant parts of our project file below. We run on servers running Windows 2012 R2 with the latest patches, and we run using IIS 8.5 (not native kestrel). Nothing has changed in our environment for over a week. The variable seems to be iOS 12.
I know y'all don't own iOS 12, but if there was some way of knowing what's going on then there would be something concrete that could be sent to Apple. I'm afraid it's going to be a lot of trouble for a lot of sites like getyourpet.com as folks upgrade to iOS 12.
-Brian Eriksen