rpplusplus / pokemonhook Goto Github PK

View Code? Open in Web Editor NEW

517.0 517.0 154.0 314.29 MB

Objective-C++ 46.72% Ruby 53.28%

pokemonhook's People

Contributors

Stargazers

Watchers

Forkers

hewigovens wangpengfei1986 webfrogs obaby cybercarrot impcoder czwen ioflong glzjin kanracyan capegf qitaos sunnyzl devtofu boolron xiaohongjun0509 dukecp raykle musketeerteam hysonchou elvis-zhou beasonshu blinkmo lisasu-g abelsu131 ziiip mtxs007 lngi waitat crazypoo nikolxm zetasq guangxianduan qunwang6 wbcyclist y2kbug bigmonstercai frankiezzz yugeorge jackieyk 0tk0 rojshanliang m1a0yu3 voyagecn xilin imaynt morgan-mmy nnn-li inyko pandarawen isaced austgl soocue blank0ken ore4o iceblacktea jessexu octree doloreng weiios billhai chinwy22 kai60 kittenyang parisilabs ekkog liuzheng w1ng imchao9 mychildhoods ryankung leejingbin mail2chensh promiseteam zxm9988 hello--world darkness0ut kelvinjin smiledqyang yuiosxiao royalwang oxidosnel ghold kerasking page-xia linghuguo bottotl bh-cheng chenhengjie123 ziggear lszzy cherrydemo guiminchu strongmancoder wu736139669 wenhhh jakobas creolophus blockchainb iliuyi

pokemonhook's Issues

xcode提示this application does not support this device's cpu type

Hi,

我按照你的步骤，先签了lib，然后压缩，然后用fastlane签ipa，用xcode安装时提示this application does not support this device's cpu type，请问怎么解决。我是iphone 5

请教一个问题：一个二进制文件只能注入一个dylib吗？

通过yolo注入dylib后，只注入一个好用，注入第二个就不好用了，测试dylib没问题。或者说我方式不对？

不明白.app是哪里来的

感谢提供这么好的资源，但是目前的签名的过程中遇到问题。
自签名过程中有一步是"把 .app 放到 Payload 文件夹，压缩成 .ipa"，不知道这个.app是怎么来的，目录中没有这个文件，Xcode工程又是用于生成dylib文件的，求解惑。

请问虾神

我自己制作了一个dylib的包，怎么弄进去打包呢。
执行 yolo pokemango libXXXX.dylib 如果叫做 LocationFaker.dylib 可以跳过这个看不懂。

请问能否给我发一个可以直接安装的ipa？

您好，我非常喜欢口袋妖怪这个游戏，但是我不会iOS开发，也没有签名用的证书，我非常想安装您这个版本来体验一下pokemonGO这个游戏，不知道能否给我发一个可以直接安装的ipa？要是可以那真是感激不尽

虾大，你说的zip包里没有libLocationFaker啊

如题，这个git库里我只看见一个zip包，里面只有一个未签名的.app文件，其他目录我翻遍了也木有找到你说的libLocationFaker这个文件...是不是忘了传上来了？

签名之后提示错误

Dyld Error Message:
Dyld Message: Library not loaded: @executable_path/libLocationFaker.dylib

感谢~ & 小小的解释

感谢作者大大~
周五下载了未签名的代码包，和小伙伴研究了一晚上，搞定了签名和安装。
今天上来看到作者贴心地又更新了签名步骤~
解释下，好多人都不会大概是大家都是奔着游戏来的，本身可能都没接触过ios开发。
最后还是非常感谢，让我们玩到了这个游戏，很激动很开心(づ￣ 3￣)づ

Why only 32bit CPU？

32bit CPU 是为了兼容性的考虑吗？还是说有其他限制？
从性能上考量，假如我要跑在 64bit 的机器上，是不是从 64bit 的越狱机器上 Clutch 更合适？
BTW，我尝试在自己的 iPad Air 上砸壳后成功安装在 6s 上.

libLocationFaker 在哪呢

您好，您給的 ZIP 包中僅含 /Payload/pokemongo.app，沒看見 libLocationFaker 的 dylib
還是需要我們自己編譯呢？ :P ...

能不能那个半成品修改一下，经纬度加个零点几的随机数

设备上次因为白苹果，不得不升到正式版。没法去编译破解包了。求大神在那个定位到联合广场的基础上加一个零点几的随机经纬度，这样不至于每次打开应用都重生到一个点。只要能有个未签名的包就行。

7月21日更新

求助一下，今天发现突然更新了，手头也没有能越狱的机子，能麻烦作者更新一下store最新版吗

iphone 5 "This application does not support this device's CPU type."

谢谢虾神提供这么好的跨区源码

我在iphone 6s上顺利执行

想在自己的旧机器 iphone 5也安装下，没想到报错

"This application does not support this device's CPU type."

原版的Pokemon Go支持iPhone 5 的CPU，是不是我哪里设定错了？

在此请教大家，谢谢

Signer did not match any installed provisioning profile

Jul 19 10:09:19 Timde-iPhone CLTM[21] : CLTM: _subscription 0x0, _subscribedChannels 0x0
Jul 19 10:09:22 Timde-iPhone installd[15102] : 0x1005b4000 -[MICodeSigningVerifier performValidationWithError:]: 188: Failed to verify code signature of : 0xe8008015 (Signer did not match any installed provisioning profile)
Jul 19 10:09:22 Timde-iPhone installd[15102] : 0x1005b4000 -[MIInstaller performInstallationWithError:]: Verification stage failed
Jul 19 10:09:22 Timde-iPhone streaming_zip_conduit[15005] : 0x100594000 __MobileInstallationInstallForLaunchServices_block_invoke240: Returned error Error Domain=MIInstallerErrorDomain Code=13 "Failed to verify code signature of : 0xe8008015 (Signer did not match any installed provisioning profile)" UserInfo=0x13ed25590 {LibMISErrorNumber=-402620395, LegacyErrorString=ApplicationVerificationFailed, SourceFileLine=188, FunctionName=-[MICodeSigningVerifier performValidationWithError:], NSLocalizedDescription=Failed to verify code signature of : 0xe8008015 (Signer did not match any installed provisioning profile)}

一直没搞懂这个Signer did not match any installed provisioning profile 具体哪个地方有什么问题，有谁碰到过吗

请问一下之前app中就已经有保护一个dylib了怎办

一开始的包就有包含了libLocationFaker这个了，如果我需要用自己制作的dylib要怎么删除这个呢

重啓後定位會回到初始點

看起來是在 +(void)load 的時候沒有正確載入儲存的 fake_x 跟 fake_y

我測試是在 - (CLLocationCoordinate2D) coordinate_ 再次檢查是否有儲存的 fake_x 跟 fake_y ，就能解決。

运行时不定时的crash

看console log里输出是

20:20:02 pokemongo➜I: Rescheduling request for retry: 24
20:20:03 pokemongo➜I: [5] https://pgorelease.nianticlabs.com/plfe/45/rpc
20:20:03 pokemongo➜I: Timeout, will retry: 23
20:20:03 pokemongo➜E: All attempts exhausted for request
20:20:03 pokemongo➜E: FAILED RPC(23, 11)
20:20:03 pokemongo➜I: [5] https://pgorelease.nianticlabs.com/plfe/45/rpc
20:20:03 pokemongo➜I: Timeout, will retry: 25
20:20:03 pokemongo➜E: All attempts exhausted for request
20:20:03 pokemongo➜E: FAILED RPC(25, 11)
20:20:03 pokemongo➜W: Error fetching request  cancelled
20:20:04 diagnosticd➜unable to find offset 0x839497ec in shared cache for arch 'arm64'
20:20:04 diagnosticd➜unable to find offset 0x83b49da8 in shared cache for arch 'arm64'
20:20:04 diagnosticd➜Invalid offset 2209652136 into shared cache for arch 'arm64'
20:20:04 diagnosticd➜unable to find offset 0x83b49da8 in shared cache for arch 'arm64'
20:20:04 diagnosticd➜Invalid offset 2209652136 into shared cache for arch 'arm64'
20:20:04 diagnosticd➜unable to find offset 0x83b49da8 in shared cache for arch 'arm64'
20:20:04 diagnosticd➜Invalid offset 2209652136 into shared cache for arch 'arm64'
20:20:04 diagnosticd➜unable to find offset 0x83b49da8 in shared cache for arch 'arm64'
20:20:04 diagnosticd➜Invalid offset 2209652136 into shared cache for arch 'arm64'
20:20:04 diagnosticd➜unable to find offset 0x83b49da8 in shared cache for arch 'arm64'
20:20:04 diagnosticd➜Invalid offset 2209652136 into shared cache for arch 'arm64'
20:20:04 diagnosticd➜unable to find offset 0x83b49da8 in shared cache for arch 'arm64'
20:20:04 diagnosticd➜Invalid offset 2209652136 into shared cache for arch 'arm64'
20:20:04 diagnosticd➜unable to find offset 0x83b49da8 in shared cache for arch 'arm64'
20:20:04 diagnosticd➜Invalid offset 2209652136 into shared cache for arch 'arm64'
20:20:04 diagnosticd➜unable to find offset 0x83b49da8 in shared cache for arch 'arm64'
20:20:04 diagnosticd➜Invalid offset 2209652136 into shared cache for arch 'arm64'
20:20:04 diagnosticd➜unable to find offset 0x83b49da8 in shared cache for arch 'arm64'
20:20:04 diagnosticd➜Invalid offset 2209652136 into shared cache for arch 'arm64'
20:20:04 diagnosticd➜unable to find offset 0x83b49da8 in shared cache for arch 'arm64'
20:20:04 diagnosticd➜Invalid offset 2209652136 into shared cache for arch 'arm64'
20:20:04 diagnosticd➜unable to find offset 0x83b49da8 in shared cache for arch 'arm64'
20:20:04 diagnosticd➜Invalid offset 2209652136 into shared cache for arch 'arm64'
20:20:04 diagnosticd➜unable to find offset 0x83b49da8 in shared cache for arch 'arm64'
20:20:04 diagnosticd➜Invalid offset 2209652136 into shared cache for arch 'arm64'
20:20:04 diagnosticd➜unable to find offset 0x83b49da8 in shared cache for arch 'arm64'
20:20:04 diagnosticd➜Invalid offset 2209652136 into shared cache for arch 'arm64'
20:20:04 diagnosticd➜unable to find offset 0x83b49da8 in shared cache for arch 'arm64'
20:20:04 diagnosticd➜Invalid offset 2209652136 into shared cache for arch 'arm64'
20:20:04 diagnosticd➜unable to find offset 0x83b49da8 in shared cache for arch 'arm64'
20:20:04 diagnosticd➜Invalid offset 2209652136 into shared cache for arch 'arm64'
20:20:04 diagnosticd➜unable to find offset 0x83b49da8 in shared cache for arch 'arm64'
20:20:04 diagnosticd➜Invalid offset 2209652136 into shared cache for arch 'arm64'
20:20:04 diagnosticd➜unable to find offset 0x83b49da8 in shared cache for arch 'arm64'
20:20:04 diagnosticd➜Invalid offset 2209652136 into shared cache for arch 'arm64'
20:20:04 diagnosticd➜unable to find offset 0x83b49da8 in shared cache for arch 'arm64'
20:20:04 diagnosticd➜Invalid offset 2209652136 into shared cache for arch 'arm64'
20:20:04 diagnosticd➜unable to find offset 0x83b49da8 in shared cache for arch 'arm64'
20:20:04 diagnosticd➜Invalid offset 2209652136 into shared cache for arch 'arm64'
20:20:04 diagnosticd➜unable to find offset 0x83b49da8 in shared cache for arch 'arm64'
20:20:04 diagnosticd➜Invalid offset 2209652136 into shared cache for arch 'arm64'
20:20:04 ReportCrash➜platform_thread_get_unique_id matched 684405
20:20:04 ReportCrash➜Formulating report for corpse[2310] pokemongo
20:20:04 ReportCrash➜Saved type '109(109_pokemongo)' report (2 of max 25) at /var/mobile/Library/Logs/CrashReporter/pokemongo-2016-07-10-202004.ips

这个是应用自己的bug么？