Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please attach APK to releases #87

Open
IzzySoft opened this issue Aug 3, 2018 · 5 comments
Open

Please attach APK to releases #87

IzzySoft opened this issue Aug 3, 2018 · 5 comments

Comments

@IzzySoft
Copy link

IzzySoft commented Aug 3, 2018

Could you please add the .apk file to the latest release (and to future ones)?

@IzzySoft
Copy link
Author

Any chance?

@IzzySoft
Copy link
Author

@tobyli ^^? Also, will there be new releases (the latest current existing tag is from 2016)? Further, could you please clarify what license this project uses? Thanks in advance!

@IzzySoft
Copy link
Author

"Doctor, everybody is ignoring me!" – "Next, please!" 😢

@tobyli
Copy link
Owner

tobyli commented Feb 26, 2019

Hey IzzySoft,

Sorry for the late reply.

For the APK, we did not include a compiled APK mostly because the project is still an early-stage research project. While most main features are working in our tests, it in general is still very under-tested and under-documented, with most likely a good amount of unknown bugs and issues. Thus we do not anticipate any release for end users at this point. For development/study/research purpose, it should be pretty straightforward to build an APK from the source.

For the license, at this point it's pretty much do whatever you want for personal and academic research use, and we have no liability and provide no support for any of it.

Let me know if you have any questions.

@IzzySoft
Copy link
Author

Background of my question is your app's listing in my repo. As that's there, at some point there must have been an APK available here – which claimed to represent v1.0. And going by the timestamp, that must have been in 4/2017 – i.e. before the first tag. Which confuses me a bit – unless you do a complete rewrite.

We can leave it that way until a first release of the new code is available (I'll find this issue when I next time wonder about the gap) – unless you want that listing removed from my repo. If it can saty (and wait for an update), Iit'd be nice if you could attach the WTF license to your code here (placing the license.txt file in the root of the git repo usually gets Github to detect it).

All the best for your further development!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants