Altair: The selected file is either invalid or corrupted. Please check the file and try again.

[john-techfox]

Before I exported the data file then I restore data from it, but error. Please check this bug!
Altair Version 2.4.13 (2.4.13.6361)

[open-collective-bot[bot]]

Hey @john-techfox :wave:,

Thank you for opening an issue. We will get back to you as soon as we can.
Also, check out our Open Collective and consider backing us - every little help counts!

[imolorhe]

Hey @john-techfox, I just tested importing an exported data file and it works as expected. Are you sure you were restoring a valid file? If possible, could you share the file?

Note: the expected behavior is that Altair would restart immediately you select the file to restore with the data restored.

[john-techfox]

Hi @imolorhe , thanks for your support
Here is data file export from altair. How can i send the file ?

[PabloSzx]

Hi @imolorhe , thanks for your support
Here is data file export from altair. How can i send the file ?

You can make a zip containing it

[imolorhe]

@john-techfox Note: only share the file if you're comfortable that it doesn't contain sensitive information. If you're not confident about that, then check a couple of things about the file:

• it's content must be a valid JSON string (using JSON.parse(fs.readFileSync(filePath, 'utf8')) should be able to help here)
• the decoded JS object must have a version property set to 1
• There must be a localstore.altair__debug_current_version property specifying the version of Altair at the time the file was exported.

[arsenikstiger]

Hi,

I have the same problem, any update about it ?
I only export Data and restore, and it doesn't work with the same message.

[imolorhe]

@arsenikstiger Can you share the exported data? Or could you check the things I mentioned above as well?

[arsenikstiger]

@imolorhe
I can't share the data, so I checked what was into this agbkp file :

• version: 1
• in localstore, I have no localstore.altair__debug_current_version property

I edited the file by adding this property with value of 1, and restore works.
It means a fix must be done on the backup feature.

Last thing, the file stores too many data, like results of queries.
I think it's a bad practice and has nothing to do in a backup file.

Otherwise this app is great :)

[imolorhe]

@arsenikstiger Thanks for that information. That is quite useful. ~Can you tell me what the actual current version of Altair you are using is? Trying to figure out why it wouldn't have the version in the backup file.~ Actually never mind, we only set the current version after you have updated Altair at least once. I'll fix that.

Also about the too much data, why do you say it's a bad practice? The backup allows you restore your previous working session and environment. This also includes things like headers and environments.

Btw thanks for using the app!

[arsenikstiger]

The bad practice i was talking about :

• storing the results of the query
• storing the whole description of the schema

I'm not talking about configuration or context, but json results of queries (or docs).
That's nor working session nor environment, imho.

In fact, I think that all that is returned by a remote server shouldn't have to be backed up (graphql definition and results), because it would be invalidated next time you query for it.
Again imho :)

[imolorhe]

Altair doesn't only work with GraphQL servers. You can load local schema files directly into Altair to view the docs within Altair. This is the same graphql definitions you would normally receive from a remote server. I also display a the last updated time in the docs, so you have an idea of how stale the schema definitions are.

[arsenikstiger]

ok, I understand the use case 👍

[imolorhe]

The underlying issue here should be fixed now.