-
Notifications
You must be signed in to change notification settings - Fork 19
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Implement experimental workaround for Android Server pairing
The new android platform introduced in 6.5.0 made the app be served from the HTTPS context by default. This broke pairing, because requests to Server are sent via insecure HTTP (we use our own TLS certificate to secure the communication once pairing is complete) and chrome disallows "mixed content" requests. I implemented a preference here that forces the app to load from HTTP, which "fixes" the issue, but it has some drawbacks: - Some browser features are disabled when loaded from an insecure context. We don't know what these are, exactly. - iOS uses its own preference for 'scheme', so pairing is presumably still broken there.
- Loading branch information
Showing
2 changed files
with
7 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters