[Bug]: Unable to add as PWA in iPadOS nor scroll with Magic Keyboard
See original GitHub issueIs there an existing issue for this?
- I have searched the existing issues
OS/Web Information
- Web Browser: safari
- Local OS: ipad 16.1.1, iOS 16.1
- Remote OS: Unraid v6
- Remote Architecture: x86-64
code-server --version
: 1.74.0, latest as of this issue
Steps to Reproduce
- Open remote web UI
- Use Add to Home button in safari
- It adds a bookmark
- Also try to scroll with magic keyboard, nothing happens. Only finger scrolling works
Expected
It should scroll with the trackpad and it should add as a PWA
Actual
No PWA, no scrolling
Logs
No response
Screenshot/Video
No response
Does this issue happen in VS Code or GitHub Codespaces?
- I cannot reproduce this in VS Code.
- I cannot reproduce this in GitHub Codespaces.
Are you accessing code-server over HTTPS?
- I am using HTTPS.
Notes
I am using nginx to proxy connection with a valid cert. Tried https and add to home still only uses a bookmark.
Note: I CANNOT scroll in github codespaces UNLESS I add it as a PWA. So the primary issue is I can’t get this to add as a PWA even with HTTPS.
nginx proxy manager -> https with letsencrypt cert -> proxy pass to port 3000 -> valid https connection
I am going to try a few more troubleshooting steps. I really love what you guys have created so I hope I can get it working
Edit: tried again with barebones nginx container and tls config, same issue. I don’t know if this is related to HTTPS because something like VueTorrent installs a PWA with just a normal HTTP connection.
Issue Analytics
- State:
- Created 9 months ago
- Comments:8 (1 by maintainers)
Top GitHub Comments
Workaround for anyone coming across this
enable shortcuts in settings -> general -> keyboards. Scrolling worked immediately. Just annoying because it forces a keyboard UI element on many text inputs. Its definitely less than ideal so hopefully it can get fixed
Alternative workaround: use stage manager. You may have to on/off/on for it to work.
Yes it does. Added as a PWA and it behaves the same. Damn, I guess its an upstream issue 😦
Hopefully they can fix it! Thanks for your help