async-http | An asynchronous client and server implementation of HTTP/1 | HTTP library

Well like I thought, the solution was removing a single line from build.gradle:

This problem occur when you are adding two dependencies that includes the same classes. And I think the accused one should be this braintreepayments dependency, so I recommend updating

It turns out the "restarts" were really just leftover invocations. At some point I'd killed the process (this is all local debug using Azure Functions Tools) and it left some state around in my Azure Storage emulator. So my local Azure tools thought the durable function was still running and/or needed to be restarted.

To get rid of the zombie invocations I just deleted all the "testhub" tables, queues, and blobs from my emulator using Azure Storage Explorer. These get auto-generated when you run a durable function locally.

What you're using is an Android HTTP Client. It's not possible to use Android Libraries in Java Cloud Functions. As you can see in the documentation, the entire execution environment is based on Ubuntu Image and Java 11. It doesn't include the Android environment.

Even if you look at the system packages included by default, you won't be able to find the packages needed to run Android Libraries.

The solution is to use a Java HTTP Client, like the one that's already built in Java 11. You're also free to choose alternative libraries, as there are many HTTP clients available out there that supports both Java and Android.

Try

You will need to change the encoding of the path segments in the parsed URI to a more strict one:

You can create a separate .css file for styling the elements. Place the .css file in the assets folder and include it in your html code.

Now load the HTML in the webview like below:

Alright further testing revealed that the app crashing actually didn't have anything to do with our API calls whatsoever. The problem actually was us loading the images to be shown next to our datasets asynchronously on demand. Turns out that during testing of the image loading we only had like 20 entries in our ListView. This was fine because iOS could load all images at once. However when loading 1500+ datasets from our API the ListView started buffering, only loading images as needed and that's when the application crashed. Probably because the original image stream wasn't available anymore or something like that.

Also as an interesting side note: iOS does actually close the network connection to the server but only after a 100 second timeout of no packets sent while the Windows .NET Core Console Application closes it immediately. And we never waited this long. Oh well :D

Future#sequence should execute the HTTP requests in parallel?

First of all, Future#sequence doesn't execute anything. It just produces a future that completes when all parameters complete. Evaluation (execution) of constructed futures starts immediately If there is a free thread in the EC. Otherwise, it simply submits it for a sort of queue. I am sure that in the first case you have single thread execution of futures.

println(scala.concurrent.ExecutionContext.Implicits.global) -> parallelism = 6

Don't know why it is like this, it might that other 5 thread is always busy for some reason. You can experiment with explicitly created new EC with 5-10 threads.

The difference with the Async case that you don't create a future by yourself, it is provided by the library, that internally don't block the thread. It starts the async process, "subscribes" for a result, and returns the future, which completes when the result will come.

Actually, async lib could have another EC internally, but I doubt.

Btw, Futures are not supposed to contain slow/io/blocking evaluations without blocking. Otherwise, you potentially will block the main thread pool (EC) and your app will be completely frozen.