Updated to most recent version of ring app
Two-Factor Authentication still returns the error:
Webpage not available
The webpage at ring://app/settings/2fa could not be loaded because:
net::ERR_UNKNOWN_URL_SCHEME
Shared Users > Select a Location still returns the error:
“Webpage not available
The webpage at ring://app/location/string of alpha-numeric-chars/settings/shared_users could not be loaded because:
net::ERR_UNKNOWN_URL_SCHEME”
I observed these error messages on three different ANDROID devices.
Please note:
ring://app/whatever
IS AN INVALID URL SCHEME …
Any URL that starts with
ring://
cannot be a valid URL
If one takes the position that
ring://
is a valid transport protocol …
I would ask that person to please cite the RFC that describes it.
A valid URL would start with a valid transport protocol such as
https://
Valid URLs might look like:
https://app.ring.com/settings/2fa
and
https://app.ring.com/?string-that-ids-account?/settings/shared_users
Or:
https://ring.com/app/settings/2fa
and
https://ring.com/?string-that-ids-account?/settings/shared_users
I base those examples on the errors that display when I attempt to navigate to
Two-Factor Authentication or Shared Users > Select a Location in the Control Center.
I realize I can navigate to the 2FA switch from the Account link on the top level menu, and can navigate to Shared Users through the Settings link on the top level menu - so it should be trivial for ring to properly link to them through the Control Center.
I wouldn’t think that those URLs are hard coded into the app - that would defeat the central premise of n-Tier web/app design.
The errors I’m observing must be another instance of an AWS server that has not received all the updates that should propogate across the cloud infrastructure that provides the appropriate content in response to user inputs.
The same problem prevented me from reaching two very important links on the website with a browser - everyone here and at ring support insisted the problem was with my browser[s] or my router[s] or my computer[s] or me. It took three weeks for that problem to resolve - the urls on the website changed - which I have no control over. [And a moderator here still maintained that the problem must have been due to user error]
Your devs and NetOps should know better.
