UIKit.h not found error - objective-c

I made a single view app for the ipad, with a movie, webview and button, and I get this error when I try and run it. I have restarted the application, and reinstalled it, but nothing is working. This error keeps coming up in my MoviePlayer_Prefix.pch file. Can someone help me out?

I have had the same issue with being unable to compile project due to UIKit.h not being found + "unable to load standard library for target..."
The solution for me was very simple - to quit (CMD+Q) and relaunch Xcode. I have found out that with Xcode opened, macOS seems to have removed command line tools for Xcode because it was preparing for a update and relaunching Xcode triggered the "install additional components" update and it made the problem disappear.

Like Faul Textor said, most likely your XCode updated to 12.1 but your Command Line Tools didn't. You need to quit XCode completely and then start it again and you should get a pop-up saying "Install Additional Components"
Sorry, this should have been a comment to his reply but I cannot do that.

It sounds like you removed the UIKit.framework from your project at some point. Check if it is listed in your project navigator. If it's not there, go to your project in the project navigator pane, select your target, go to the build phases tab, click on link binary with libraries, hit the plus button, find the UIKit.framework there and add it to your project.
EDIT:
This answer suggests that there mayb be an issue with your framework search paths build setting. Check that out and if the path is empty and it still doesn't work, a re-install of Xcode would fix it, I think.

Just wanted to add my two cents on not making a dumb-ass mistake - came across this answer hoping to solve same problem.
Turns out I had written #import "<UIKit/UIKit.h>" instead of #import <UIKit/UIKit.h>.
Thought I would add in case someone else makes a simple mistake like me.

Related

How to troubleshoot React Native build error?

Below you can see the output I get when I try to run npx react-native run-android. It suggests some options to try in order to further pinpoint the problem, however they don't work with the aforementioned command so I assume that they are related to a gradle (just an educated guess).
I know ZERO about gradle; I have just seen the name here and there and in the output shown below. So please keep that in mind when you answer. If I need to learn how to run some gradle command(s) directly, please be as verbose as possible in your answer.
The project was working fine just a bit ago, but I wanted the ability to force portrait mode for certain screens but without configuring my entire app to always have to stick to portrait mode. So I found what looked to be a solution in the react-native-orientation-locker module. I installed it with yarn and then proceeded to update files as directed: https://www.npmjs.com/package/react-native-orientation-locker.
After updating the appropriate files, I got an error that suggested axios was the problem. I uninstalled and reinstalled axios. After that didn't work, I proceeded to undo all the file changes I had just made. Then I uninstalled the react-native-orientation-locker module.
To my knowledge, I have undone everything I did between the time the project worked and stopped working.
Sadly, I had not put this into source control yet (a mistake I won't make again), so I can't revert.
Where to go from here?
Problems like this are hard to pin point. What you can do is open the android project in android studio and see the logs as the project is being assembled. I assume you do not have much knowledge about android either so you might need some senior resource to help you.
What I usually do in this case is open android studio and if I am lucky enough, it tells me which file has an issue and I go to the file and do what android studio suggests me. Some times it fixes the problem and sometimes it doesn't.
Another thing I would like to mention is that the documentation of the package you are using is important to follow. I assume you did that already but I would suggest to review it narrowly and closely.
Another guess I can tell you is try to go to your-project/android/build.gradle and over there, you'll see something like this in the start. The package you are using mentions something about target SDK 27. I think you should check that out too. May be it helps
Lastly I would say always use source control while working with react native. It can easily blow up at any time so you should always have a safety net to fallback to :)

Codename One: App broken after iOS build

