Closed StrawMonkey closed 2 years ago
Hello StrawMonkey, thank you for opening an issue with us!
I have automatically added a "needs triage" label to help get things started. Our team will investigate the issue and help solve it ASAP. Other community members may also look into the issue and provide feedback š
Thanks for opening an issue with us! I was just able to confirm this issue. After debugging it looks like the front-end is definitely sending the right data , and the manifest url being sent is also correct. @JudahGabriel based on this Im thinking this is a backend issue with our Edge package generator.
Hi @StrawMonkey
I've determined the issue: multiple redirects are causing our tooling to be unable to fetch your manifest.
Specifically, we have backend tooling from the Edge team that is having trouble following your redirects, and ultimately, it gives up trying to find your manifest.
Here's how your site is working today:
This double redirect appears to be causing the issue. Our internal tooling gives up and can't find your manifest.
We've opened a bug internally to fix this.
In the meantime, here's a workaround:
In PWABuilder, you can use https://app.timeling.com/en-gb as your URL. With that, you'll be able to generate your package.
I'm leaving this bug opened until we resolve the underlying issue in our internal tooling.
Note to self: internal bug filed here.
Hey @StrawMonkey I'm glad to report this issue has been fixed, app.timeling.com correctly works in PWABuilder, including generating a Windows app package for your PWA. š
Describe the bug I get an error when generating the windows package, other platforms work.
URL to app https://app.timeling.com
To Reproduce Steps to reproduce the behavior:
Expected behavior Package download.
Screenshots![image](https://user-images.githubusercontent.com/5722041/124632088-4f27f480-de84-11eb-8a75-eb5ecbb96206.png)
Additional info (please complete the following information):
Additional context
Error response: