so removing the file worked for one user, but not another.
hopefully someone from support has seen this.
FWIW - We had two factor enabled the first time the user logged in, then disabled it.
Were you using two factor at all?
No progress here - I'm going to watch github and see if an issue is opened on ANZ or ABP.
This is bad.
@URITECHNOLOGY - was the URL it redirected you to %2fApp ?
I see that in our URLs - and I'm thinking, for some reason that's getting changed.
I'm wondering if something in the upgrade affects how Chrome handles the redirect.
@URITECHNOLOGY - what version are you on? JQ or Ang?
I'm still trying to recreate this in my dev environment using a local state file, but not having much luck.
I'm seeing this as well. Jquery / 8.9
New deployment and when setting up new tenant, gets into a login loop.
Works with MS Edge, but some Chrome installations get in this authentication loop.
I'm actively troubleshooting it at this very moment.
Thanks for this - but any idea why it causes all the tests to fail?
FWIW - Have you tried creating DTO objects then firing into a seperate UOW function that maps to your enity then creates?
I've found myself stepping "outside the EF bubble" with DTO objects sometimes, both for speed and tracking issues.
And thanks for the AutoDetectChangesEnabled tip - never tried that.
Speaking of - if you comment that out while debugging - do you get more information?
I was eventually able to figure it out.
The documenation screenshots are the older Azure interface.
Basically - the steps now are to create the service plan, add a sql box, add a database, add an app service, connect and to migration / update-database, then in visual studio (for me anyway) publish and it will pick up everything on your Azure account.
In your catch, if you comment out the throw, does it still happen?
