Open peteclark3 opened 10 years ago
This also crashes the app for me
LaunchServices: invalidationHandler called
I can provide full crash report if required.
Using Titanium 3.2.2 / xcode 5 / iOS 8 here same issue. I narrowed it down to the Social.twitterAccountList() call. Weird issue because it still crashes the app even when removing all code from the twitterAccountList method (in ObjC).
Tried adding a new dummy method without code, calling that also crashes the app.
Service exited due to signal: Segmentation fault: 11
Sounds like a memory (de)allocation issue somewhere.
I'm using Titanium 3.4.0 Beta / xcode 6.0.1 / iOS 8 and also getting bothered by the same issue.
I hope someone specify the problem and fix it soon...
Hi, I worked on the module last night and find the solution as explained in pull request : https://github.com/viezel/TiSocial.Framework/pull/100
You can create your own module with the change, or repo authors will create a new version to fix the problem.
Best.
Apparently this is not related to just 3.4.x SDKs, I'm still using 3.2.2 for an app and the fix works there too. Thanks @alperdincer !
Same here 3.4 ios8 xcode 6 crashes
Anyone know how to build a version with the latest changes? I get these messages no matter what version of the SDK i change in the Titanium.xconfig
File "build.py", line 216, in
@amigoni I changed the TITANIUM_SDK path in the titanium.xcconfig file and then I was able to run ./build.py. More info here...
@harrythree Thanks for the tip, but no luck.
@amigoni Maybe try changing the TITANIUM_SDK_VERSION to something newer. Doesn't seem like it would compile if you don't have the Ti version it has set by default (which is pretty old. 2.1.4.GA).
Yeah. Did that already before your suggestion. I have 3.4.0.GA which is the latest that I have installed. Double checked that it exists.
These are the two lines I changed to get it to work in titanium.xcconfig.
And of course make sure you change directories in terminal to the tisocial.framework folder you got from here and run ./build.py
Oops the mark down parsed 2. and left out some stuff. Should be... TITANIUM_SDK = /Users/your_computer_name/Library/Application Support/Titanium/mobilesdk/osx/$(TITANIUM_SDK_VERSION)
Ok some progress but using this.
TITANIUM_SDK = /Library/Application Support/Titanium/mobilesdk/osx/$(TITANIUM_SDK_VERSION)
but now I get this.
In file included from /Users/Leonardo/Downloads/TiSocial.Framework-master 2/Classes/NappCustomActivity.m:9:
_/Users/Leonardo/Downloads/TiSocial.Framework-master 2/Classes/NappCustomActivity.h:8:9: _fatal error: 'TiModule.h' file not found
1 error generated.
* BUILD FAILED *
The following build commands failed:
CompileC build/social.build/Release-iphoneos/social.build/Objects-normal/armv7/DkNappSocialModule.o Classes/DkNappSocialModule.m normal armv7 objective-c com.apple.compilers.llvm.clang.1_0.compiler
CompileC build/social.build/Release-iphoneos/social.build/Objects-normal/armv7/NappCustomActivity.o Classes/NappCustomActivity.m normal armv7 objective-c com.apple.compilers.llvm.clang.1_0.compiler
(2 failures)
xcodebuild failed
Thanks for your patience.
Leo Amigoni
On Thu, Oct 2, 2014 at 9:28 AM, Harry Baldwin notifications@github.com wrote:
Oops the mark down parsed 2. and left out some stuff. Should be... TITANIUM_SDK = /Users/your_computer_name/Library/Application Support/Titanium/mobilesdk/osx/$(TITANIUM_SDK_VERSION)
— Reply to this email directly or view it on GitHub https://github.com/viezel/TiSocial.Framework/issues/95#issuecomment-57593186 .
That seems like it doesn't know where the SDK is located. Send me an email (harrythree@gmail.com) and I'll send over my build of the module in the morning.
Like @amigoni, I also have Ti installed in /Library/Application
Support/Titanium and I also get the #import "TiModule.h"
problem.
No issues with any of the other modules I use, and have updated to 3.4.0. Does anyone know the fix?
@amigoni Open up the social.xcodeproj and under Build Settings > User-Defined, update the TITANIUM_SDK_VERSION to 3.4.0.GA, it's at 3.1.1 currently.
Let me know if you need more info. Workaround currently for me was just to remove this code (from the sample code).. and it worked