I have been building my App for Android repeatedly without any errors. I know tried to also build it for iOS which would not work, since I now know that I need a Mac.
After that, I tried to build it again for Android and now everything seems broken. IntelliJ tells me everywhere that it "can't resolve Symbols" and "can't resolve methods". I tried opening and closing the IDE and also restarted the computer, tho I am not able to make a successful build again. This just started after the failed iOS build.
Here is a Screenshot for you, those are very simple lines, there is no reason for them not to work. I am really clueless right now what wrong.
Maybe someone of you has an advice for me? I can only repeat, i did not change the code at all, but it just won't compile anymore, neither in the simulator nor with the Android build.
That may be due to a missing or corrupt CodenameOne_SRC.zip and/or CodenameOne.zip and/or JavaSE.jar files.
Solution:
Create a new dummy Codename One project, right click on the dummy project and select Properties then click the Update Project libs button. Once it's done, close the dialog and right click the project again, then navigate to Codename One -> Refresh cn1lib files.
Now close the dummy project and minimize your IDE and go open your Dummy project folder in your file explorer. Now copy the CodeNameOneBuildClient.jar and JavaSE.jar found in the main folder to the relative path of your faulty project, replace them if already exist. Do the same for CLDC11.jar, CodenameOne.jar, CodenameOne_SRC.zip that are found in the lib folder of your dummy project.
Go back to IntelliJ and right click on your faulty project and navigate to Codename One -> Refresh cn1lib files, then clean and build your project.
This should fix any reference or missing class issues.
FYI, you don't need a Mac to build an iOS project in Codename One.

Xcode 6.3.2 unable to build or run projects

After upgrading to Xcode 6.3.2 I'm unable to build/run, analyse, profile project. Even project clean functionality looks broken. Does any body experienced similar problem and know how to fix it?
The problem appears to go away when you go download and install the new command line tools for 6.3.2.
After struggling with this problem for couple of hours I have finally found solution. In my case Xcode Derived Data location was set to custom folder and it was the origin of the problem. After changing Xcode Derived Data location to default one everything back to normal.

Xcode builds on Debug but not on Release

So, I have this problem when trying to build my project.
Currently If I run the project in Debug mode, it runs fine, the app starts up on the device and I can test stuff.
However the weird part is when i switch over to the Release build and try to build on the device. When I press the Run button Xcode builds as normal and the build succeeded notification even pops up, but then I get this error code.
Lets call my app xxx
Could not launch "xxx.app"
No such file or directory:
/Users/*my Name*/Library/Developer/Xcode/DerivedData/*Bunch of xcode folders*/Products/Release-iphoneos/xxx.app/xxx
I went into finder and searched up xxx.app and couldn't find it. Furthermore there doesn't even exist a Library folder under /Users/my Name/.
So what is xcode trying to do here, and what should I do to fix this?
Edit: I have also tried Cleaning the project and building again, the error code still comes up.
I get this crap all the time.
What I do is clean the project, close it, shut down Xcode, start up Xcode, open project, then build and run.
If that still does not work then find the "DerivedData' folder Organizer->Projects and delete it, then do the above again and try again.
I tried creating a new scheme and setting it to Release mode. That worked for me. However, a reboot after closing xCode seems to work, too.
I went into finder and searched up xxx.app and couldn't find it. Furthermore there doesn't even exist a Library folder under /Users/my Name/.
It does exist, but it's hidden (since OSX Lion) in the Finder (because standard users -- as opposed to developers -- should not mess with it).
Some utilities (on a simple command line) can make it visible again but the simplest thing to do is to use "Go" menu of the Finder and select "Go to folder…" (Command-Shift-G). Then copy/paste the path you want to go to and validate.

MonoTouch / MonoDevelop: "Did not get project info" when opening xib-files

So, I just installed everything needed for MonoTouch on a MacBook running Lion.
I followed the steps/instructions to install (see here) and then created a new solution. When I open my xib-file I get the following error (in MonoDevelop):
Error updating Objective-C type information. Did not get project info
System.Exception: Did not get project info
at MonoDevelop.Macdev.XcodeSyncing.XcodeProjectTracker.UpdateTypes(IProgressMonitor monitor, Boolean force) [0x00029 in /Users/builder/data/lanes/monodevelop-mac-2.8.6.4/ca00645c/source/monodevelop/main/src/addins/MonoDevelop.MacDev/XcodeProjectTracker.cs:351
I have done nothing else than installiong Xcode, then the Framework/Runtime (MRE-2.10.8_3), then MonoDevelop (2.8.6.4) and then MonoTouch.
Anyone seen this before? I can't find a single thing in this specific error on the net.
It seems that I needed to close the solution, restart the program and then some form of "updating xcode"-thing was running. Then it worked with getting the designer up. Of course, I can't see the Assistant Editor and create those outlets, but that's another issue...
I fixed this issue by building the application, and then double clicking the xib file.
I fixed this issue by building the application, closing and reopening the solution, and then double clicking the xib file.