-
Notifications
You must be signed in to change notification settings - Fork 43
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
Add fastlane file structure #15
Comments
Added with 7ce775b |
Thanks for the suggestion! I just took it as is - maybe I have more motivation to do something else later:) |
@PanderMusubi as the store entry is now live (https://f-droid.org/packages/io.kuenzler.whatsappwebtogo/), how do I get it to use "my" metadata? |
If you move metadata one directory up and remove fastlane it should appear in next release. @IzzySoft correct? |
I wouldn't recommend that (though it should indeed work). Instead, switch to the proper Fastlane file structure: there's one directory level missing here. This repo has |
@IzzySoft next release is out (took a while..). Changelog and Images worked, but Title and Description not so much. Anything I still need to do? |
Yes, we'd need to open another MR at F-Droid to remove the local description. But first you'd need to fix your fastlane short-description: max 80 chars are permitted, all behind that will get truncated. Yours has 129 chars, so almost half of that will be cut off. I'd simply make that
Then, after you've tagged your next release (fastlane is always tied to that), we can go and switch over. While on it, why not taking some of the current description into your <i>WhatsappWeb</i> lets you access WhatsApp Web on your mobile phone or tablet. It has full support for sending audio and pictures / video. With a clean and easy interface it's fun to use - it even shows up as running on an Android phone on the phone where WhatsApp is installed!
-free and without ads-
If you have problems just send a mail or create a github issue.
This app is in no way affiliated with WhatsApp Inc. The rights for WhatsApp and WhatsApp Web belong to WhatsApp Inc. This app is a private project to enable the use of WhatsApp Web on Android Devices. |
Thanks for the quick feedback and tips! I updated short-description and description. I want to wait for an actual change to the app for the next tagged release to avoid having "empty" releases. |
Release 1.6.1/30 was picked up by fdroid: https://f-droid.org/wiki/page/io.kuenzler.whatsappwebtogo/lastbuild_30 |
@IzzySoft ping :) |
@92lleo pong, here you go 😃 |
@92lleo as for pulling from fastlane, I had to clear all summaries as well. You might wish to add the corresponding
|
@IzzySoft I'm preparing a release currently, is there anything needed to be included (besides the short descriptions)? |
The feature graphic |
Looks like your fastlane structure contains everything that's needed (short and full desc), what's recommended (screenshots, changelogs), what's nice-to-have (featureGraphic), and even more (title). Now you'd only need to get some things in the right place: all the picture stuff needs to be below |
@IzzySoft thanks for the hint, I somehow overlooked the image dir. Fixed now. If the metadata looks good for you now, I'd tag a new release |
Yes, looks good now! When tagged, please send a note to the corresponding RFP (or update the MR, whichever it is). Thanks! |
Tagged as v1.6.2. |
Oops, no – I see your app was already added. Then we'd need a MR to remove summary/description from our metadata, so fastlane can take over. |
https://gitlab.com/fdroid/fdroiddata/-/merge_requests/7076 |
Ah, I did that already… well, so much work, one doesn't remember each single item 🤣 Yes, then everything should be ready. I didn't check when that build went through – but of course it would need to be signed (manual step) and then won't appear before the next index is published. |
Fastlane file structure is present and working. I think this can get closed? |
Correct. Thank you all for your help! Closing. |
Add fastline file structure as detailed in fdroid doc
(task from #8)
The text was updated successfully, but these errors were encountered: