I have a portfolio in Google Drive. When I try to load from Drive, I got the error “XML Format not valid” but when I try open with my Android, it is open without problem. So, the Drive version is not corrupt.
The Android app can only read the binary format. So if Android is able to successfully read the file, then I find it very strange how the desktop version can have an XML error…
First question: if you make a copy (!) of the “MyPP.backup-after-open.portfolio” and name it “my-test.portfolio”, can you then open it?
Second question: how old is the file? I know there are binary files that contain XML (but those cannot be read by Android).
same problem renaming “MyPP.backup-after-open.portfolio” to “my-test.portfolio”.
mybe I didnt explain well. The problem happens when the desktop version try to open the PP located in Google Drive. With android’s app works fine. I started use PP this year.
I did the following test:
I copied the version located in Google Drive to my computer and then opened the new local version. PP open it correctly.
Could you kindly provide further details about your PC environment, please? OS, PP version and how your are sync with Google. How did you access the portfolio file, via the local synchronized file in the GDRIVE folder structure?
I configured my Google Account from Settings > @Online Accounts. So, in File appears the remote folder (google-drive://account@gmail.com/).
Then, from PP open access to this remote folder and goes to folder where is located all files of PP. I never receive the option to enter the password like happen when it is open a copy in local folder.
So I am really not a Linux guy, is this the normal syntax for file access in the Linux world? For me as a windows user, the path more sounds like that is just a connection and the file would be downloaded in the background by the system and just this “copy” ist used. May that explains the issue and would explain why a manual copy would work. But here @ProgFriese is our real expert in Linux world I guess.
When discussing with ChatGPT, it suggests I may not check for the file signatures properly. Or the Google Sync layer may change it. Maybe the dump can tell us more.
Looks like gnome-online-accounts. I don’t know that tool.
The problem for me is the combination of a remote drive with Flatpak. Is Google Drive mounted in the user space here or not? If not, does Flatpak have full rights to it? I don’t know.
I guess that’s again the issue here. That would also fit to the fact, that both hex tests looks like the same. Because they aren’t created in the context from Flatpack.