Last release lacks APK attachment
See original GitHub issueThe Latest release lacks the .apk
file. Could you please attach that (and continue attaching it for future versions)? Thanks!
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Apk file won't upload due to lack of uniqueness - Forums
"Failed to upload APK. The version codes of all uploaded APKs in an app must be unique. The APK you just uploaded with...
Read more >Pushing android apk to GitHub release files · Issue #9067
Basically, I want Travis to generate an apk and upload it as an attachment/binary when I create a new release for my project...
Read more >How to debug apk signed for release? - android - Stack Overflow
The first one will enable debugging of signed APK, and the second one will prevent compile-time error. After this, you can attach to...
Read more >[Discontinued] [Windows] APK Easy Tool v1.60 (2022-06-23)
Apk Easy Tool is a lightweight GUI application that enables you to manage, sign, compile and decompile the APK files for the apps...
Read more >Slack for Android - Release Notes
Slack 22.12.10. December 7, 2022. What's New. Ever have those weeks where it feels like nothing's happening, but then you look back later...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
You can redistribute the binaries as they’re just Apache License 2.0 - licensed. If it’s the exact same binary you can represent it as the same as the official release, though wouldn’t represent an F-Droid distribution as an official distribution channel. It’s just Github and Play, officially.
Sure – that’s what I’ve meant. I don’t want to put an additional burden unto you, so I’d pick exactly the
.apk
you provide – expecting it to be the very same you already support anyway. My repo isn’t that “official” either (F-Droid knows about it and gives me “thumbs up” for filling a gap, but that’s all).So thanks, I’ll then pick it ASAP 😉