Logs submitted.
As a quick note, I’ve gotten a full sync now. I had four issues during the process (which involved pulling down ~1.3 TB of data, and then moving ~30 GB of that data to other accounts. Almost all of these issues match those described in other forum threads, and I thus don’t think they’re ARM64-specific.
-
Intermittent crashes of
insync-headless status. These crashes only occurred during the first third of the sync process, and may be related to Insync trying to get a handle on my very large data set. -
A “Daily Limit for Unauthenticated Use Exceeded” error. This would cause files (and sometimes entire folders) to hang for minutes (files) to hours (folders). However, Insync always eventually recovered.
-
Possibly related to the above, at some point during the initial sync every account that I added eventually took one error that caused
insync-headless error listto prompt me to “log in again”. However, after indicating that I wanted to log in again, Insync then continued normally. Both consumer accounts took this error relatively early in the sync process, but my Workspace account took it somewhere after the half-way mark. Genuinely not sure what to make of this. -
Finally, towards the end of the process where I was re-arranging (and thus uploading) ~30 GB of data, Insync began taking a different rate limit error. This error didn’t clear up when I just let Insync run overnight (no back-off?), but taking the suggestion from the linked thread to just turn off Insync for an hour and then start it back up again worked around the issue.
That all sounds like a lot, but every single one of these issues could be worked around, and most of them have occurred in non-ARM64 builds… So at least in my testing this build seems good.
Thank you for your team’s work with this — having an ARM64 build of insync-headless will make my life a lot easier. I hope that it continues to get support and development!