You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Register a user against a server. Perform no actions on that new user except to create it. (Specifically, do not create a room). Leave the element-web stable client running so we'll be able to share keys later.
Login on element X iOS with the credentials above
Attempt to click the "Continue" button
(Nothing happens)
Looking at the appium source, the button is tagged enabled=false, so I imagine clicking won't help.
I have been able to login to an existing user with a room already created and share credentials there.
Logs are available on request via browserstack (however they have my test username/password embedded in them so will not supply public link here). Am also able to share the username/password if developers wish to try locally.
Practically this isn't a big issue; most users will create a room and use the device a little on element-web before they try to sign in on their phone; however, if you don't create that room then the entire app appears frozen/broken with no way forward.
Your phone model
No response
Operating system version
No response
Application version
No response
Homeserver
No response
Will you send logs?
Yes
The text was updated successfully, but these errors were encountered:
Steps to reproduce
(Nothing happens)
Looking at the appium source, the button is tagged
enabled=false
, so I imagine clicking won't help.waiting (up to 90s) does not enable the button.
video-8a9165f808fd2c1dc9a04d84c0ab2094ba05b928.mp4
Outcome
What did you expect?
To be able to share keys from the first login.
What happened instead?
Never able to click the button.
I have been able to login to an existing user with a room already created and share credentials there.
Logs are available on request via browserstack (however they have my test username/password embedded in them so will not supply public link here). Am also able to share the username/password if developers wish to try locally.
Practically this isn't a big issue; most users will create a room and use the device a little on element-web before they try to sign in on their phone; however, if you don't create that room then the entire app appears frozen/broken with no way forward.
Your phone model
No response
Operating system version
No response
Application version
No response
Homeserver
No response
Will you send logs?
Yes
The text was updated successfully, but these errors were encountered: