Then try this:

Project Build Settings:

Architectures: Standard (armv6 armv7)
Base SDK: Latest iOS Build Active
Architectures Only: Checked Valid
Architectures: armv6 armv7

Make sure you delete an sub settings in the Architecture build setting.

Target Build Settings:

Same at project settings.

Clean all targets and try building the project again

MFMessageComposeViewController *controller = [[[MFMessageComposeViewController alloc] init] autorelease];
if([MFMessageComposeViewController canSendText])
{
controller.body = @"A test message from http://www.macoscoders.com";
controller.recipients = [NSArray arrayWithObjects:@"9880182343",nil];
controller.messageComposeDelegate = self;
[self presentModalViewController:controller animated:YES];
}

The MFMessageComposeViewController invoking class can implement the below delegate method to know the result of the SMS sending operation.

- (void)messageComposeViewController:(MFMessageComposeViewController *)controller didFinishWithResult:(MessageComposeResult)result

You can download sample XCode project source here

We can overcome this issue by editing FBDialog.m in the FBConnect. Add the below code as the first line in FBDialog.m’s webViewDidFinishLoad : methods

[_webView stringByEvaluatingJavaScriptFromString:@"document.getElementById('cancel').onclick = function onclick(event) { window.location.href = 'fbconnect:cancel'; }"];

This should fix the issue and dialogDidCancel should get called correctly..!

FBStreamDialog* dialog = [[[FBStreamDialog alloc] init] autorelease];
dialog.delegate = self;
dialog.userMessagePrompt = "Image Upload Sample";
dialog.attachment = [NSString stringWithFormat:@"{\"name\":\"Anish\","
"\"href\":\"http://www.macoscoders.com/\",\"description\":\"This is an example to upload image to FB\","
"\"media\":[{\"type\":\"image\","
"\"src\":\"http://www.macoscoders.com/images/anish.jpg\","
"\"href\":\"http://www.macoscoders.com/\"}],"
"\"properties\":{\"another link\":{\"text\":\"Home page\",\"href\":\"http://www.macoscoders.com/\"}}}"]];
[dialog show];

Make sure you have implemented the correct delegate methods for FBConnect to know the status of posting to wall
Cheers..!

[UIApplication sharedApplication].applicationIconBadgeNumber = 5;

Flash CS5: Native iPhone Application Development

The new support for iPhone applications in the Flash Platform tooling will not allow iPhone users to browse web content built with Flash technology on iPhone, but it may allow developers to repackage existing web content as applications for iPhone if they choose to do so.Flash Player uses a just-in-time compiler and virtual machine within a browser plug-in to play back content on websites. Those technologies are not allowed on the iPhone at this time, so a Flash Player for iPhone is not being made available today. Flash Professional CS5 will enable developers to build applications for iPhone that are installed as native applications. Users will be able to access the apps after downloading them from Apple’s App Store and installing them on iPhone or iPod touch. Developers can deliver applications built with Flash Platform tooling just like any other iPhone application. This will require the developer to be a member of the iPhone Developer Program and follow the program guidelines. iPhone applications built with Flash Platform tools are compiled into standard, native iPhone executables, just like any other iPhone applicatio. Applications can be built targeting iPhone OS 3.0 and later.

Update: Apple has bowled out Adobe’s effort to get iPhone application development on Flash platform with introduction of new clause in its iPhone SDK 4.0 license agreement which makes developing iPhone application using tools other than from Apple as illegal. Check more details about whats new in iPhone SDK 4.0 and its implications at http://www.macoscoders.com/2010/04/09/new-features-in-iphone-os-4-0/

Xcode: Loading Stack Frames

Recently I encountered an new error for the first time in XCode. When my iPhone application under development crashed, instead of showing me the stack trace of where the application crashed, it threw an error “Loading Stack Frames” and was struck there indefinitely.  After researching about this for a while, I came to know my application crashed because of a stack overflow due to a non-terminating recursion in your code, and gdb is now trying to load all the stack frames on the stack . Usually, the stack of a application doesn’t get deeper than 50 frames or so (and that’s already a quite deeply nested stack). My application stack had run into 104708 frames which was quite too high.I finally figured out that the crash was due to an race condition.

The new SDK 3.1.2, which now includes Xcode 3.2.1, is available in versions that are compatible with Leopard and Snow Leopard for iPhone and iPod Touch developers.

The update contains general bug fixes for the SDK and Xcode. Dashcode is reported to now support the creation of Web applications that are optimized for Safari on the iPhone, PC, and Mac.

