Appcelerator Blog

The Leading Resource for All Things Mobile

Announcing our iOS 8 Support with Appcelerator SDK/Studio 3.4.0 Release

3 Flares 3 Flares ×

Update: we’ve now released our official Studio/SDK 3.4.0 GA providing support for iOS 8 and iPhone 6. You can read more about this release in this blog post.

iOS 8 is here! As Apple releases iOS 8 we release our support for it in our RC version of Appcelerator SDK/Studio 3.4.0. You now can take advantage of such features as Touch ID and Local Interactive Notifications with categories.

Once we get our hands on the iPhone 6 and iPhone 6 Plus, we will test against those new devices and certify the build for General Availability as quickly as possible.

If you have not already ported your iOS apps using our 3.4.0 betas, now is the time to get your apps ready. Make sure that your customers will not be adversely impacted as they upgrade their devices to iOS 8. (Please note that you will have to use XCode 6 and this requires OS X Mavericks or Yosemite.)

As always we want to thank our active development community and our enterprise customers. The feedback you provided on our iOS 8 beta releases has been remarkable. This is the only way that we are able to provide our high quality releases the same day as the mobile operating system releases. Thank you very much and please keep the feedback coming!

Getting Access to SDK/Studio 3.4.0

To get access to both Studio and SDK 3.4.0 please follow these 3 steps

1. Upgrade Studio

  • Community Members: Click here to get access to Titanium Studio 3.4.0 RC.
  • Appcelerator Platform Customers: Click here to download Appcelerator Studio 3.4.0 RC.

2. Install Appcelerator/Titanium SDK

ti sdk install --branch 3_4_X -d

3. Install NPM Packages

Note: You may need to use ‘sudo’ before these terminal commands on OSX and Linux

npm install -g alloy@1.5.0-rc3
npm install -g titanium@3.4.0-rc4

For more information about our release, please read our release notes.

3 Flares Twitter 0 Facebook 0 Google+ 0 LinkedIn 3 Email -- 3 Flares ×

17 Comments

  1. Donovan

    While I’m glad to see this new SDK version there is still an annoying issue thats been happening to me since the launch of SDK 3.3.0.

    My app will work fine and just crash after some use. I can not figure out what is causing it to do this but its been happening since 3.3.0 it did not happen with 3.2.3. This is the error I get when it crashes.

    [ERROR] : 2014-09-18 00:53:44.669 Speedtest X[21696:1665754] *** Terminating app due to uncaught exception ‘NSInvalidArgumentException’, reason: ‘*** NSAllocateMemoryPages(43459736) failed’
    [ERROR] : *** First throw call stack:
    [ERROR] : (
    [ERROR] : 0 CoreFoundation 0x04e9ddf6 __exceptionPreprocess + 182
    [ERROR] : 1 libobjc.A.dylib 0x04a60a97 objc_exception_throw + 44
    [ERROR] : 2 CoreFoundation 0x04e9dd1d +[NSException raise:format:] + 141
    [ERROR] : 3 Foundation 0x01f75cfc NSAllocateMemoryPages + 106
    [ERROR] : 4 Foundation 0x01e84323 _NSDataCreateVMDispatchData + 34
    [ERROR] : 5 Foundation 0x01e8251a -[_NSPlaceholderData initWithBytes:length:copy:deallocator:] + 252
    [ERROR] : 6 Foundation 0x01e8240d -[NSData(NSData) initWithBytes:length:copy:freeWhenDone:bytesAreVM:] + 92
    [ERROR] : 7 Foundation 0x01edefb3 -[NSData(NSData) copyWithZone:] + 144
    [ERROR] : 8 libobjc.A.dylib 0x04a76b45 -[NSObject copy] + 41
    [ERROR] : 9 Speedtest X 0x003038ef -[APSHTTPResponse responseData] + 48
    [ERROR] : 10 Speedtest X 0x003039d6 -[APSHTTPResponse responseLength] + 218
    [ERROR] : 11 Speedtest X 0x00306540 -[APSHTTPRequest connection:didReceiveData:] + 327
    [ERROR] : 12 CFNetwork 0x039704a1 ___ZL30_NSURLConnectionDidReceiveDataP16_CFURLConnectionPK8__CFDatalPKv_block_invoke + 51
    [ERROR] : 13 CFNetwork 0x03987f99 __65-[NSURLConnectionInternal _withConnectionAndDelegate:onlyActive:]_block_invoke + 83
    [ERROR] : 14 Foundation 0x01f71365 __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 12
    [ERROR] : 15 Foundation 0x01e97e45 -[NSBlockOperation main] + 99
    [ERROR] : 16 Foundation 0x01e77247 -[__NSOperationInternal _start:] + 700
    [ERROR] : 17 Foundation 0x01e76f79 -[NSOperation start] + 83
    [ERROR] : 18 Foundation 0x01e76dc3 __NSOQSchedule_f + 237
    [ERROR] : 19 libdispatch.dylib 0x0581d03f _dispatch_client_callout + 14
    [ERROR] : 20 libdispatch.dylib 0x05805d86 _dispatch_queue_drain + 690
    [ERROR] : 21 libdispatch.dylib 0x05805976 _dispatch_queue_invoke + 197
    [ERROR] : 22 libdispatch.dylib 0x05807a07 _dispatch_root_queue_drain + 374
    [ERROR] : 23 libdispatch.dylib 0x0580899d _dispatch_worker_thread3 + 108
    [ERROR] : 24 libsystem_pthread.dylib 0x05b72296 _pthread_wqthread + 724
    [ERROR] : 25 libsystem_pthread.dylib 0x05b6feea start_wqthread + 30
    [ERROR] : )
    [ERROR] : libc++abi.dylib: terminating with uncaught exception of type NSException

    • This needs to be created as a jira ticket (http://jira.appcelerator.org/) or request help in the Q&A (http://developer.appcelerator.com/questions/newest).

    • Ingo Muschenetz

      It is difficult to tell from just a stack trace. If you search in JIRA, this stack trace appears a few times for different reasons. I would suggest reviewing existing tickets to see if one matches, or file a new one with a test case if none do.

  2. Jason Miller

    3.4.X

    Can anyone provide guidance on location services for iOS 8?

    I’ve included:
    (within ios/plist/dict)

    NSLocationAlwaysUsageDescription
    NSlocation Always Usage Description Here

    …into my tiapp.xml

    Should I ask for permissions in alloy.js as a global?

  3. Fábio

    I updated to skstudio 3.4 but now I only have the iPhone 6 and 6+ simulator.
    Check the print screen – http://oi58.tinypic.com/2iqee8p.jpg

    Any solution?

  4. Donovan

    I have found a bug with this release. If you upload a file and that file upload is aborted the file will not be cleared from ram it just stays there eating large amounts of the device ram and will cause the app to crash if more uploads are aborted.

    This did not happen in SDK 3.2.3.

  5. Kosso

    Following these instructions do not seem to have worked for me.

    When I now open Titanium Studio, an error window pops up saying :

    “An internal error occurred during: “Update iOS info”.
    org.json.simple.JSONObject cannot be cast to org.json.simple.JSONArray”

    When I go to a project and open “Run Configurations” I only see “iOS SDK: 7.0” in the drop down. But I see Simulator Version : 8.0 there.
    In Device Profile I do not see the new iPhone 6 (Plus) and resizable devices.

    But I can open XCode 6 and build a test iOS8 app. Obejctive-C or Swift and all that is fine.

    So what gives? Any hints? This process never run smoothly for me, every time we get a big update. :(

    I have installed :
    Titanium Studio, build: 3.4.0.201408011456
    XCode: 6.0.1
    node : v0.10.32
    npm : v1.4.28
    Titanium CLI : v3.4.0-rc4
    Titanium SDK : 3.4.0.v20140918202513

    and the versions of allow and titanium installed from the commands above (run via sudo).

    When I run ‘titanium setup’ then do a ‘c’heck. It says I have an older Titanium SDK (3.3.0.GA) selected, even though I went into the Titanium SDK setup and made sure the latest 3.4.0.v20140918202513 build was ‘active’.

  6. Tom Nguyen

    anyone else getting this build error?

    DeveloperPortal: Using pre-existing current store at URL (file:///Users/tomnguyen/Library/Developer/Xcode/DeveloperPortal%206.0.1.db)

    Just updated everything. I see the Simulator in Run options. Cleaned the build Remove configurations.
    Just cannot build. Cant figure it out.

    Studio 3.4
    SDK 3.4
    Xcode 6.0.1

    • Paulo

      I am getting major issues with the new SDK and Studio. I am getting the following:

      [ERROR] : Failed to load command “build”
      [ERROR] : TypeError: Cannot call method ‘map’ of undefined
      at Object. (/usr/local/lib/node_modules/titanium/node_modules/node-appc/lib/exception.js:33:27)
      at Module._compile (module.js:456:26)
      at Module._extensions..js (module.js:474:10)
      at Module.load (module.js:356:32)
      at Module._load (module.js:312:12)
      at Module.require (module.js:364:17)
      at require (module.js:380:17)
      at Object. (/usr/local/lib/node_modules/titanium/node_modules/node-appc/lib/auth.js:25:18)
      at Module._compile (module.js:456:26)
      at Module._extensions..js (module.js:474:10)
      ———————————————
      at Object.run (/usr/local/lib/node_modules/titanium/node_modules/node-appc/lib/subprocess.js:59:8)
      at find (/usr/local/lib/node_modules/titanium/node_modules/node-appc/lib/subprocess.js:96:14)
      at q.process (/usr/local/lib/node_modules/titanium/node_modules/async/lib/async.js:731:21)
      at processImmediate (timers.js:330:15)

      I have no idea how to solve this. I can’t run the simulator or anything without seeing the above error.

      Any help is highly appreciated.

      Thanks

  7. Matt

    Paulo, I had this problem until I realized that I was installing SDKs with ‘sudo’, which then does not allow the normal build process to see the necessary files in the SDK. Try re-running ti sdk install –branch 3_4_X -d without sudo and hopefully that works for you.

  8. Ace McLoud

    Hmm, running

    ti sdk install –branch 3_4_X -d

    I get

    [ERROR] No branches found!

  9. Just upgrade the studio and I cannot run the no more.
    It say the application can’t be opened

Comments are closed.

Sign up for updates!

Become a mobile leader. Take the first step to scale mobile innovation throughout your enterprise.
Get in touch
computer and tablet showing Appcelerator software
Start free, grow from there.
3 Flares Twitter 0 Facebook 0 Google+ 0 LinkedIn 3 Email -- 3 Flares ×