This PR moves all string literals into the ARB file.

How to review

• At the codebase:
  • Ensure the text is replaced with the correct internationalization variable
  • Ensure the Text that was in upper case calls toUpperCase() after the replacement
• At the ARB file:
  • Check that the description gives the right context information to understand the text
    • Check for ellipsis: is the substantive omitted? If so, is it implicit in the description?
    • Is it talking about plural or singular verbs?

Overview

For getting the metadata data while syncing we are not retrying for 5xx status code responses, this leads to a false positive and we also don’t retry to get the metadata properly.

Errors

In order to track in a better way the errors, the class ArDriveError will be responsible for being the base class for exceptions. The class NetworkError will be the base class for all network errors, having its implementation on: ServerError RateLimitError NetworkTimeOut UnknownNetworkError Those errors are well known and will help us to improve our error handling.

HttpRetry

This class abstracts the retry logic for dart:http library requests. For handling the response, we'll use the GatewayResponseHandler class. For RateLimitError we won't retry. It is because we need to wait until be free of the rate limit.

Upgrade Flutter version

Update the Dart SDK and the versions of outdated packages.

Motivation

With the current version of Dart 2.13.0 we aren't able to update the version of Flutter to the latest: 2.10.3. To know more about the improvements in this version, see: Flutter 2.10.0 improvements.

Adds extra tagging for the Flutter App to distinguish the platform from where it was uploaded.

--- Releases --- Android release: https://appdistribution.firebase.google.com/testerapps/1:305132849030:android:6cf0cd5ec064fad3ffce07/releases/5tufi7h8vct90 iOS release: https://appdistribution.firebase.google.com/testerapps/1:305132849030:ios:06ea33a95a2e0d42ffce07/releases/44njrtdqphdf8

In the test phase of the mobile app is very important to have a tool to log errors on release mode applications. To do so, we’ll use the FirebaseCrashlytics. We won’t enable it on production.

--- Releases --- iOS release: https://appdistribution.firebase.google.com/testerapps/1:305132849030:ios:06ea33a95a2e0d42ffce07/releases/02dj3i89vddag Android release: https://appdistribution.firebase.google.com/testerapps/1:305132849030:android:6cf0cd5ec064fad3ffce07/releases/1gpcb7gid0s3g

Changes

• Ports the safe types: ArweaveAddress, Winston, and TransactionID from CORE into Dart
• Implements a Builder for the contract state
• Implements the ContractReader interface
  • Implements RedstoneContractReader
  • Implements VertoContractReader
  • Implements SmartweaveContractReader
    • which refactors the implementation of web-pst to simply read the contract (removed the TS code that is already ported to Dart)
• Implements the ContractOracle ~interface~ class
  • Implements ArDriveContractOracle (the composite class; implements ContractOracle)
• Implements the CommunityOracle ~interface~ class
  • which makes use of a ContractOracle (e.i. the composite class) to make high-level computations
• Injects the CommunityOracle to the PSTService

TODO

• ~Make the weightedRandom method testable~

The rules for Inferno are written in English and Chinese, yet the in-app fire icon only directs users to the English rules page. We need to ensure that users of the Chinese version of the app are redirected to the Chinese rules page.

This PR adds the create manifest feature for public drives.

The cubit/form/state patterns are largely extended from the existing code as I was learning to work with the Flutter codebase and learn Dart in general. Specifically, create manifest uses a similar flow to the ghost folder cubit as suggested by @jdaev.

I've extracted some logic for the manifest out into the new ManifestEntity class for testability where it made sense to do so here. I could continue, but its functional and I'm opening it up for review in its current state for feedback.

Experienced a public drive failing to sync/display due to a missing folder that other folders were referring to.

The drive gets stuck in a state where the loading symbol (on the file display portion, not in the sync dialog) is displayed indefinitely, with no drive data or controls available.

I've observed this to happen in the following filesystem layout: Root Folder -> Missing Folder -> Folder 1 (has files) + Folder 2 (has files) Only Folders 1 and 2 have files.

The absence of "Missing Folder" confirmed to be the cause of this issue as the problem drive now loads and displays properly after I manually created an ArFS-entity transaction for it.

This behaviour can be reproduced by creating a folder under the drive root folder that points to a Parent-Folder-Id that doesn't exist (using a made-up ID such as 1337babe-511a-dead-beef-ffffffffffff. Don't use that though. It's mine).

Currently, it seems that this issue has been fixed for the code that deals with shared drives (it gracefully displays the orphaned files in the root folder), but is still present when logged with a wallet that contains the drive.

Here's an error from an attempt of syncing the problem drive:

It may be that this bug is also behind of an issue of a substantial amount of my private drive files and folders not displaying in ardrive-web while visible and downloadable by ardrive-cli (fresh install, confirmed to be mined properly). Let me know once you've verified that this bug is fixed and I'll make another issue if this condition still prevails.

While typing a long password at login, the app freezes for a small moment every time. Sometimes it momentarily freezes when preparing an upload (the animation stops), and I've even observed it freeze completely during uploading a few times (it would seem that the uploads succeeded nonetheless).

It also does random logouts in a way that requires a full login (name, password and terms-accepting) instead of just asking for a password. These often happen right after an upload completes, sometimes at idle (perhaps triggered by sync).

I'm guessing the latter might be a timeout-issue stemming from the former. Something is probably done in the UI-thread that should be done in a separate tread/asynctask/whatever you flutter-people use.

This behaviour was observed using ArConnect, Chromium 92.0.4515.107, GNOME 40.3.0, Manjaro Linux (kernel 5.12.19-1). Might be just an issue with my system, but here's a report nonetheless.

--- Releases --- Android release: https://appdistribution.firebase.google.com/testerapps/1:305132849030:android:6cf0cd5ec064fad3ffce07/releases/5v0ui48plqlso iOS release: https://appdistribution.firebase.google.com/testerapps/1:305132849030:ios:06ea33a95a2e0d42ffce07/releases/5viu967cohe5g

--- Releases --- Android release: https://appdistribution.firebase.google.com/testerapps/1:305132849030:android:6cf0cd5ec064fad3ffce07/releases/7tkmn6sd5h3vg iOS release: https://appdistribution.firebase.google.com/testerapps/1:305132849030:ios:06ea33a95a2e0d42ffce07/releases/05cfaus0p4qs0

--- Releases --- Android release: https://appdistribution.firebase.google.com/testerapps/1:305132849030:android:6cf0cd5ec064fad3ffce07/releases/7fphmbta7de0o iOS release: https://appdistribution.firebase.google.com/testerapps/1:305132849030:ios:06ea33a95a2e0d42ffce07/releases/3qstngar8mgc0

--- Releases --- Android release: https://appdistribution.firebase.google.com/testerapps/1:305132849030:android:6cf0cd5ec064fad3ffce07/releases/2fkbant0feeig iOS release: https://appdistribution.firebase.google.com/testerapps/1:305132849030:ios:06ea33a95a2e0d42ffce07/releases/3nqedj90285do

Integration branch for the Story's sub-tasks.

--- Releases --- Android release: https://appdistribution.firebase.google.com/testerapps/1:305132849030:android:6cf0cd5ec064fad3ffce07/releases/7unj2boou3560 iOS release: https://appdistribution.firebase.google.com/testerapps/1:305132849030:ios:06ea33a95a2e0d42ffce07/releases/56ec6b5bfal0g

--- Releases --- Android release: https://appdistribution.firebase.google.com/testerapps/1:305132849030:android:6cf0cd5ec064fad3ffce07/releases/4si2aomlsk9v0

--- Releases --- Android release: https://appdistribution.firebase.google.com/testerapps/1:305132849030:android:6cf0cd5ec064fad3ffce07/releases/0mhrgcr47h4f8 iOS release: https://appdistribution.firebase.google.com/testerapps/1:305132849030:ios:06ea33a95a2e0d42ffce07/releases/3dm08s97eok08