nightkr
Release to F-Droid
Update for your fastlane full_description.txt (taken from my repo, where your app is already present since yesterday):
<p><i>FlickBoard</i> is a flicking-style keyboard, in the style of <a href='https://www.exideas.com/ME/index.php' target='_blank'>MessagEase</a> and <a href='https://github.com/dessalines/thumb-key'>Thumb-Key</a>.</p><p>Type the letters in the center of a key by tapping it. Type the keys in the corners by swiping in that direction. That's it!</p><p><b>Why not MessagEase?</b> It's proprietary, and is currently threatening everyone's existing installations unless they subscribe.</p><p><b>Why not Thumb-Key?</b> Thumb-Key intentionally doesn't support some gestures that MessagEase supports.</p>
Yes, it's HTML – and yes, all in one line (as F-Droid otherwise replaces each line break with <br>s). Be welcome to copy-paste it over :wink:
https://github.com/nightkr/flickboard/commit/c9b844ffba4b1d0a34321098a6883152ffd638d2
Also a minor niggle but I see the author name on IzzyOnDroid is listed as just "Natalie", is that pulled from the GitHub display name?
Yupp. Shall I put something else? Just let me know.
And no need to be sorry :wink: Glad to help!
@rommeswi if you have my repo added, you can already find the app here and in your favorite F-Droid client :smiley:
@IzzySoft is there anything I can do on my side to make the F-Droid packaging smoother?
Obviously one of you folks still needs to test and approve it in the end, but I don't want to burden you more than is necessary.
one of you folks
One of the folks at F-Droid, yeah. I'm currently not active at F-Droid. So I don't keep track of what progress which app has at RFP or fdroiddata. What I however can give you are these hints:
I'm currently focusing on improving my repo – with features that never took off at F-Droid despite being requested there long ago. See e.g. additional APK checks or, for a shorter and easier to understand summary, see What about security?. You'll find neither the permission checks, the Manifest checks nor the signing block checks at F-Droid. Signature verification there's only in place with apps having reproducible builds (while in my repo it's in place for each and every app). The Library scan was never implemented there either – while with my repo it's run for each and every update (and of course at initial inclusion time).
Next things to come are mirrors, to distribute the load and increase resilience.
I'd say you don't need to push things to hard over there; your app has a good place with my repo now. But if you want it there, too, and making it easier to the crew over there – find the hints behind above links. Especially creating your MR at fdroiddata yourself should already speed up things, to my experience when I was still active there.
Version 0.0.8 of this app is still not showing on IzzySoft's Fdroid repo even 8+ days after release.
Not an actual problem as far as I'm concerned, so I'm just flagging it here on this old issue for visibility :)
@racingcirc it is long there. But @nightkr forgot to adjust versioning before building the APK :wink:
$ iod repo get se.nullable.flickboard
se.nullable.flickboard: looking for 'https://api.github.com/repos/nightkr/flickboard/releases'
se.nullable.flickboard: checking tag 'v0.0.8'
se.nullable.flickboard: lastRelNo set to '0.0.8', checking for files
se.nullable.flickboard: Upstream file date (2024-02-21 17:55) is newer than ours (2024-02-21 17:53).
se.nullable.flickboard: returning ['0.0.8','https://github.com/nightkr/flickboard/releases/download/v0.0.8/flickboard-v0.0.8.apk',1708534532]
se.nullable.flickboard: 0.0.7/0.0.8, https://github.com/nightkr/flickboard/releases: https://github.com/nightkr/flickboard/releases/download/v0.0.8/flickboard-v0.0.8.apk
- Grabbing update for se.nullable.flickboard: OK
repo/se.nullable.flickboard_10.apk already exists and is identical to the one we downloaded; replacing it nevertheless
$ sigcheck repo/se.nullable.flickboard_10.apk
package: name='se.nullable.flickboard' versionCode='10' versionName='0.0.7'
:man_shrugging:
Thanks for the quick responses. Good to hear that this was only a minor oversight and not indicative of some systemic dysfunction.
@nightkr This is excellent software, you're clearly great at this! 🐱👏🏼
@nightkr no worries, such things happen more often than you'd think – and not just to you :wink: And consider it a good sign that you have loyal users noticing it and ringing the bell, so the cause can be uncovered, seem embarrassing – and be remembered (only by you, not by us) to not be repeated :zany_face:
But @nightkr forgot to adjust versioning before building the APK 😉
Actually (and as your log shows) releases v0.0.7 and v0.0.8 have the exact same APK attached; v0.0.9 looks good though (but I did notice the APK size went from 2.4 to 11.3MB) :)
Yeah, I suspect I accidentally only rebuilt the AAB (for Play). Almost made the same mistake now.
The size is larger as of 0.0.9 because it now bundles the Noto Color font, in order to render emojis better on older devices.
@nightkr you might want to try removing fdroid-bot label to trigger a rescan.
If you want issuebot to run on an issue again, remove the fdroid-bot label again (which you can do yourself if you have at least "reporter" status for this repo, or you can ask someone to do it for you). On the next run, issuebot will consider that issue as if it had not seen it.
via https://gitlab.com/fdroid/rfp#issuebot
@msolglu Ah, thanks! I'm afraid I don't have reporter permissions, so I can't edit that.
@dandv I would love to see it happen, but I think the thread in general summarizes why I wouldn't hold my breath for it.
This issue has been migrated to Codeberg: see https://codeberg.org/natkr/flickboard/issues/15 for any further discussion!