RichardKnipe

> Looks like the NDK download URL has been a bit of a moving target. > > two ways I was able to resolve this: > > option 1) to...

> I had a similar issue, it appeared to be that the NDK URL was broken, so I had to update my `buildozer.spec` to the latest recommended NDK version The...