-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
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
Switch to OKHttp #3163
Switch to OKHttp #3163
Conversation
Ooooohhhh. Went to do one last commit to clean out the I'll have a look at moving this out as I think it's best we don't leave the custom lib lying around. |
Ok this looks good for testing now. Had to rework the |
String downloadListUrl = url != null ? url : | ||
settings.getString(GeneralKeys.KEY_SERVER_URL, | ||
Collect.getInstance().getString(R.string.default_server_url)); | ||
|
||
if (downloadListUrl.endsWith("/")) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The rationale for the while loop was presumably that since it's user input there could be multiple trailing /, as unlikely as that might seem. Did you change it because it just doesn't seem likely or is there another reason?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope that is a genuine mistake. I can look at putting that back in and make sure it's covered by a test so it doesn't get absentmindedly removed again by someone (like me).
For a rainy day / good first issue, some of the types that Collect matches against are handled by the Android type mapper. It would be great for someone to go through and remove custom handling for those, I think. |
I believe that tested with success here! List of verified cases:
@opendatakit-bot unlabel "needs testing" |
Thank you, @seadowg and @kkrawczyk123! Great to see httpclientandroidlib go. @yanokwa, please see odk-x/httpclientandroidlib#2 which can be merged when the release goes out. |
Closes #2869
What has been done to verify that this works as intended?
Tests run locally and a quick play with the app on the emulator. Also ran the build through test lab as a precaution.
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
This should not effect users at all but as we're changing the backbone of the communication with Open Rosa servers it would be good to check Collect thoroughly against Aggregate/Central (and any other common Open Rosa servers).
Before submitting this PR, please make sure you have:
./gradlew checkAll
and confirmed all checks still pass OR confirm CircleCI build passes and run./gradlew connectedDebugAndroidTest
locally.