Open zola-25 opened 10 months ago
Same problem here, any solution?
@zola-25 Ok, found the solution: if you are using Vite PWA, you need to explicitly tell it to send the credentials for the manifest (I didn't see this in their docs, but I found it checking the code):
export default defineConfig({
// your vite config
plugins: [
VitePWA({
// your config
useCredentials: true,
}),
// the rest of your plugins
]
})
Hope it helps!
Describe the bug
Steps to reproduce the behavior:
Login
Error in devtools:
Notice when loading resources, web manifest is loaded from static web app server with 302, from a different IP to other resources?
The app manifest content has become the HTML of the standard auth page of the protected branch!:
Expected behavior web app manifest should load as any other resource on a protected branch, post-auth, with response 200 with the content that was set at build/deploy time.
When branch is not protected, the behaviour is normal (as expected). manifest file loads with no redirect and with the content that was set by development.
Additional context Web app is a pre-compiled Blazor web assembly app, with both app build and api build skipped by Oryx.