Instead lets just use the path_provider. This was being used as for some
reason I wanted the files to reside inside the 'files' folder and not in
the 'app_flutter' directory.
However, that requires maintaining a fork of path_provider, which I no
longer want to do.
Related to #125
This still needs to be integrated into the Flutter Markdown renderer.
But the good news is that this works!
It currently requires network access to download the katex scripts. It
does NOT send the katex string to any server. The rendering is performed
in the app.
The Git Api was strange and took a foldeName and it would only allow you
to access git operations in a particular path. This has now been fixed,
and now it can operate in any path.
This was the first step to moving the git api into its own library.
* Set target to be 9.0 - libgit2 has been compiled with the target of
9.0, so for now lets support that. Later we can figure out how to target
8.0, if required.
* Set the BUILD_NUMBER and BUILD_VERSION correctly. In new flutter
projects these values are automatically set, but since I created this
project before those patches went it, we need to set it up.
* Do not target only arm64.
* Set the correct CFBundleName. It was set to 'journal' instead of
'GitJournal'.
It needed the SWIFT_VERSION variable to be set, and for it to be set to
a version that exists on my system. I'm pasting the error over here so
maybe I google search will help a lost soul in the future -
`flutter_email_sender` does not specify a Swift version and none of the targets (`Runner`) integrating it have the `SWIFT_VERSION` attribute set. Please contact the author or set the `SWIFT_VERSION` attribute in at least one of the targets that integrate this pod.
https://github.com/sidlatau/flutter_email_sender/issues/8
The Podfile and lockfile have all changed since the dependnecies have
changed so much (because of the AndroidX update). I've had to comment
out the flutter_email_sender for now, since I just cannot seem to get
it to work, in fact, even the current build is a hit and miss.
It just seems to make a lot of changes. No idea about half of these. The
ios world is strange and foreign. I have hooked it up to Firebase
Analytics, though.
Also build on all architectures instead of just 64-bit.
