F-Droid version about tui-consolelauncher HOT 52 CLOSED

Next release should be possible to build in F-Droid. Hooray!

https://gitlab.com/fdroid/fdroiddata/merge_requests/2523/

from tui-consolelauncher.

Thank you very much for your help

from tui-consolelauncher.

Yes, i dont know why open source project is being released on google play.

from tui-consolelauncher.

@MichalLebeda Why not?

@AlfaOmega33 Feel free to fix #45 and then it will be build.

from tui-consolelauncher.

@licaon-kter could you please help me updating the F-Droid version? It's driving me mad

from tui-consolelauncher.

Not my area of expertise, sorry.

from tui-consolelauncher.

The issue #45 seems solved as I'm able to import the Gradle and build the most recent code with Android Studio. I'm not sure how F-Droid works but now it should in theory be possible to update the F-Droid version.

from tui-consolelauncher.

Just found out about this launcher... I'll wait for that update on F-Droid.

from tui-consolelauncher.

now there are Google's binary dependencies 😮

from tui-consolelauncher.

So far the only occurrence of Firebase is in ThemesManager for database purposes. While not offensive, it can further hamper the possibility of a new build on F-Droid as it refuses to build apps using Firebase and other related non-free stuffs.

from tui-consolelauncher.

I've split into flavors, foss is eligible for F-Droid. Sadly, I just had to delete theme altogether from foss

from tui-consolelauncher.

Any chance for a new release?

from tui-consolelauncher.

Ah finally, new version is out.

from tui-consolelauncher.

I just picked the latest commit hash and pushed 😃

from tui-consolelauncher.

How?

from tui-consolelauncher.

@Andre1299 I see 6.5 on Play, but source is at 6.4? Will update to 6.5 when it's out, please push

from tui-consolelauncher.

https://gitlab.com/fdroid/fdroiddata/merge_requests/3052/
👍

from tui-consolelauncher.

Could you please tell me how can I update the fdroid repo?

from tui-consolelauncher.

This is merged, so will be built and updated this week
As there is no consistent release tagging here, only manual updating works

from tui-consolelauncher.

Where can I manually update?

from tui-consolelauncher.

@Andre1299 "Manual update" means in the context of metadata used to build it.

from tui-consolelauncher.

@licaon-kter I released the version 6.7

from tui-consolelauncher.

What are these? https://github.com/fAndreuzzi/TUI-ConsoleLauncher/tree/master/libs

We need sourcecode or libs pulled from approved maven repos for everything included in the app. Binary files can't be used.

from tui-consolelauncher.

I replaced them with Gradle dependencies

from tui-consolelauncher.

@fAndreuzzi The tag is b0rken, it should be v6.7b

from tui-consolelauncher.

Is it good now?

from tui-consolelauncher.

Yes and no, autoupdate won't pick it up since you did not also bump versionName and versionCode. But we can build like this and in the next release you increment them an needed.

FYI, please keep the tag formatting vX.Y and don't mix them eg. 6.8, v6.9 as this confuses the autoupdater. ;)

So, with those two JARs it build fine but now it fails: https://gist.github.com/licaon-kter/424984f1f92b2e29de2035e4f67e14e3

from tui-consolelauncher.

I uploaded proguard-rules.pro and drafted a new release. How is it going now?

from tui-consolelauncher.

Better

FYI, https://gitlab.com/fdroid/fdroiddata/commit/b04e8e5350974ef9b01dade3002736217567e01e

from tui-consolelauncher.

Thank you very much!

So from now I'll only need to draft new releases?

from tui-consolelauncher.

Yup, add features, edit versionName X.Y and versionCode ZZZ then Tag vX.Y

from tui-consolelauncher.

/close this

from tui-consolelauncher.

@licaon-kter how long does it take before the update appears on F-Droid?
Also, if I use auto-update, how can I know wether the build went fine or if it ended up with an error?

from tui-consolelauncher.

Build process almost realtime (UTC): https://f-droid.org/wiki/index.php?title=Special:RecentChanges&days=7&from=&hidebots=0&hideanons=1&hideliu=1&limit=500

Last build log for your app: https://f-droid.org/wiki/index.php?title=ohi.andre.consolelauncher/lastbuild&redirect=no

from tui-consolelauncher.

Thank you

from tui-consolelauncher.

@licaon-kter Hello, unfortunately the last release didn't appear in f-droid. Could you help me to understand what's the problem?

from tui-consolelauncher.

You've introduced gradle flavours and the metadata needs to be adapted.

from tui-consolelauncher.

Thank you. How can I do that?

from tui-consolelauncher.

Ok so, gradle flavour is the issue, fdroidbot won't detect versionCode

Ref: https://gitlab.com/fdroid/fdroidserver/issues/420

Issue aside, why do you want them different?

/LE: https://gitlab.com/fdroid/fdroiddata/commit/f7d931d01ab44d1dce75827a130ccf980cf51bef

from tui-consolelauncher.

Since Google started to block apps which use SMS permission, I had to split t-ui in two versions (fdroid and playstore) in order to provide two manifest file (the fdroid one with the permission).
Should I wait replies from that thread?

from tui-consolelauncher.

Should I wait replies from that thread?

No

Ok, split them, that was not my question, why do you need a different versionCode for F-Droid? How does that help with SMS?

from tui-consolelauncher.

Because the F-Droid version will probably get some updates before the play store version. If it's a problem I can find an other solution.

from tui-consolelauncher.

It's not a problem per se, but it (now) breaks autoupdates.

from tui-consolelauncher.

Do you think that there is a chance to fix this issue?

from tui-consolelauncher.

No idea

from tui-consolelauncher.

So, I'm going to unify the versionCodes. Is it a problem if I do it now? Is someone checking at the code?

from tui-consolelauncher.

The faster the better ;)

from tui-consolelauncher.

How is it going now?

from tui-consolelauncher.

Ref: https://gitlab.com/fdroid/fdroiddata/commit/122d5faed62ad65bbe534f83c82b6e68d36776c9

I see that now the versionName is vX.Y and Tag is vX.Y, as said above please keep it consistent and don't change it yet again in the future (eg. in the past versionName was X.Y but Tag was either X.Y or vX.Y), else autoupdate will break yet again.

from tui-consolelauncher.

Actually it's v6.13.1, should I change something?

from tui-consolelauncher.

No, that's my point. :)

from tui-consolelauncher.

Thank you very much!

from tui-consolelauncher.