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

F-Droid #1

Open
swedneck opened this issue Oct 19, 2018 · 16 comments
Open

F-Droid #1

swedneck opened this issue Oct 19, 2018 · 16 comments

Comments

@swedneck
Copy link

Would it be possible to add this app to F-Droid?

@hazae41
Copy link
Owner

hazae41 commented Oct 24, 2018

Yes, you can submit it to FDroid if you think it should be 👍

@swedneck
Copy link
Author

Great, I'll submit a packaging request!

@swedneck swedneck reopened this Oct 24, 2018
@swedneck
Copy link
Author

Actually before i close this, could you confirm whether Sweet-IPFS complies with F-Droid's Inclusion Policy?

@hazae41
Copy link
Owner

hazae41 commented Oct 25, 2018

Yes, it does, thanks for your submit

@swedneck
Copy link
Author

Thanks!

@swedneck
Copy link
Author

@IzzySoft
Copy link

F-Droid maintainer here. Thanks for bringing this to us! Pending one of our developers making the build work (not being a dev I cannot tell if there may be any complications), it should show up soon. If you want screenshots to be shown in the F-Droid client, please take a look here for how to achieve that. Preferably you provide that via your repo (so you can easily replace them; btw that would also work for description and summary). Wouldn't even be "extra work for the F-Droid presence", as Fastlane/Triple-T would work for Playstore as well 😉

@hazae41
Copy link
Owner

hazae41 commented Dec 12, 2018

Hello, Sweet IPFS still does not appear on F-Droid
https://search.f-droid.org/?q=ipfs&lang=en

Is this normal ?

@hazae41 hazae41 reopened this Dec 12, 2018
@TPS
Copy link

TPS commented Dec 12, 2018

When @IzzySoft says, "soon" above (re: F-Droid inclusion), that usually means several months. Be patient, as F-Droid's run by a very small band of volunteers! Updates happen much more quickly after initial publishing, FWIW.

@IzzySoft
Copy link

When @IzzySoft says, "soon" above (re: F-Droid inclusion), that usually means several months.

Ouch. For the "usually" that is, @TPS. I was hoping for a better hit here… But "Amen" to the other two sentences.

@hazae41 please watch the state of the RFP. Once this goes to "close", it should hopefully be no longer than a week or two. I wasn't aware nobody had picked it up; just pinged the 3 most active "builders" to make them aware.

@licaon-kter
Copy link

@hazae41 Some help building: https://gitlab.com/snippets/1789429

What am I doing wrong?

@hazae41
Copy link
Owner

hazae41 commented Dec 20, 2018

@hazae41 Some help building: gitlab.com/snippets/1789429

What am I doing wrong?

Try with latest version of Sweet IPFS

@hazae41
Copy link
Owner

hazae41 commented Jan 9, 2019

Bump

@licaon-kter
Copy link

licaon-kter commented Jan 9, 2019

Didn't get a chance to test, will do.

/LE: @hazae41 What's up with the tags? The order is pretty strange, I can't enable Auto-update like this.

@licaon-kter
Copy link

licaon-kter commented Jan 9, 2019

Builds ok.

Now, regarding the Tags... I see more APKs but not enough tags, I see tags with higher values, etc. can these be fixed (older one purged or new one getting a higher value) ?

/LE: https://gitlab.com/fdroid/fdroiddata/merge_requests/4264

@licaon-kter
Copy link

java.io.FileNotFoundException: arm64
android.content.res.AssetManager.nativeOpenAsset(Native Method)
android.content.res.AssetManager.open(AssetManager.java:744)
android.content.res.AssetManager.open(AssetManager.java:721)
fr.rhaz.ipfs.sweet.Daemon$install$2.invokeSuspend(Daemon.kt:63)
kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:32)
kotlinx.coroutines.DispatchedTask.run(Dispatched.kt:236)
kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:594)
kotlinx.coroutines.scheduling.CoroutineScheduler.access$runSafely(CoroutineScheduler.kt:60)
kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:742) 

Something wrong with the build?

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

5 participants