ASCII图形显示为对Google的请求的JSON响应(ASCII drawing appearing as JSON response of request to Google)

ASCII图形显示为对Google的请求的JSON响应(ASCII drawing appearing as JSON response of request to Google)

我目前正在开发一个小型php库，它允许用户从Google Play开发者控制台访问数据，并将其插入到数据库中以供将来使用。

为了达到这个目的，我使用GET和POST请求（这部分仍然可以）对相应的Google服务进行身份验证，然后执行各种POST请求以获取我需要的所有数据。

一切工作正常，我从2或3周后就获得了脚本本身的功能（用于获取JSON响应），并且自那时起我每天都会启动它：没有问题。

今天，我试图再次启动它，并作为任何POST请求的JSON响应，我得到这个：

我发誓这不是假的，但它非常可怕。 Google现在在拖我吗？ 另外，控制台的Web版本仍然有效，似乎我的外部请求没有。

我正在开发一个本地主机，所以黑客的可能性接近（如果不是）0，而且我真的担心我将所有这些工作都付诸东流。

如果谷歌实际上试图让我无法获取数据，加上让我愤怒，他们的做法是正确的。

我一直在用各种关键字来搜索这个，但仍然没有运气。

I am currently working on a small php library which would allow users to access data from the Google Play Developer Console, and insert it into a database, for future use.

To achieve this, I authenticate into the corresponding Google service with GET and POST requests (this part is still ok) and then do various POST requests to get all the data I need.

Everything was working fine, I got the script itself functioning (for fetching JSON responses) since 2 or 3 weeks, and I am launching it on a daily basis since then : no problems.

Today, I tried to launch it again, and as a JSON response for any POST request, I'm getting this :

I swear this is no fake, yet it's quite scary. Is Google trolling me right now? Plus, the web version of the console still works, it just seems that my requests from outside don't.

I'm working on a localhost, so the hacking possibility is near (if not) 0, and I'm really worried that I made all this work for nothing.

if Google is actually trying to silence me from fetching data, plus making me rage, they are doing it right.

I've been googling this with all sort of keywords, still no luck.

最满意答案

其实，我已经解决了这个问题。 由于Google Webkit似乎会定期更改其JSON响应的格式，因此我的解析和正则表达式不再适用于获取用于身份验证的正确标识符。 我仍然认为谷歌正在兜售非官方API的用户或开发人员，但现在我已经找到了一个解决方案：手动检查我的解析函数，使它们适应各种正确的价值，并且再次运行。

这是一种痛苦，但如果有人遇到这个问题并到此为止，那么你就知道该怎么做了！

（我不能更精确，因为这些变化完全是随机的，但这些都是指导原则。）

Actually, I have solved this problem. As Google Webkit seems to regularly change the format of its JSON responses, my parsing and regular expressions were not working anymore to get the correct identifiers for authentication. I still think Google is trolling users or developers of non-official APIs, but now I have found a solution : manually check my parsing functions, adapting them to get every right value, and it's working again.

It's a pain, but if someone ever gets this problem and ends here, you know what to do!

(I can't be more precise, since these changes are totally random, but those are guidelines.)