TinyDB. Restore after app reinstall or wipe date

[Korneich]

Good day to all!
I have encountered a seemingly simple problem - saving a TinyDB backup and restoring it after reinstalling the application or deleting its data. It seems that I have already gone through the circle of different extensions several times: ETinyDB, MFile, TinyDBx...
Please - tell me how I can implement the ability to periodically save a TinyDB backup to a file and then restore it after reinstalling the application.

When restoring after clearing data - such an error

Thanks in advance for your help!

[Taifun]

You will need SAF to access non media files, which your app does not own

Some basics on Android storage system

From an Android point of view there are an → Internal Storage and an → External Storage . 1. Internal Storage The Internal Storage can only be accessed with a rooted device. 1.1 The app package is saved in /data/data/<packageName>/ In order to be able to debug your app, AI2 saves the assets for → Companion on devices with Android ≥ 10 (API ≥ 29): /storage/emulated/0/Android/data/edu.mit.appinventor.aicompanion3/files/assets/ Android < 10 : /storage/emulated/0/Android/data/edu.mit.a…

SAF: App Inventor implementation of Storage Access Framework

1.Introduction Description: Basically AI2 wrapper of Storage Access Framework. Using this extension, you can get read and/or write access to a single document or tree document (and all of its children recursively). Latest Version: 1.3 Released: 2021-09-16T18:30:00Z (UTC) Last Updated: 2023-11-15T18:30:00Z (UTC) 2.Blocks [image] [image] [image] [image] [image] [image] [image] [image] [image] 3.Documentation EventsErrorOccurredEvent indicating error/exception h…

Panacea - Is SAF the answer to Android File Restrictions?

[SAFLogo2] A guide for using the basics of SAF (Storage Access Framework) for all Android versions, to overcome the many file restrictions Android has placed upon AppInventor developers. This is just about SAF, so please keep any comments related to that. It is not about other aspects or methods for the android file system.

Taifun

[Korneich]

I would be grateful if you could tell me how to implement this. I am a beginner and I can't figure out such a large number of blocks.

[Kumaraswamy]

Use the FilePicker to allow the user to select the file, then use File component to read the file's content. Then give it to ETinyDB

[Korneich]

thank you, I will try

[Korneich]

@Kumaraswamy

FilePicker

Please tell me where to get FilePicker ?
Here?

[Kumaraswamy]

[ABG]

You can do this without extensions or files too.

TinyDB has a block that can dump its contents into a dictionary.

Dropping a dictionary into a sharing component text stream block can feed the contents cross platform to your email or text editor apps as a JSON text string.

Coming back, the AI2 textbox should be able to accept an Android paste of a text copy done from the email client or wherever you saved the JSON text string.

The web component has a block that can decode the JSON text into a dictionary.

There is a for each key and value loop block that can traverse the dictionary.

Loop through the dictionary and reload TinyDB from the dictionary, using the keys as tags, value for value.

[Korneich]

@ABG

You can do this without extensions or files too.

I saved your message. Thank you very much.

[ABG]

Error 2104 I need help

I had a typo in my URL, so the download failed. This version is more transparent: [blocks (1)] TinyDB_web_paste (1).aia (3.0 KB)

You're not the first to ask for this.

Here's the sharing code:

[Korneich]

@Kumaraswamy

Use the FilePicker to allow the user to select the file, then use File component to read the file's content. Then give it to ETinyDB

Thank you very much to you and everyone who helps!
Everything worked out.
The preliminary version is in the screenshot below. In the final version for my application, I will format it a little differently, add the date and time to the file name, and add "Share".

[Martin_Herraiz]

I suggest you to save the important parameters of each user of the app in its own label of a FireBase data base, so key data can always be retrieved, even if the user changes it's mobile phone, or the device where the app is used.

[Korneich]

@Martin_Herraiz

I suggest

The user will be able to save their backup file anywhere in order to restore it later.

[Martin_Herraiz]

With FireBase, it can be done in such a way that the restore procedure is automatic.
If the app starts without user data in tinydb, then asks: Are you a new user and want to register, or do you want to recover your previous data?

[Korneich]

Thanks, but this is probably the next level for me.
I had a hard time logging in through the FireBase using the user's private key and the device ID . But I implemented it