If you’ve used this new update, please tell us about your experiences with it in the comments.

iPhone OS streams movies and audio using HTTP over EDGE, 3G, and Wi-Fi networks. iPhone OS uses a native application to play back video even when video is embedded in your webpages. Video automatically expands to the size of the screen and rotates when the user changes orientation. The controls automatically hide when they are not in use and appear when the user taps the screen. This is the experience the user expects when viewing all video on iPhone OS.

Safari on iPhone OS supports a variety of rich media, including QuickTime movies. Safari on iPhone OS does not support Flash so don’t bring up JavaScript alerts that ask users to download Flash. Also, don’t use JavaScript movie controls to play back video since iPhone OS supplies its own controls.

Safari on the desktop supports the same audio and video formats as Safari on iPhone OS. However, if you use the audio and video HTML elements on the desktop, you can customize the play back controls. See Safari DOM Extensions Reference for more details on the HTMLMediaElement class.

Follow these guidelines to deliver the best web audio and video experience in Safari on any platform:

• Follow current best practices for embedding movies in webpages as described in “Sizing Movies Appropriately,” “Don’t Let the Bit Rate Stall Your Movie,” and “Using Supported Movie Standards.”
• Use QuickTime Pro to encode H.264/AAC at appropriate sizes and bit rates for EDGE, 3G, and Wi-Fi networks, as described in “Encoding Video for Wi-Fi, 3G, and EDGE.”
• Use reference movies so that iPhone OS automatically streams the best version of your content for the current network connection, as described in “Creating a Reference Movie.”
• Use poster JPEGs (not poster frames in a movie) to display a preview of your embedded movie in webpages, as described in “Creating a Poster Image for Movies.”
• Make sure the HTTP servers hosting your media files support byte-range requests, as described in “Configuring Your Server.”
• If your site has a custom media player, also provide direct links to the media files. iPhone OS users can follow these links to play those files directly.

Sizing Movies Appropriately

In landscape orientation on iPhone OS, the screen is 480 x 320 pixels. Users can easily switch the view mode between scaled-to-fit (letterboxed) and full-screen (centered and cropped). You should use a size that preserves the aspect ratio of your content and fits within a 480 x 360 rectangle. 480 x 360 is a good choice for 4:3 aspect ratio content and 480 x 270 is a good choice for widescreen content as it keeps the video sharp in full-screen view mode. You can also use 640 x 360 or anamorphic 640 x 480 with pixel aspect ratio tagging for widescreen content.

Don’t Let the Bit Rate Stall Your Movie

When viewing media over the network, the bit rate makes a crucial difference to the playback experience. If the network cannot keep up with the media bit rate, playback stalls. Encode your media for iPhone OS as described in “Encoding Video for Wi-Fi, 3G, and EDGE” and use a reference movie as described in “Creating a Reference Movie.”

Using Supported Movie Standards

The following compression standards are supported:

• H.264 Baseline Profile Level 3.0 video, up to 640 x 480 at 30 fps. Note that B frames are not supported in the Baseline profile.
• MPEG-4 Part 2 video (Simple Profile)
• AAC-LC audio, up to 48 kHz

Movie files with the extensions .mov, .mp4, .m4v, and .3gp are supported.

Any movies or audio files that can play on iPod play correctly on iPhone.

If you export your movies using QuickTime Pro 7.2, as described in “Encoding Video for Wi-Fi, 3G, and EDGE,” then you can be sure that they are optimized to play on iPhone OS.

Encoding Video for Wi-Fi, 3G, and EDGE

Because users may be connected to the Internet via wired or wireless technology, using either Wi-Fi, 3G, or EDGE on iPhone OS, you need to provide alternate media for these different connection speeds. You can use QuickTime Pro, the QuickTime API, or any Apple applications that provide iPhone OS exporters to encode your video for Wi-Fi, 3G, and EDGE. This section contains specific instructions for exporting video using QuickTime Pro.

Follow these steps to export video using QuickTime Pro 7.2.1 and later:

1. Open your movie using QuickTime Player Pro.
2. Choose File > Export for Web.A dialog appears.
3. Enter the file name prefix, location of your export, and set of versions to export as shown in Figure 8-1.
   Figure 8-1 Export movie panel

   

4. Click Export.QuickTime Player Pro saves these versions of your QuickTime movie, along with a reference movie, poster image, and ReadMe.html file to the specified location. See the ReadMe.html file for instructions on embedding the generated movie in your webpage, including sample HTML.

Creating a Reference Movie

