Mobile Chrome Authentication Cookie Persistent missing on browser reload - asp.net

Question

I have developed an ASP.Net Core 6 web application which uses Cookie Authentication. Everything works as it should do i.e. I secure the Controllers using the [Authorize] and it challenges the authentication on a request, forces them over to the Login Page, they login, cookie is generated and all works fine. I have a "remember me" and I set this to last for 5 days and again this all works fine apart from the following situation:
On mobile devices (Android & iOS) in Chrome:
The user is logged in a accessing secure pages fine, they close the chrome app. They then re-open the chrome app, chrome opens and it then reloads my webpage as the tab has the site in there from when it was previously closed.
It would at this stage seem there is NO authentication cookie sent over on this reload of the browser. The user is taken straight to the Login Page.
BUT, they are logged in as if they click any link on the Login Page e.g. the Logo/Home page icon -> it checks the User.Identity.IsAuthenticated and redirects them to their dashboard which is behind a secure controller method.
Has anyone come across this before? It works perfectly on a desktop, just not on mobile devices and only seems to be with chrome when the chrome browser application is reloaded after being closed. Safari seems fine.
This is an issue for me as the users will be asked to create a shortcut link on their mobile homescreen to go to the website. If they close their browser and later click the shortcut link - it will reopen chrome and it will re-ask them to login but it shouldn't as they are already logged in.
Hope this makes sense.
Here are some of the configs:
Program.cs
builder.Services.Configure<CookiePolicyOptions>(options =>
{
options.CheckConsentNeeded = context => true;
options.MinimumSameSitePolicy = SameSiteMode.Lax;
});
builder.Services.AddAuthentication(CookieAuthenticationDefaults.AuthenticationScheme)
.AddCookie(options =>
{
options.Cookie.HttpOnly = true;
options.ExpireTimeSpan = TimeSpan.FromDays(5);
options.LoginPath = "/Account/Login";
options.AccessDeniedPath = "/Account/RestrictedAccess";
options.LogoutPath = "/Account/Logout";
options.SlidingExpiration = false;
options.Cookie.SameSite = SameSiteMode.Lax;
options.Cookie.MaxAge = TimeSpan.FromDays(5);
options.Cookie.SecurePolicy = CookieSecurePolicy.Always;
});
builder.Services.AddDistributedSqlServerCache(options =>
{
options.ConnectionString = "xxxxxxx";
options.SchemaName = "dbo";
options.TableName = "WebSessions";
options.DefaultSlidingExpiration = TimeSpan.FromDays(7);
});
builder.Services.AddSession(options =>
{
options.IdleTimeout = TimeSpan.FromDays(7);
options.Cookie.HttpOnly = true;
options.Cookie.IsEssential = false;
options.Cookie.SameSite = SameSiteMode.Strict;
options.Cookie.SecurePolicy = CookieSecurePolicy.Always;
});
app.UseSession();
app.UseHttpsRedirection();
app.UseStaticFiles();
app.UseCookiePolicy();
app.UseRouting();
app.UseAuthentication();
app.UseAuthorization();
The entire site works on https (ssl) and all content is served via https.