Remove play-services about amazefilemanager

[VishalNehra]

OK, I'll look into it. Thanks for guiding.

[VishalNehra]

I've added a product flavor with name fdroid. It is not using the play services api and runs fine.
What to do next?

Release another version and ping me :)

[VishalNehra]

It's gonna take a while before we finalize new version. I'll inform you here once done.

[VishalNehra]

Sir, we've released new version, so you might wanna take a look for fdroid variant (:

[VishalNehra]

@krt16s could'nt find another way to communicate to you.
I published a new version of Amaze here on GitHub. Last one was around a year ago and this one has a year worth changes. It'd be great if you could add a new build on the Fdroid application page.

Well, actually you app was set to do automatic upgrades, however this only takes places once a day. Even if 24hrs had already passed, the update would have failed:

• The tag does not match the versionname ("v3.0.2 Beta 6" vs. " v3.0.2-beta.6")
• You included quite some jar files. Jar files are binaries that have to be replaced with source build versions. We allowed jcifs because we were less strict back then, it's a hassle to build and we verified it against upstream sources.

While I can try building them from source, I'd rather see that be done on your side. Both because I am rather short on time and because managing dependencies on our side is simply wrong :). Are those jars not available from central, jcenter or jitpack?

[VishalNehra]

OK, I've modified the tag.
The new jars' do have maven dependencies, but last time I checked, they were not working for me that's why I had to include their jar files.
Regards