A reference movie contains a list of movie URLs, each of which has a list of tests, as show in Figure 8-2. When opening the reference movie, a playback device or computer chooses one of the movie URLs by finding the last one that passes all its tests. Tests can check the capabilities of the device or computer and the speed of the network connection.

If you use QuickTime Pro 7.2.1 or later to export your movies for iPhone OS, as described in “Encoding Video for Wi-Fi, 3G, and EDGE,” then you already have a reference movie. Otherwise, you can use the MakeRefMovie tool to create reference movies. You can download the tool from:

• http://developer.apple.com/quicktime/quicktimeintro/tools

Also, refer to the MakeiPhoneRefMovie sample for a command-line tool that creates reference movies.

For more details on reference movies and instructions on how to set them up see “Applications and Examples” in HTML Scripting Guide for QuickTime.

Creating a Poster Image for Movies

The video is not decoded until the user enters movie playback mode. Consequently, when displaying a webpage with video, users may see a gray rectangle with a QuickTime logo until they tap the Play button. Therefore, use a poster JPEG as a preview of your movie. If you use QuickTime Pro 7.2.1 or later to export your movies, as described in “Encoding Video for Wi-Fi, 3G, and EDGE,” then a poster image is already created for you. Otherwise, follow these instructions to set a poster image.

If you are using the <video> element, specify a poster image by setting the poster attribute as follows:

<video poster="poster.jpg" src="movie.m4v" ...> </video>

If you are using an <embed> HTML element, specify a poster image by setting the image for src, the movie for href, the media MIME type for type, and myself as the target:

<embed src="poster.jpg" href="movie.m4v" type="video/x-m4v" target="myself" scale="1" ...>

Make similar changes if you are using the <object> HTML element or JavaScript to embed movies in your webpage.

On the desktop, this image is displayed until the user clicks, at which time the movie is substituted.

For more information on including QuickTime Movies in webpages, see the tutorial Including QuickTime In A Web Page.

Configuring Your Server

HTTP servers hosting media files for iPhone OS must support byte-range requests, which iPhone OS uses to perform random access in media playback. (Byte-range support is also known as content-range or partial-range support.) Most, but not all, HTTP 1.1 servers already support byte-range requests.

If you are not sure whether your media server supports byte-range requests, you can open the Terminal application in Mac OS X and use the curl command-line tool to download a short segment from a file on the server:

curl --range 0-99 http://example.com/test.mov -o /dev/null

If the tool reports that it downloaded 100 bytes, the media server correctly handled the byte-range request. If it downloads the entire file, you may need to update the media server. For more information on curl, see Mac OS X Man Pages.

Ensure that your HTTP server sends the correct MIME types for the movie filename extensions shown in Table 8-1.

Be aware that iPhone OS supports movies larger than 2 GB. However, some older web servers are not able to serve files this large. Apache 2 supports downloading files larger than 2 GB.

http://cocoawithlove.com/2009/04/easy-custom-uitableview-drawing.html

"Error Domain=NSCocoaErrorDomain Code=3000 UserInfo=0x113e80 "no valid 'aps-environment' entitlement string found for application"

APNS Error

XCode: Could Not Support Development

Today  when I started my work on an iPhone project, my XCode failed to mount my iPhone. The XCode organizer was showing an orange dot next to it instead of the usual green one. Organizer complained “Could Not Support Development”. I tried restarting my XCode, launched iTunes but in vain. iTunes was able to mount my iPhone but XCode simply failed and I was not able to test my app’s on my phone. Finally I restarted my iPhone and tried again. Bingooo..! it started working again. My iPhone was running the latest iPhone OS 3.0 GM developers build. See left for the screenshot of the error message that I got.

Error Starting Executable

Quite a few times in our iPhone application development cycle we would encounter XCode error “Error Starting Executable – No provisioned iPhone OS device is connected.” even when we know the device is connected to the machine.   This error occurs when the connected device is not configured in the XCode->Organizer. Organizer would fail to mount the device as the version of XCode installed on the developer machine may not support the version of iPhone OS installed on the device.

If you select the device in the Organizer, then XCode would list you the supported iPhone OS versions as well as the OS Version of the device. (An organe dot aganist the device in Organizer indicates it has not been mounted properly.)

iPod_Unmounted_In_Organizer

- (void)viewDidLoad
{
    self.view.backgroundColor = [[UIColor alloc] initWithPatternImage:[UIImage imageNamed:@"MyBackground.png"]];
}

the first feedback would be I am missing all the formatting options that I take for granted on desktop version of wordpress.

If you come across anyother reasons for getting this error message, do let me know.