-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Trying to login caused crash, Didn't find class "org.apache.http.client.methods.HttpPost" #5000
Comments
This starts the process of exercising HTTP features prior to any contemplated move to OkHttp. More importantly it makes sure basic HTTP works to guard against things like issue ankidroid#5000
API28 requires you to specify in the manifest if you need Apache HTTP: https://developers.google.com/maps/documentation/android-sdk/config#specify_requirement_for_apache_http_legacy_library
Nice - that's a good one. Thanks for attempting to work on this from source, and thanks for reporting this. As we move towards API28 we have to be very careful of Apache HTTP library use as they are deprecating it: I just broke this with this commit moving us to API28 - I had focused on the hidden API issues with API28 and neglected a part of the Apache HTTP library changes. The correct fix (building now in my CI) is to follow the API docs and add an entry to the AndroidManifest. The full fix is to also implement at least a basic exercise of the HTTP infrastructure in automated tests so something fundamental like this doesn't slip through - and my PR has that also. I'll have it merged as soon as CI checks out and I re-read the diff a few more times |
If you have a moment - can you confirm this was running against an API28 device? In my testing I trigger it every time on my API28 emulator, but on API<27 it doesn't appear to be necessary |
API28 requires you to specify in the manifest if you need Apache HTTP: https://developers.google.com/maps/documentation/android-sdk/config#specify_requirement_for_apache_http_legacy_library
This starts the process of exercising HTTP features prior to any contemplated move to OkHttp. More importantly it makes sure basic HTTP works to guard against things like issue #5000
Yes, I confirm it was an API28 emulator. I also confirm that it now works fine. Thanks! |
Reproduction Steps
Expected Result
Login
Actual Result
Exception
Debug info
Research
Enter an [ x ] character to confirm the points below:
[x ] I have read the support page and am reporting a bug or enhancement request specific to AnkiDroid
[ x] I have checked the manual and the FAQ and could not find a solution to my issue
[ x] I have searched for similar existing issues here and on the user forum
The text was updated successfully, but these errors were encountered: