Xcode 4.6.3 Bug - .m file won't open or has issues in opening

506 views Asked by At

I have a weird problem. I have Xcode 5.0, but I'm still using Xcode 4.6.3 because I want my apps to retain the iOS6 look.

The problem I have is, when I click some .m files, the file loads, then the scroll disappears (so I can't scroll down at all), and sometimes the file shows empty (but actually, the file isn't empty).

It works fine on Xcode 5, but not on the old version.

Edit : See the image below (and notice the curly brace in the bottom)

xcode 4.6.3 bug

other issue

Any help would be appreciated.

Thanks guys!

3

There are 3 answers

0
Lukasz Mozdzen On

I have same problem. Can't load one of the files on Xcode 4.6.3. It works on Xcode 5. Problem is that my app doesn't looks like it was on other version. I changed storyboard to looks like iOS6 and earlier but still all my views went up a little bit, even tables are partly hidden by navigation bar.

Also when I try to open that file whole Xcode 4.6.3 crash

0
Erwin On

This sometimes works:

  1. Open the file in another text editor. Textmate works for me.
  2. Do a minor edit. For example: add a blank line.
  3. Save the file using that text editor.

When you switch back to Xcode, the file should be restored and usable.

0
jem On

Had the same problem happening here. In this case, inside the class was the following autogenerated code:

- (void)tableView:(UITableView *)tableView didSelectRowAtIndexPath:(NSIndexPath *)indexPath {
    // Navigation logic may go here. Create and push another view controller.
    /*
    <#DetailViewController#> *detailViewController = [[<#DetailViewController#> alloc] initWithNibName:@"<#Nib name#>" bundle:nil];
    // ...
    // Pass the selected object to the new view controller.
    [self.navigationController pushViewController:detailViewController animated:YES];
[detailViewController release];
    */
}

Not sure why, but the culprit seemed to be the hash symbols on the first line inside the block comment. Removing those and saving from a different editor resulted in the file loading correctly in Xcode.