Nidal Bakir

Sure, but I can not find a way to mock the `_ParseDioClient` class to fake the `DioError`. I was thinking of adding a **typedef** like this: `typedef ParseDioClientForMockTest = _ParseDioClient;`...

We can support the old directory path by doing something like: ``` dart Future getDatabaseDirectory() async { if (Platform.isIOS) { if(await _isDatabaseFileExistsInOldPath()){ return (await path_provider.getApplicationDocumentsDirectory()).path; } return (await path_provider.getLibraryDirectory()).path; }...

@mtrezza I'm sorry, I did not mean to close the PR! I did not know that if I deleted the forked repository from my account all my PR would be...

same for me!!

Reopening in a different PR because I lost all the progress and the reference of these changes. The new PR [pull/825](https://github.com/parse-community/Parse-SDK-Flutter/pull/825)

I think I came late to this PR because there are 31 comments and only 6 lines changed. Is there anything I should know?

Fix via #860

@exaby73 In your **app/build.gradle** change **jdk7** to Java **jdk8** ``` dependencies { implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk8:$kotlin_version" } ``` So it will not complain about `kotlin-stdlib-jdk8-1.5.30.jar(version 1.5)` The conflict will be between: `kotlin-stdlib-jdk7-1.6.10.jar...

@stuartmorgan Just a side note... If you try to rebuild the app without executing the `flutter clean` command. The build will run without any errors! I do not know why...

And as for now, is there any workaround? Thanks.