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

Distribution on F-Droid #1

Closed
DragoonAethis opened this issue Jan 21, 2015 · 18 comments
Closed

Distribution on F-Droid #1

DragoonAethis opened this issue Jan 21, 2015 · 18 comments

Comments

@DragoonAethis
Copy link

Since there are quite a few devices without Google Play (either because Amazon and Friends or willingly), F-Droid would be a good place to distribute the app for everyone else. https://f-droid.org/

@SyncedSynapse
Copy link
Member

I'll look into it, though i guess it can't be distributed as-is because there's currently a dependency on Google Play services which kind of defeats the purpose of F-Droid.

@SyncedSynapse
Copy link
Member

(Fat fingers on previous close)

@logomancer
Copy link

Integrating Dominik Schuermann's Android Donations Library may be a way forward. This would also let you support donations out of Google Play.

@SyncedSynapse
Copy link
Member

Thanks for pointing that out. My issue wasn't the donations, it's that there needs to be different build configurations (product flavours in Android speak), and i still haven't used them. Shouldn't be hard, but i want to get the bugs out and do a little more polish first.

@ghost
Copy link

ghost commented Jan 22, 2015

I don't see play-services dependency within the source, is it just required to be installed on the system? We add an antifeature to such apps, but we can (and do) build them. Not all of ours users are able (or want) to have a enitrely google free phone...

@SyncedSynapse
Copy link
Member

You're correct, my previous comment was wrong: it doesn't depend on Play services, but it does use Google Play in-app billing.
Do you know if this is acceptable on F-Droid?

@ghost
Copy link

ghost commented Jan 23, 2015

As long as no non-free stuff is required at build time (doesn't look that way), we can build and ship it. As I said, I will mark it with an "anti feature", NonFreeDep in this case:

the application depends on a non-free application (e.g. Google Maps) - i.e. it requires it to be installed on the device, but does not include it.

Being not familiar with in-app billing, what is the point of the IAP_KEY? As we don't use api keys and such, will the app still be usable if we just use "foobar" as key?

@SyncedSynapse
Copy link
Member

IAP_KEY is the key that's used to validate responses from Google Play. It might show some errors if not set correctly. If you want the correct one, drop me an email and i'll send it (synced.synapse gmail).

Sorry, but i'm not familiar with the submission process on F-Droid. What am i supposed to do to submit it?

@ghost
Copy link

ghost commented Jan 23, 2015

Well, sending it to me would be essentialy the same as including it in the source repo, since we publish sourcecode for every build: Users shouldn't be required to trust us, but should be able to operate acomplete fdroid instance themselves, building everything on their own systems.. if they want to. Such a publication of the key will most likely not be covered by the TOS you agreed to, but I might be wrong.

I just enabled the build in https://gitlab.com/fdroid/fdroiddata/commit/0d87c2ba6eb06c41f0100aebd9aacdf85911fb89 since it builds installs and startsup fine. I cannot test it anyfurther as I don't have Kodi installed. I'll post the apk tomorrow when the buildservers has finished, so you can have a look at it.

@SyncedSynapse
Copy link
Member

Ok, i'll take a look tomorrow.

@ghost
Copy link

ghost commented Jan 24, 2015

@logomancer
Copy link

Looks good. In-app purchases are broken, as expected, which means that there's no way to unlock the custom themes. But other functionality works fine.

@ghost
Copy link

ghost commented Jan 26, 2015

@SyncedSynapse, is there a link for alternative donation methods you want to add?

@SyncedSynapse
Copy link
Member

It is blowing up as soon as you enter the settings, which is not supposed to. I'll take a look to check what can be done. Integrating with Google Play won't be possible, but it shouldn't blow up.

@krt16s No thanks.

@SyncedSynapse
Copy link
Member

@logomancer Can you please confirm that you can access the settings page?
It's throwing an exception on my account, but i suspect it might be my configuration.

@logomancer
Copy link

This is what I get when I try to access the settings menu: https://docs.google.com/file/d/0B5GHfURMehx2VzZIOENLUFVXNVk/

Running on a Galaxy S4 running OmniROM 4.4.

@SyncedSynapse
Copy link
Member

@logomancer Thank you very much. It's what i suspected. I guess that behavior is acceptable.

2 quastions:

  • How will the f-droid version be updated?
  • Can i close this issue?

@DragoonAethis
Copy link
Author

AFAIK F-Droid rebuilds the app whenever a new tag/release is made: https://f-droid.org/wiki/page/FAQ_-_App_Developers#Do_I_need_to_tell_you_when_I_update.3F - and yes, it's good to close. Thanks! :)

SyncedSynapse pushed a commit that referenced this issue Feb 2, 2015
poisdeux pushed a commit to poisdeux/Kore that referenced this issue Apr 25, 2020
Fix androidx migration for commandline builds
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

3 participants