Copy link to clipboard
Copied
Hi there,
I have a big problem regarding Character Animator on my iMac. I can't open my Character Animation project because I get the following error:
'libgit2 error -3(9/Object not found - no match for id (91b93d9ec61fe14acd59e1c288d6373f0debd39c)) returned from git_revparse_single(&headP, repoP, specZ)'
My project is located in the Adobe Creative Cloud, and I know by looking up this problem on different forums that usually a conflicted copy of the 'odb.sqlite3' file is the problem and that it should be fixed if you rename the conflicted file to 'odb.sqlite3' and delete the old one, but that doesn't fix the issue for me unfortunately.
I have also tried to add an empty directory named 'objects' but that doesn't work either.
Can someone help me? I don't want to lose all my work.
Copy link to clipboard
Copied
I can take a look at the project and see if I can diagnose or repair it if you zip it up and send me a download link (via private message if you prefer). If the project is large or you don't want to send the artwork, for this error I most likely only need the contents of the Ch Data/repo.noindex subfolder (which should be much smaller to package and send).
Dan Tull
Copy link to clipboard
Copied
One other thing: if there were previously multiple odb.sqlite3 derivative files (conflicted copies), include all of them that you have. I think I've seen at least one case where I needed to merge them to fix the project.
DT
Copy link to clipboard
Copied
Did Adobe fix this yet?
Copy link to clipboard
Copied
The potential is still there for this to happen. There's an issue that seems to be a CC files sync bug, but has been tricky to confirm. Since part of the issue is the database being out of sync with loose files that point to project states, I think we could also make this easier by pulling those refs into the database as well (so at least they won't be inconsistent), but have not done that yet.
DT
Copy link to clipboard
Copied
Getting the same error on my Mac. Have moved the project file, uninstalled CA and removed preferences, reinstalled with no success. Would you please advise?
Copy link to clipboard
Copied
If you zip up the project (or if that is too big, the Ch Data\repo.noindex folder) and send me a download link (Dropbox, Google Drive, whatever) via private message, I can take a look.
DT
Copy link to clipboard
Copied
Here you are sir.
Copy link to clipboard
Copied
Hi I'm using a Macbook pro having the same issues, I would like some help 😞
Copy link to clipboard
Copied
Thank you, I will send the project to you right away!
Copy link to clipboard
Copied
The same is happening to my files, is there an update to fix this bug in CA.
Adil
Copy link to clipboard
Copied
This is really bad, DanTull​.
Through trial and error I had to rename the "conflicted" copies of the .sqlite3 file to the original odb.sqlite3 filename. Then I was finally able to open the project.
Also, is it normal for Character Animator projects (.chproj) files to always show as being Zero Bytes in size? That was enough to cause me concern when my project wouldn't open back up.
Copy link to clipboard
Copied
Glad you were able to get it to open again.
Out of curiosity, which application's sync folder was the project within? Also, did you ever have the project open on more than one computer or what the conflict spurious? I do have an issue open for a problem I saw where a sync'd folder managed to get conflicts when only one machine was actively using it, I think due to "echoes" from another pair of machines signed into the same account (a fairly tricky and dangerous sync bug).
DT
Copy link to clipboard
Copied
Hi DanTull​,
I had created a new Character Animator project from scratch and had it saved within one of my Creative Cloud folders. I do have two machines tied to account for syncing, and I think my Macbook Pro may have been on and actively syncing while I was working on the project on my iMac, so this may have caused the syncing "echoes" issues you mentioned. I did not at any time open the project on the Macbook Pro — I had just closed the project and had reopened it, and that was when I received the libgit2 error.
Though, it did give me a bit of a fright after encountering the error and seeing that the .chproj file was zero bytes! But I'm glad to discover that this is normal and that the important files are the contained folders.
May I suggest that Adobe mention this in the program documentation? Having an empty project file like this seems like a unique situation when compared to the behavior of other Adobe apps.
Thanks again for your help!
Pat
Copy link to clipboard
Copied
I was having this same issue. I had my project in the Documents folder on my Mac and was backing up that folder to iCloud. I located the odb.sqlite3 file and noticed it had the cloud icon with the arrow next to it which usually indicates that it hasn't been backed up yet.
I clicked the cloud and it sunc that file and when I went to open my project again everything was back up and running!
Any idea why this may have happened?
Thanks!
Copy link to clipboard
Copied
The .chproj files are *always* empty. They are just a file extension to click on and associate the application with. The SQLite database files contain all the real content.
Copy link to clipboard
Copied
I ran into this issue when I first started Adobe Character Animator. In fact, every project would error out after a day or two. One thing that helped was to store files locally, rather than my creative cloud drive and to make sure you file permissions were set up correctly (give yourself full access to what every directory your saving too).
If there are any pros or support specialists on this thread:
Can you provide us with the best use guide in terms of saving files? I'd love to stop using local storage as my computer is getting weaker and weaker as the days go by and I'm afraid this won't be a sustainable workflow.
Thanks!
Rob
Copy link to clipboard
Copied
DanTull managed to save part of my project, but I do the same thing now. I store my projects locally because I don't trust saving them on the cloud anymore. (Which is quite annoying because then my colleagues can't acces them, but better safe than sorry I guess.)
A possible 'fix' is renaming the conflicted copy of the .sqlite3 file to the original obd.sqlite3 file, just like Pat Lee Media said, but I hope Adobe fixes this problem as soon as possible.
Copy link to clipboard
Copied
I don't know if there will ever be a solution. The following is my technical understanding of the problem.
Many applications update a file by opening it, reading the file, closing it. Or they open it, write it, close it when you select "Save". If the application uses a database however (CH uses SQL Lite 3), the application keeps the database open while running. It does not expect anything else to touch or try to modify the file.
If the cloud sync and application try to do things to the file at the same time (e.g. CH closes the database then tries to open it for update; but the cloud sync software is busy still writing the large database file to the cloud since nobody else is using it), then problems occur. CH cannot write to the file because the cloud software has locked it from update (it wants to make sure nobody else can modify it or else the copy being made may be corrupt / half done). But if CH cannot finish an operation, it can leave the database file in an inconsistent state.
Anyway, some of the above may not be completely correct. But I think the problem is CH has a database under it, which is held open for longer periods of time, and is quite large in size. So it happens in more than other applications that hold everything in memory and just read/write a file when required.
The only solution I know of is to make sure the CH files are not on a folder backed up by cloud sync software. To do a backup, I copy the directory tree over to a backed up area periodically while CH is not running. But it is not safe to share the CH files between two authors concurrently. You can export a puppet and send that to other team members, but you cannot have two people editing scenes in the same project concurrently. That is not safe.