CellularPrivacy / Android-IMSI-Catcher-Detector

AIMSICD • Fight IMSI-Catcher, StingRay and silent SMS!
https://cellularprivacy.github.io/Android-IMSI-Catcher-Detector/
GNU General Public License v3.0
4.73k stars 946 forks source link

F-Droid builds need special workarounds #819

Open SecUpwN opened 8 years ago

SecUpwN commented 8 years ago

Thank you for your feedback! Please add below details so that we can help you a bit faster.


Agreements

Please check these boxes to ensure you've actually read and understood these important rules!

  • [x] I have reviewed and accepted the guidelines for contributing to this project.
  • [x] I have searched the open Issues and made sure I am not filing a duplicate.
  • [x] I have read the notes on debugging and will properly maintain this Issue.

Overview

Please add a short and easy to understand description of the Issue you've experienced here.

First introduced with 0.1.40-alpha-normal, the metedata of our app on F-Droid seems to need a special workaround and a forced version to be able to be built by F-Droid. We need to fix this to prevent nagging @krt and other F-Droid members. Thanks for digging a bit deeper into this, @larsgrefer!

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'com.SecUpwN.AIMSICD'.
> No signature of method: java.util.ArrayList.toSorted() is applicable for argument types: (org.codehaus.groovy.runtime.NumberAwareComparator) values: [org.codehaus.groovy.runtime.NumberAwareComparator@1160497]
  Possible solutions: toSet(), toString(), toString(), toString(), toString(), sort()

Reproduction

Please tell us the detailed steps on how to reproduce your Issue here.

Please see the attached logfile of the F-Droid build server. @f-droid, can you point us to what is wrong?


References

If your Issue is related to any other existing Issues or pull requests, please link them here.

https://gitlab.com/fdroid/fdroiddata/issues/423

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Kaicastledine commented 8 years ago

Hello I've just downloaded 0.1.41 alpha via FDroid and Have had the following issues - running on CM12.1 on a Xperia Z2

.Request API key crashes app .Downloading database after entering in API key - Says check connection regardless of 3G or wifi .Downloaded database and moved to SD scan in Files/OpenCellID/ in android data folder but does not show any data REF:https://github.com/CellularPrivacy/Android-IMSI-Catcher-Detector/issues/435

SecUpwN commented 8 years ago

Hello I've just downloaded 0.1.41 alpha via FDroid and Have had the following issues

Good evening @Kaicastledine, please do not cross-post your Issues in Issues with different targets. I recommend you to wait for the upcoming release this sunday since your Issues may have been solved. Alternatively, if you cannot wait to test out the latest changes, feel encouraged to compile it yourself.

Kaicastledine commented 8 years ago

Apologies, Great news indeed, Will wait for the update. Many thanks

SecUpwN commented 8 years ago

@mimi89999, would you please have a look at this and see if you can fix this for todays release?

mimi89999 commented 8 years ago

That's impossible. It's 22:45 in my timezone and I have to wake up early tomorrow...

SecUpwN commented 8 years ago

That's impossible. It's 22:45 in my timezone and I have to wake up early tomorrow...

Ok, seems like we're living in the same timezone (I'm in Germany). Don't worry about it today.

mimi89999 commented 8 years ago

Well, this could be just added to build.gradle.

I'm waiting for a reply from F-Droid about gradle 2.12 on the buildserver...

ghost commented 8 years ago

Sorry for late reply, but I am rather busy. The workaround is just forcing a gradle version. The original problem was that the gradle version matching the android plugin was really old.

SecUpwN commented 8 years ago

The workaround is just forcing a gradle version.

Thanks for taking the time to reply, @krt16s. Does that mean I'll always have to do stuff like

    init=echo 'task wrapper(type: Wrapper) { gradleVersion = "2.11" }' >> ../build.gradle
    gradle=normal
    forceversion=yes

I'd like to get back to the state where I just had to use gradle=normal without forcing anything. Reason is, as you can see, that you have additional work fiddling with our metadata each time. Not so good.