Xcode 4.0 GM Seed Release Notes

Xcode 4.0 GM Seed Release Notes

Resolved Issues

Editing Nib Files

• Refactoring: Xcode refactors Cocoa bindings. 8423815

Source Control and Snapshots

• On a project with no snapshots, new snapshots appear in the projects organizer. 8774085

Performance Measurement and Analysis

• Xcode 4.0 Developer Preview 6 installs a set of kernel extension with a version number of 9999, which hinders their upgrade.
  Before installing Xcode 4.0 GM Seed, perform these actions:
  • In Terminal, execute these commands:

    sudo rm -rf /System/Library/Extensions/AppleProfileFamily.kext/Contents/PlugIns/AppleIntelPenrynProfile.kext

    sudo rm -rf /System/Library/Extensions/AppleProfileFamily.kext/Contents/PlugIns/AppleIntelNehalemProfile.kext

    sudo touch /System/Library/Extensions

  • Install Xcode.
  • Restart your computer. 8844127

Enhancements

Enhancements

General

• You can access the values of the build settings of the target being built through environment variables and launch arguments. When you create custom executables (by changing the value of the Executable setting in Run and Profile scheme actions), you can specify the target against which to expand the environment variables and launch arguments. 7546808

Editing Nib Files

• Xcode suggests key path completions in the bindings inspector as you type. To take advantage of this feature, specify the class of object being managed by your controller in the attributes inspector.
  Xcode uses the project’s symbol index to generate the key path completions. 8176168

Editing Source Code

• There’s an additional gesture to jump to a symbol definition in the source editor: holding down the Command key. When you hold down Command, Xcode represents the symbol under the pointer as a hyperlink; you can move the pointer between symbols until Xcode highlights the one you want to act on. You can then click the symbol to jump to its definition. Other modifies keys behave as expected. 8459719

Task Information and Alerts

• The activity viewer presents more detailed information about scheme-related tasks, such as building a product. 7982481

Xcode 4.0 Developer Preview 5 Release Notes

Xcode 4.0 Developer Preview 5 Release Notes

New Features

General

• The build action in the scheme dialog allows you to choose which targets should be built for each scheme action. 8025069
• Each scheme action specifies the build configuration to use when Xcode performs that action as part of a build. Setting up a scheme with scheme actions that use particular build configurations allows you to, for example, set up a scheme that runs the product with the Debug configuration but profiles it with the Release configuration. 8090845
• The Build and Archive command archives the products of the targets selected in the active scheme for archival, including their dSYM files. You submit your products to iTunes Connect using these archives. You can also use them to symbolicate crash logs. 7696041
• The post-action scripts of archive scheme actions have access to information about the just-built archive in their environment:
  • ARCHIVE_PATH: The path to the archive.
  • ARCHIVE_PRODUCTS_PATH: The installation location for the archived product.
  • ARCHIVE_DSYMS_PATH: The path to the product’s dSYM files. 8423449
• Xcode detects and enforces implicit build dependencies between targets when you build a scheme. You can turn this off per scheme in a scheme’s build action. 7879553
• When the active scheme is a unit-test scheme, clicking Run in the toolbar produces an unknown error dialog.
  To run unit tests, choose Product > Test. 8642393
• Fix-it is not supported in iOS application projects created using the new project dialog. The iOS project templates have the compiler set to LLVM-GCC, which does not support Fix-it.
  After creating an iOS project, set the compiler to LLVM 2.0. 8607314
  
  

Creating Facebook Reference Project

Creating Facebook Reference Project

Once you are done with registering your facebook application, you need to download facebook SDK and create a new reference project. This reference project will be used to compile your actual project.

1. Download facebook android SDK from git repositories.
(git clone git://github.com/facebook/facebook-android-sdk.git)

2. In your Eclipse goto File ⇒ Import ⇒ Existing Projects into Workspace and select the facebook project you downloaded from git repository.

Generating App Signature for Facebook Settings

Generating App Signature for Facebook Settings

To create facebook android native app you need to provide your Android application signature in facebook app settings. You can generate your application signature (keyhash) using keytool that comes with java. But to generate signature you need openssl installed on your pc. If you don’t have one download openssl from here and set it in your system environment path.

Open your command prompt (CMD) and run the following command to generate your keyhash. While generating hashkey it should ask you password. Give password as android. If it don’t ask for password your keystore path is incorrect.

keytool -exportcert -alias androiddebugkey -keystore "<path-to-users-directory>\.android\debug.keystore" | openssl sha1 -binary | openssl base64

check the following command how i generated hashkey on my pc.

keytool -exportcert -alias androiddebugkey -keystore "C:\Users\Ravi\.android\debug.keystore" | openssl sha1 -binary | openssl base64

Registering your Facebook Application

After generating your app signature successfully, register your facebook application by going to create new facebook application and fill out all the information needed. And select Native Android App and give your hashkey there which you generated previously using keytool.

and note down your facebook App ID

Android Facebook Connect Tutorial

This tutorial is about integrating facebook into your android application. I am going to explain various steps like generating your application signature, registering facebook application, downloading facebook sdk and other steps. Here is an officialdocumentation of facebook integration.

Debugging OpenGL Frames

When debugging an OpenGL frame, the debug navigator shows the OpenGL call trace that generated the captured frame. The call trace includes the stack frame for each OpenGL call.

Note: The debug navigator shows content only after Xcode has captured an OpenGL frame.

The debug navigator contains the OpenGL call trace and a filter bar.

With the filter bar (the bottom box on the left in the screenshot) you specify the OpenGL calls and stack frames you want to see.

• Call filter: Shows only markers and OpenGL draw calls.
• Call stack slider: Shows stack frames, from only the most relevant to all of them.