Python Error - Google Foobar

This may not be the answer you're looking for, but that first "bytes" string is a base64 encoding of the following error message:

"Could not find 'answer' function".

I've done the Foobar challenge myself, and that should only happen if you are trying to verify a file that is missing a defined "answer" function, which obviously you are not. Are you certain that the spec they provide has 3 arguments vs an array with 3 items?

The second message (CAEQARABEAEQARABEAEQARABEAEQAQ), while valid base64, doesn't map to ASCII or UTF-8. After some closer analysis of some of the other strings others have posted, I've concluded that this is the base64 encoded version of the test output. It isn't very human readable, but I believe it is 11 2-byte chunks, the first of which is unhelpful, but the following 10 are the test result for each of the corresponding test cases. In the case of this message it converts to binary as:

0000100000000001 <- unknown pre-pended info0001000000000001 <- passing test 10001000000000001 <- passing test 20001000000000001 <- passing test 30001000000000001 <- passing test 40001000000000001 <- passing test 50001000000000001 <- passing test 60001000000000001 <- passing test 70001000000000001 <- passing test 80001000000000001 <- passing test 90001000000000001 <- passing test 10

The '1's at the end of each of these lines indicates that all 10 tests are passing.

A failing test case is represented by the following string:

0001000000000000 <- failing test case

This should help you (and others) continue testing to achieve fully passing tests (you can complete your own analysis with tools like this one: https://cryptii.com/base64-to-binary), but unfortunately this will not help you move forward with your final submission until Google remediates the issue on their end.

UPDATE: July 2, 8PM PDTAfter reaching out to a couple of Google recruiters about the issue they were able to confirm that the issue was identified and is believed to be resolved today.If you re-save your code after making a change to it (whitespace should be fine), you should be able to test and submit correctly. Alternatively, you may now be able to request a new challenge anyway.

There will be nothing for you to solve this issue, it is a issue on Google's site, as the Google Foobar API is responding with this message as I've found out.

Notherless your best bet will be to use the feedback command and give Google Foobar a feedback and mark it as a bug. This will be more likely to reach their attention and helping them to fix this issue!