這篇文章樓主似乎是對岸翻譯
附上原文

1. 14 October, GMT +0, 02:00 - The devs are making progress. They are mostly done with the obfuscation I think.
   
2. I hesitated to even update at all, because the situation is not much different than yesterday, the progress that has been made was expected. SafetyNet was annoying but not more than that. The level of expertise required to do debugging has dropped slightly, which means more people can help. (This still means you probably can"t help, but 2 years of experience instead of a neccessary 5+ is nice.)
   
3. As a filler I"ll talk a little bit about how the obfuscation works, the part that is not different than from the first API break. The encryption is somewhere inside the client, but the real deal is figuring out what parts of the encryption are actually used. The strategy from Niantic is putting a lot of bogus in the encryption "folder". The devs then need to filter out what is relevant, and what is not.
   
4. Now a lot of these bogus functions are still called, but their return value is just never used. You need to pay close attention to figure out the neccessary parts. Calling all those bogus functions also makes your phone slower by the way.
   
5. Now during the first API break figuring out what was bogus was a lot easier because they would skip the bogus. However, if they try to skip any function now (which requires altering the code), the anti-debugging measures come into action and they end up in an infinite loop. This is why the debugging is a lot more tedious.
   
6. 15 October, GMT +0, 01:00 - It seems like little progress has been made today. In general it feels like everyone had a collective off-day. The devs are looking for the last piece of the puzzle. They are looking for the encryption (xxhash seed) that Niantic is using. It"s buried somewhere...
   
7. Maybe friday is just the day everyone is busy, because last friday, when the API broke, there were little people working on it. Hopefully the devs can finish the job over the next couple of days, like the FPM-dev predicted.

複製代碼

其內容表示

10月14日，GMT +0，02:00 - 開發者正在取得進展。他們大多是用我想的混淆。
我猶豫甚至更新，因為情況沒有太大的不同，昨天，已經取得的進展是預期。安全網是惱人，但不超過。調試所需的專業水平略有下降，這意味著更多的人可以幫助。 （這仍然意味著你可能不能幫助，但2年的經驗，而不是一個必要的5+是好的。）
作為一個填充者，我將談談一下混淆的工作原理，這一部分與第一個API沒有什麼不同，加密是在客戶端內部，但真正的交易是找出加密的哪些部分實際上使用了Niantic的策略在加密“文件夾”中放置了很多偽造的東西，然後開發者需要過濾掉什麼是相關的，什麼不是。
現在很多這些假的函數仍然被調用，但是它們的返回值從未使用過。你需要密切注意找出必要的部件。調用所有這些假的功能也使你的手機慢路。
現在在第一個API休息期間，弄清楚什麼是假的很容易，因為他們會跳過假。然而，如果他們試圖跳過任何函數現在（這需要改變代碼），反調試措施開始起作用，他們最終在一個無限循環。這就是為什麼調試是一個更多的繁瑣。
10月15日，GMT +0，01:00 - 今天似乎沒有什麼進展。一般來說，感覺像每個人都有一個集體休息日。開發者正在尋找拼圖的最後一塊。他們正在尋找Niantic正在使用的加密（xxhash種子）。它埋在某處...
也許星期五隻是每一個人都忙的日子，因為上星期五，當API打破了，有一些人在工作。希望開發人員可以在接下來的幾天完成這項工作，就像FPM-dev預測的那樣。


大家自個看明白吧!!