We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No response
adb shell am start -d caldavs://user:[email protected]:444/path at.bitfire.davdroid/.ui.setup.LoginActivity
The Login type page is not skipped, a user has to select Login with URL and password before the intent data appear.
The login type selection could be skipped when the login intent data contains
When the loginFlow extra is set, we already skip the initial login page as expected. See https://manual.davx5.com/integration.html#launching-the-davx5-login-screen
loginFlow
I think we have to adapt the [Standard]LoginTypesProvider.intentToInitialLoginType to check whether there's a URL / email address.
[Standard]LoginTypesProvider.intentToInitialLoginType
At that point we can also better document what it returns in LoginTypesProvider KDoc.
LoginTypesProvider
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Problem scope
App version
Android version and device/firmware type
No response
Steps to reproduce
adb shell am start -d caldavs://user:[email protected]:444/path at.bitfire.davdroid/.ui.setup.LoginActivity
Actual result
The Login type page is not skipped, a user has to select Login with URL and password before the intent data appear.
Expected result
The login type selection could be skipped when the login intent data contains
Further info
When the
loginFlow
extra is set, we already skip the initial login page as expected.See https://manual.davx5.com/integration.html#launching-the-davx5-login-screen
I think we have to adapt the
[Standard]LoginTypesProvider.intentToInitialLoginType
to check whether there's a URL / email address.At that point we can also better document what it returns in
LoginTypesProvider
KDoc.The text was updated successfully, but these errors were encountered: