So this is where the error occurred (xtractor.py line 89).
The 'files' key was not in the downloaded archive which means almost assuredly the participant didn't complete the takeout procedure correctly. Especially so since it continued to work for test cases afterward. An exception could be that the participant was part of some A/B testing where Google gave a different file structure for that particular case. I will write a more user-friendly message here to let you know when the archive content was not correctly structured. I should not be using that direct key request anyways. I'm also going to write in a more detailed logging scheme to show a bit of the stack trace information when something like this occurs.
So this is where the error occurred (xtractor.py line 89).
The 'files' key was not in the downloaded archive which means almost assuredly the participant didn't complete the takeout procedure correctly. Especially so since it continued to work for test cases afterward. An exception could be that the participant was part of some A/B testing where Google gave a different file structure for that particular case. I will write a more user-friendly message here to let you know when the archive content was not correctly structured. I should not be using that direct key request anyways. I'm also going to write in a more detailed logging scheme to show a bit of the stack trace information when something like this occurs.