Hans-Christoph Steiner 978f4a2928 ignore potential filesystem corruption ...

As nice as it would be to help the users, F-Droid is not well positioned to
help the user with this problem.  The Android OS itself should do it. Plus
this issue has been open a long time, without much work on it, and the
existing solution is causing crashes.

#855
!440
!581

Utils.getBinaryHash() is used in a lot of places in the code, so its not
easy to handle this specific issue.  Here's one example:

org.fdroid.fdroid.Utils$PotentialFilesystemCorruptionException: java.io.IOException: read failed: EIO (I/O error)
	at org.fdroid.fdroid.Utils.getBinaryHash(Utils.java:426)
	at org.fdroid.fdroid.AppUpdateStatusService.findApkMatchingHash(AppUpdateStatusService.java:159)
	at org.fdroid.fdroid.AppUpdateStatusService.processDownloadedApk(AppUpdateStatusService.java:110)
	at org.fdroid.fdroid.AppUpdateStatusService.onHandleIntent(AppUpdateStatusService.java:65)
	at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:65)
	at android.os.Handler.dispatchMessage(Handler.java:99)
	at android.os.Looper.loop(Looper.java:137)
	at android.os.HandlerThread.run(HandlerThread.java:60)

2018-03-07 22:51:39 +01:00

..

libs/binaryDeps

move main project files into standard gradle/Android Studio layout

2016-03-28 12:12:37 +02:00

src

ignore potential filesystem corruption

2018-03-07 22:51:39 +01:00

tools

move all translation scripts to tools/

2017-05-10 23:18:28 +02:00

build.gradle

versionCode 1001003

2018-02-13 22:05:56 +01:00

lint.xml

lint: make UnusedResources an error

2017-05-31 17:29:40 +02:00

proguard-rules.pro

support new index-v1 format using Jackson parser

2017-03-31 09:09:31 +11:00