Storyboard loads forever with "An internal error has occurred editing functionality may be limited"

Question

idomo OP

Created Jul ’19

Replies 6

Boosts 0

Views 4.9k

Participants 4

Having this issue since beta 3 came out and hoped that beta 4 will fix this, but it didn't.

Every time I'm opening Main.storyboard in xCode, I'm getting the death wheel (colorful endless spinning wheel) with the error "An internal error has occurred editing functionality may be limited".

The only option I have is to "Quit immediately", but when opening xCode again, it loads the storyboard since is the last file I've opened, so the only way to be able to use xCode at all is to go to the project directory, right click on the .xcworkspace file, click "Show package contents", locate the file "UserInterfaceState.xcuserstate" and delete it.

Only after deleting this file I'm able to use xCode as normal as possible and of course, the storyboard is still not accessible.

Well, I've reported to Apple via the Feedback Assistant and via the email and also updated them that it happens also in beta 4, but it doesn't seems like anyone cares about it.

It doesn't seems to happen with any other storyboard file from other projects and the launch screen file, it's only in this specific file, but the exact same file (without any changes) was working perfectly with xCode beta 2.

Also, since this issue has begun, some specific ViewController's localization stopped working(?), it's just showing this specific one in English (base) translation while the whole app is showen in anouther language (the device's/simulator's main language, it happen on both iOS 12 & 13), maybe it's related some how? 😕

* Tried everything from restart the Mac to deleting Derived Data (several times), went all over google (this forum, stackoverflow and some more places) - nothing helps.

This is the closest description to my issue, that of course, doesn’t have any helpful answer.

* The app is running fine on real device/simulator with iOS 12/13 (respectively).

*I have xCode 10.2.1 installed, but can't open the project or the storyboard there 'cause I've adopt iOS 13 color scheme that doesn't supports there.

* Using macOS 10.14.4 (18E226)

Any suggestions? I'll really appreciate any kind of help.

The storyboard file (remove the spaces around "google"):

drive. google .com/file/d/10ynwU7mtTIUE8pW2Ud4dHtSAzJTv5vEc/view

Boost

Answer 1

Claude31 OP

Jul ’19

First thing would be to check all IBOutlets connections, in case oine is broken.

That could also be caused by an error in code (I remember getting this problem some time ago: https://forums.developer.apple.com/message/125837#125837).

What you could try, to localize the error, is to comment out all the code you can comment out. And see when the problem disappear.

0

Answer 2

idomo OP

Jul ’19

Hi, thank you for comment here.

How can I check IBOutlets connection if I don't have access to the storyboard?

There is a lot of code and if the storyboard is crashing I have to quit xCode and open it again after deleteing some file that I've specified in the first comment, It will take forever to check all of the code in my project...

I still think this is an issue in the .storyboard file itself, but I don't know what can cause that in there and I can't comment anything there, otherwise it will show an error that the storyboard can't be opened.

0

Answer 3

Claude31 OP

Jul ’19

You can open storyboard file as html to inspect manually. But it is very verbose and hard to track.

0

Answer 4

KMT OP

Jul ’19

>How can I check IBOutlets connection if I don't have access to the storyboard?

Not sure what that means....you have the project and it's files, right?

Simply use the storyboard editor to check that storyboard's connections, meaning to redo them fresh one by one, followed by an option-clean build folder when they're all reconnected. How to make connections in the first place if you need a refresher is here:

https://developer.apple.com/library/archive/referencelibrary/GettingStarted/DevelopiOSAppsSwift/ConnectTheUIToCode.html

>otherwise it will show an error that the storyboard can't be opened.

If that means manually editing a storyboard, right...it's easy to do more harm than good. Be sure to have a backup if you take the plunge, but my advice in that case is to just use the backup and avoid molesting the storyboard manually.

0

Answer 5

idomo OP

Jul ’19

That’s what I’m saying, the only way to see the storyboard file is with the source code editor and every little change there causing error message that xCode can’t open the storyboard, it doesn’t even makes it to the death wheel part...

0

Answer 6

idomo OP

Aug ’19

The only sulotion I could find is to downgrade to xCode 11 beta 2 (link to download) that doesn't have this annoying issue.

Hope that they would solve this before the last realese.

0