Umbraco v13.9 startup error The DELETE statement conflicted with the REFERENCE constraint "FK_umbracoExternalLoginToken_umbracoExternalLogin_id".

[robertjf]

Which Umbraco version are you using?

13.9.0

Bug summary

Upgraded Umbraco to latest v13 release and on startup (local dev environment) the following error is occuring:

The DELETE statement conflicted with the REFERENCE constraint "FK_umbracoExternalLoginToken_umbracoExternalLogin_id".

Full stack trace indicates this is happening because it's attempting to delete External Login Providers on startup, even though no configuration has changed - the relevant stack trace locations are:

   at Umbraco.Cms.Infrastructure.Persistence.Repositories.Implement.ExternalLoginRepository.DeleteUserLoginsForRemovedProviders(IEnumerable`1 currentLoginProviders)
   at Umbraco.Cms.Core.Services.ExternalLoginService.DeleteUserLoginsForRemovedProviders(IEnumerable`1 currentLoginProviders)
   at Umbraco.Cms.Web.BackOffice.Security.BackOfficeExternalLoginProviders.InvalidateSessionsIfExternalLoginProvidersChanged()
   at Umbraco.Cms.Web.BackOffice.NotificationHandlers.ExternalLoginProviderStartupHandler.Handle(UmbracoApplicationStartingNotification notification)

We do not have any back-office external login providers registered, just cloud identity; we do have a provider registered for members only.

Specifics

See summary

Steps to reproduce

1. Upgrade umbraco from 13.8.1 to 13.9.0
2. Launch the website locally

Expected result / actual result

No response

[github-actions]

Hi there @robertjf!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[AndyButland]

Thanks for the report @robertjf - I can replicate, and have identified the issue and a fix in the linked PR. We'll prepare a 13.9.1 with a fix for this.

[AndyButland]

Fixed via #19273 and will be resolved in 13.9.1 (and 16.0.0).