Export & update of the older channel on the local drive

Observed behavior

Trying out a scenario that is presumably something users would stumble upon:

1. First I tried to import an older version of the GDL channel I had on one local drive, import was successful.

2. Next I updated that channel to the most recent version by importing from Studio, success again.

3. Finally I tried to export the same channel back to the local drive to update it, and the export failed.

Expected behavior

Should the users be able to update the local channel storage by exporting from an updated channel on the server, or this isn’t something we recommend? If not, should we make a note of that in the user documentation, and recommend that the export is always created anew, that is, from scratch?

User-facing consequences

Inability to update channels on local drives.

Errors and logs

Nothing in the console or network tab, logs are the same as in #5547. DB of the channel in question (from the local drive, original and after export):

0e173fca6e9052f8a474a2fb84055faf.zip

0e173fca6e9052f8a474a2fb84055faf-after-export.zip

Steps to reproduce

Let me know if you want me to upload the full KOLIBRI_DATA folder somewhere.

Context

• Kolibri version: 0.12.4b3
• Operating system: Ubuntu 16.04
• Browser: Chrome & Firefox

[radinamatic]

Well, it does seem to be a garden variety connection-with-external-drive issue, as after plugging out and in again, I’m able to export that channel and other too… 🤷‍♀️

I guess I was trying so hard to find a fault in various import/export scenarios, the unit finally got fed up with me, and refused to obey! bug-confirmation-bias 😂

[radinamatic]

Seems resolved, closing for now!