On Aug 29, 2015, at 08:47 , Alex Hall <[email protected]> wrote: > > I've seen this off and on in the last few betas, and have no idea how to > solve it. Sometimes, when I make a new project, a file will show the error > "no module named 'UIKit'". The file is empty apart from the code Xcode > inserted automatically, so there can't be a typo in UIKit. Is there a simple > fix for this, or is the bug at least known, if indeed it is a bug and not > something I'm doing wrong? Thanks!
What file? If you’re talking about a file created as part of the new-project template, then it’s not going to be “empty”, but will have some boilerplate in it. If you’re saying you create a new class file, then my guess would be you’ve forgotten to set the correct target membership when you created the file. If neither of those apply, then there might I suppose be errors that appear temporarily because Xcode does several things asynchronously (such as indexing) just after creating a project. When you get the error, what happens if you go ahead and build anyway? Is there a build error, or does the original error go away? _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
