I think the response krt gave was fair enough: --- I dont get all that API key nonsense, you can search this board for our opinions on API keys. I’ll keep thi

I think the response krt gave was fair enough: --- I dont get all that API key nonsense, you can search this board for our opinions on API keys. I’ll keep this short: If your app requires an API key and you withhold it (because you entered an agreement with the service provider), this basically makes it not buildable for 3rd parties in a useful manner. F-droid will not sign an agreement with whatever service provider you use nor will we withhold build information. There are actually only two solutions: 1) Provide a way for the user (!) to enter API key or account information at runtime. 2) Provide a way for us to get the key at buildtime, e.g. there was one app where I had to download a pre-compile APK file, extract the key from it and re-use that key in our builds.. which sucked. Anyway, I dont see what’s the difference to just providing the API key. If you distribute an APK, you distribute the API key (in one form or another) — since without it the app would not work… sigh.