Arcane-Tracker VS OkHttp

If you're on PC or a compatible Android device get a deck tracker, as it will make identifying opposing Secrets in play and "remembering" what's left in your deck much easier. They also record the game in a way the replay can be watched/shared later to help analyze what's going right/wrong. Firestone is Windows-only and Hearthstone Deck Tracker is for Windows or Mac, and is tied in with viciousSyndicate, which has statistics and decks much like HSReplay. Arcane Tracker is no longer officially supported and just won't work on some Android devices because of that, but it supports HSReplay (the server behind HS Deck Tracker).

It's on GitHub only now, it's just not officially supported any more, and it's less likely to work for some people (like me; Moto G Fast on Android 10) because of that.

I did find their GitHub info.

Link: https://github.com/HearthSim/Arcane-Tracker/releases

Arcane Tracker has been unofficially maintained on GitHub by it's mastermind since around MaDF. It's updated for FitB, but unlikely he'll keep up through another expansion as he's working on it without being able to test (no Android 10 or lower device).

Good point, sorry; lol. GitHub is where it's hosted now, and it's possible to bookmark the Releases page or the latest tag to easily get back there and check for an update.

We will use Square’s Mock Webserver to spin up a mock server which we can use to simulate real api's request to the get coffee endpoint.

OkHttp Documentation

mockwebserver -> https://github.com/square/okhttp/tree/master/mockwebserver

I searched in the OkHttp GitHub project for an advice on which values may be suitable for Android apps nowadays but found no answers (only this old issue which does not help). Since we share a single OkHttp client Singleton for all our retrofit APIs and even Coil, I wonder if the default 5 maxRequestsPerHost is really enough.

You can technically add a Content-Length header for each part. It's not forbidden by the RFC, but nor is it common. It caused [problems](https://github.com/square/okhttp/issues/2138) for OkHttp, and they eventually removed it. Might be fine for internal-only use, though.

Boundaries are a lot like UUIDs, and rely on the same logic. When generating random data, once you have enough bits, the odds are against that sequence of bits ever having been generated before in the universe.

Lets be specific. This is the gradle build file for Squares okhttp client library. How exactly would your bld tool "predict" or "help" with all the parameters needed? There is no need to be defensive. Replace those large build files with your own, show where your approach is better and then understanding will lead to better solutions.

And adding to that: The asynchttpclient library is just a thin wrapper around OkHttp3, so it might be easier to just go with that instead: https://square.github.io/okhttp/

Retrofit in combination with OkHttp for fetching data from server (which hopefully already exists)

OkHttp