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
Describe the issue *
Unable to Login. I get the message "Sorry Request aborted", but I am using the same details as I use to successfully login to the same version on my Samsung Galaxy A8 tablet.
Expected behaviour
To Login
To Reproduce
Steps to reproduce the behaviour.
Go to Login page (Welcome back), insert email address and password and press SIGN IN. Error message appears every time.
App Version
V6.1.0
Device
Samsung Galaxy S6 running Android 7.0
When did this happen
Please let us know the time of the day this issue occurred. We can look into our server logs for anything related to your case.
All of 2024
Additional context
Made multiple unsuccessful attempts to Login over past 6 months. Successful on Galaxy Tablet A8 running Android 14. Uninstalled and re-installed app, but same error messages afterwards.
The text was updated successfully, but these errors were encountered:
https://irecord.org.uk/forum/mobile-applications/unable-log-app-sorry-request-aborted
App Name *
iRecord (Android)
Describe the issue *
Unable to Login. I get the message "Sorry Request aborted", but I am using the same details as I use to successfully login to the same version on my Samsung Galaxy A8 tablet.
Expected behaviour
To Login
To Reproduce
Steps to reproduce the behaviour.
Go to Login page (Welcome back), insert email address and password and press SIGN IN. Error message appears every time.
App Version
V6.1.0
Device
Samsung Galaxy S6 running Android 7.0
When did this happen
Please let us know the time of the day this issue occurred. We can look into our server logs for anything related to your case.
All of 2024
Additional context
Made multiple unsuccessful attempts to Login over past 6 months. Successful on Galaxy Tablet A8 running Android 14. Uninstalled and re-installed app, but same error messages afterwards.
The text was updated successfully, but these errors were encountered: