TEST 3: How to fill up your account with the Demo App

Apps
1

There are some limitations for using the TEST 3 network. Just like with TEST 1 and TEST 2. Here they are:

  • Your Vault won’t take more than 100MB. Want more? Just start an extra Vault.
  • Your account can’t be more than 100MB as well. Here’s the code.

740×93 10.6 KB

So here’s what you can do to use all the 100MB.
Fist of all, don’t choose “Upload directory” when you upload private files. The demo app will see this as more than 5MB. if the map is bigger than that and will give an error. Instead, upload files one by one. But there’s another thing to look at, remember files are chunked in 3 pieces at least, and the 100MB. storage on your account is actually 100 units. So when you upload 33 little .jpeg files you might have filled your account space already, triggering 100 units.

The trick is to take a file and split it using a program like winrar. I have a 70MB. videoclip and did a spilt to 5MB. pieces. But for some reason, the 5MB pieces gave an error. So after that I re-rarred the thing to 4MB. pieces and I’m uploading them 1 by one. The demo app is having trouble connecting to the Launcher now and then, but when I restart them both I’m good.

793×287 21.2 KB

This is just a temporary thing to get around some errors and limitation. Without hacking any code :yum:.

5 Likes
2

On Linux here… I got no error initially, trying to upload 7.1MB directory with the largest file being just 1.3MB. It just tries and then fails with an error.

So, eventually at ~90% the launcher gave an error:

thread '<unnamed>' panicked at '

 ====================================================================================================
| Result evaluated to Err: CoreError::MutationFailure::{ reason: LowBalance, data: ImmutableData f7ad..} |
 ====================================================================================================

', src/core/self_encryption_storage.rs:59
note: Run with `RUST_BACKTRACE=1` for a backtrace.
thread '<unnamed>' panicked at '

 ======================================================
| Result evaluated to Err: "PoisonError { inner: .. }" |
 ======================================================

', src/core/self_encryption_storage.rs:59

Repeated that twice and I’ll log it as an issue as really all never events should be taken care of gracefully.

1 Like