-
-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pinned webpage causes issue #353
Comments
It does work for me, if Outlook.com is NOT pinned. (I do use it like this) For testing, I tried to use https://roadmap.sh/ and https://dev.azure.com/ - both work pinned as well. |
Please create a |
Sorry for the late answer: firefoxpwa-stderr.log Console log:
|
It seems to be the same issue as I'm having (with broken URLs), but I don't know why it only happens to you when the tab is pinned. So, I guess you can just unpin it, install the PWA and pin it again? Alternatively, you can uncheck "use the manifest" when installing the PWA (although this will mean menu entry shortcuts and few other similar features won't work). The actual issue with invalid URLs that cause panic is because of a library that has this bug (seanmonstar/reqwest#668, seanmonstar/reqwest#1399). I probably cannot fix this myself. |
That is how I did it. Unpin, install and pin again (or used the installed version) as a workaround. |
Perhaps Outlook.com is doing some testing by serving different manifests, and one of them is corrupted. So, as this seems to be an issue with website and library (reqwest) that I cannot fix, I'll close this issue. Probably Microsoft will fix at some point, and I also hope reqwest fill fix that bug in the future. I may also add this to the documentation when I finish it. |
Ok |
I tried to create a pwa for Outlook.com, and I had the tab pinned.
If you try to create a PWA then, it causes "An unexpected error occurred".
It's hard to see if there is an error in the console, since it's flooded with errors from Outlook itself.
fyi: It works, if the tab is not pinned.
The text was updated successfully, but these errors were encountered: