how can i fix it wrong archtecture about ipapatch HOT 13 CLOSED

Would you try to disable bitcode for IPAPatch and try again?
(Or you can git pull and try again, I just disabled it with 5cf7be6)

Please let me know if it solve your problem.

from ipapatch.

i try, but unfortunately no use

from ipapatch.

the app i downloaded is from PP助手, a chinese app store , the app's architecture is armv7 my phone is arm64

from ipapatch.

maybe i should download the app from app store, and clutch the app by myself?

from ipapatch.

@UESTC-LXY I think armv7 is ok, it's backward-compatible.

Would you try set Build Active Architecture Only to NO for the IPAPatch target?

from ipapatch.

from ipapatch.

the code is like that

from ipapatch.

by the way, the program is based on your youtube demo program

from ipapatch.

Is it still report mach-o, but wrong architecture ?
If is, please try modify Valid Architectures of IPAPatch target, set it to ONLY armv7 (delete others).

And I think you can't change method's return value by this way, please check aspects README:
https://github.com/steipete/Aspects#using-aspects-with-non-void-return-types

from ipapatch.

oops, mach-o problem fixed , but

2017-03-24 11:45:05.482 Busuu-ja[17786:4107946] GTLDriveChannel (api#channel) registration conflicts with GTLCalendarChannel
2017-03-24 11:45:05.484 Busuu-ja[17786:4107946] GTLPlusDomainsAcl (plus#acl) registration conflicts with GTLPlusAcl
2017-03-24 11:45:05.484 Busuu-ja[17786:4107946] GTLPlusDomainsActivity (plus#activity) registration conflicts with GTLPlusActivity
2017-03-24 11:45:05.484 Busuu-ja[17786:4107946] GTLPlusDomainsActivityFeed (plus#activityFeed) registration conflicts with GTLPlusActivityFeed
2017-03-24 11:45:05.485 Busuu-ja[17786:4107946] GTLPlusDomainsComment (plus#comment) registration conflicts with GTLPlusComment
2017-03-24 11:45:05.485 Busuu-ja[17786:4107946] GTLPlusDomainsCommentFeed (plus#commentFeed) registration conflicts with GTLPlusCommentFeed
2017-03-24 11:45:05.485 Busuu-ja[17786:4107946] GTLPlusPeopleFeed (plus#peopleFeed) registration conflicts with GTLPlusDomainsPeopleFeed
2017-03-24 11:45:05.485 Busuu-ja[17786:4107946] GTLPlusPerson (plus#person) registration conflicts with GTLPlusDomainsPerson
2017-03-24 11:45:05.486 Busuu-ja[17786:4107946] GTLPlusPlace (plus#place) registration conflicts with GTLPlusDomainsPlace
2017-03-24 11:45:05.488 Busuu-ja[17786:4107946] GTLStorageChannel (api#channel) registration conflicts with GTLDriveChannel
2017-03-24 11:45:05.656578+0800 Busuu-ja[17786:4107946] *** Assertion failure in +[BSUSplitApp splitAppType], /Users/lukakiarelli/Desktop/busuuIosApp/Busuu/Source/Model/Utility Classes/BSUSplitApp.m:81
2017-03-24 11:45:05.657 Busuu-ja[17786:4107946] WARNING: GoogleAnalytics 3.09 void GAIUncaughtExceptionHandler(NSException *) (GAIUncaughtExceptionHandler.m:49): Uncaught exception: The bundle identified should always be identified
2017-03-24 11:45:05.658607+0800 Busuu-ja[17786:4108010] [MC] System group container for systemgroup.com.apple.configurationprofiles path is /private/var/containers/Shared/SystemGroup/systemgroup.com.apple.configurationprofiles
2017-03-24 11:45:05.659038+0800 Busuu-ja[17786:4108010] [MC] Reading from public effective user settings.
2017-03-24 11:45:05.687 Busuu-ja[17786:4108008] [Adjust]d: Package handler read 0 packages
2017-03-24 11:45:05.687 Busuu-ja[17786:4108010] [Adjust]d: Read activity state: ec:0 sc:1 ssc:1 sl:0.0 ts:0.0 la:1490327003.2 uuid:73505a2e-bbe2-4eee-895f-c6d291f9664a
2017-03-24 11:45:05.718 Busuu-ja[17786:4108010] [Adjust]d: Wrote activity state: ec:0 sc:1 ssc:2 sl:102.5 ts:0.0 la:1490327105.7
2017-03-24 11:45:05.718 Busuu-ja[17786:4108010] [Adjust]i: Processed Subsession 2 of Session 1
2017-03-24 11:45:05.727686+0800 Busuu-ja[17786:4107946] invalid mode 'kCFRunLoopCommonModes' provided to CFRunLoopRunSpecific - break on _CFRunLoopError_RunCalledWithInvalidMode to debug. This message will only appear once per execution.
2017-03-24 11:45:10.680748+0800 Busuu-ja[17786:4107946] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'The bundle identified should always be identified'
*** First throw call stack:
(0x1c66baed 0x1b8f3067 0x1c66b9c9 0x1cf614dd 0x199f89 0x1da247 0xdd6fd 0x21905b7d 0x21b06c9b 0x21b0be6d 0x21b1ea9d 0x21b095ab 0x1df4cc13 0x1df4cacd 0x1df4cdb7 0x1c627f8d 0x1c627ab5 0x1c625f01 0x1c57909f 0x1c578ec1 0x218ff3f5 0x218fa023 0xcc2b1 0x1bd664eb)
libc++abi.dylib: terminating with uncaught exception of type NSException

from ipapatch.

@UESTC-LXY Is the wrong architecture problem fixed by setting Valid Architectures?

*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'The bundle identified should always be identified'

Seems this app check the bundle identifier on launch, which modified by IPAPatch. you can use class-dump to find out if it's implemented in separated method, and patch it. Or just hook -[NSBundle bundleIdentifier] and return the original bundle identifier.

Good luck! :)

from ipapatch.

Thank you very much! wrong architecture settled by i reclone your master and set Valid Architectures

from ipapatch.

@UESTC-LXY OK, thanks for the info.

I will close this issue now. I think the bundle identifier checking can be bypass easily, just need some experiment. If you have any further questions, please create another issue.

from ipapatch.