On the first-generation iPod debugger can not display interface

Xcode 4.3.1 is used to create a "Simple View Application"
Make the necessary changes (such as rootViewControler, armv6 and the like), specifying the target is running iOS3.1. Select the device debugging (Xcode already cracked).
Xcode shows the build is completed, copy the files to iPod also completed and running. . . It started when the iPod like a program, but nothing is displayed. Trace debug to
- (BOOL) application: (UIApplication *) application didFinishLaunchingWithOptions: (NSDictionary *) launchOptions
This statement
method[Self.window addSubview: self.viewController.view];
Implementation of this statement would not return it.
However, if you stop debugging, run directly on the iPod just past the Xcode install the application's icon, then running is normal.
Someone encountered this problem?
I guess not when debugging XIB file path of the class can not be found (formerly VC Debug debugging path often have problems), but can not find any place Xcode comes to debugging path. . . .
Reply:
Depends on the specific reasons for the debug log.
Generally due Developer certificate.
Reply:
Debugging on your device, development of supply is the need to create the configuration file, provisioning profile, Apple company IOS development process strictly controlled, for fear that you will develop their own applications easily mounted on someone else's hardware devices, each iphone or ipad has a unique identifier, the identifier you need to create a profile by apple official before they can run on their own devices to develop their own software for testing, do not take the android developers ways to measure, create a configuration file The process is complex, it is recommended Baidu, or simulator tests.
Reply:
/ / Set the view controller as the window's root view controller and display.
self.window.rootViewController = self.viewController;
[Self.window makeKeyAndVisible];

This sentence was replaced with top [self.window addSubview: self.viewController.view]; Try
Reply:
rootViewController is iOS4.0 more support, if
self.window.rootViewController = self.viewController;
[Self.window makeKeyAndVisible];
Then executed there directly throw an exception that can not find this selector.
In addition, the certificate is certainly not a problem, because I use real machine debugging run that has seen the program installed on the target iPod, and it stops debugging, run the application directly on the iPod dot display is normal.

In addition, I also left a test today, creating a Empty Application, which is no NIB file applications, debugging and display are normal. I feel that when debugging the application can not find the NIB file, you can not create view like the corresponding. . .
Reply:

reference to the second floor holydancer reply:

on their device debugging, development of supply is the need to create a configuration file, provisioning profile, Apple IOS Development Company process is strictly controlled, for fear that you will develop their own applications easily mounted on someone else's hardware devices, each iphone or ipad has a unique identifier, you need to create a profile by apple Crown under the identifier can only be in develop their own software running on their own equipment for testing, do not take the android developers ways to measure, create a configuration file is very complicated, ......

Certificate has been ready, the preparation of the program can be run separately, that is not online debugging.
Reply:
Look debugging output

I once had a similar problem occurs, can correctly installed on the device, and run normally, but can not debug. The reason is that the certificate expired message class.

Reply:

reference to the 6th floor ybh37 reply: output

look debugging
I once had a similar problem occurs, can correctly installed on the device, and run normally, but can not debug. The reason is that the certificate expired message class.

Debugging output is not content ah. . . . I hit a log in the main function, there is an output,
In didFinishLaunchingWithOptions played at the beginning of the log, there is an output
Played at the end of the log, not output, the program will hang in there no more.
Look at a single pace went [self.window addSubview: self.viewController.view]; then stopped.