We moved session caching as internal parts of HTTP providers. Since that change, the Beacon API was receiving a bad bath for session caching.
How was it fixed?
These updates fix that (by setting the proper path to the HTTPSessionManager class) and raise the timeout for the async tests since some seem to be timing out.
What was wrong?
We moved session caching as internal parts of HTTP providers. Since that change, the
BeaconAPI was receiving a bad bath for session caching.How was it fixed?
These updates fix that (by setting the proper path to the
HTTPSessionManagerclass) and raise the timeout for the async tests since some seem to be timing out.Todo:
Cute Animal Picture