I'm now running Mavericks and the latest Xcode on a mid 2009 MPB. There is no problem creating the AwesomeProject and then building with Xcode. The problem starts once the simulator comes up. I see the white Powered by React Native screen and then after it goes away it takes a very long time and finally the Packager gives me the following output:
Error: ENOENT, open '/Users/SM/AwesomeProject/AwesomeProject.xcodeproj/project.xcworkspace/xcuserdata/SM.xcuserdatad/.dat2864.046'
at Error (native)
[3:15:07 PM] <START> request:/index.ios.bundle
[3:15:07 PM] <START> find dependencies
[3:15:10 PM] <START> find dependencies
This is followed by the big red screen!
Xcode also notifies me that it got disconnected from the simulator. The one warning I do see in Xcode is:
"Applications using launch screen files and targeting iOS 7.1 and earlier need to also include a launch image in an asset catalog."
How can I finally complete the Getting Started test and experience React Native?
The red screen only has two options on it which I'm not able to use, its likely just the result of not being able to run the Simulator on my machine:
Bottom line I do not have enough RAM, only 4GB. After investigating it looks like I need to upgrade or get a new Mac at some point in the future. Its been a max frustrating day for me to say the least.
Here is what Activity Monitor tells me about my machine:
That is how my machine looks without Xcode and the Simulator running! There are two upgrade options if I want to keep going now. Double my RAM and optionally get a SSD. Does anyone know if this will be enough to get the Simulator working?
I did see this link saying that adding more RAM helped:
http://iphonedevsdk.com/forum/iphone-sdk-development/120512-how-much-ram-needed-desirable-on-an-xcode-build-machine.html
UPDATE
After the upgrade to a 500GB SSD, more RAM and a clean install of Mavericks things are working swell. I highly recommend this as a way to get more life out of a older MBP. Thanks to Memory Express and the Apple Store for all the tips and sweet deals.
Related
I create a flutter app and now I'm trying to run it through XCode on my real iPhone, but after the installation finishes, I face the following problem:
Also with I trying to run the application on my real phone, after clicking on the application icon, I face a white screen appears, and then the application closes directly.
Catalina 10.15.3
IOS 14.2
XCODE 11.7
Also I was make a trust to app in phone
Does anyone know the reason for this problem?
This problem maybe because of two reasons:
First: Xcode 11.7 doesn't have support files for iOS 14 you can download it from here https://github.com/filsv/iPhoneOSDeviceSupport
Second: I have this problem now and I couldn't fix it.. but I have iPhone with iOS 14.2 and iPad with iOS 14 so the problem was just on the iPhone but after I updated the iPad with iOS 14.2 it happened with it.. so the problem maybe because of the iOS 14.2 so we have to wait for the update or because of the Xcode 11 version and we have to download the Xcode 12 version..
I hope we can find a solution quickly...
make sure to have the latest system update on your target device and the latest Xcode version as well. The error should disappear.
Best,
Ralf
I have fixed the problem by using the above solution but it has happened again. So, I have followed these instructions and fixed again:
https://stackoverflow.com/a/61665031/6586109
A good first place to look is Window > Devices & Simulators in xCode, then find the details for your device. There may be error information here that helps you find the fault.
Restarting devices and installing updates seem to fix this problem for a lot of people.
For me, there was a red notice in the device window about connection to the device and it turned out to be the cable that was at fault.
This was an official Apple cable, just a few months old, and still works fine for charging and data transfer; and I've been using it with xCode without problems for a couple of months. It seems to be possible for Apple cables to develop some tiny physical fault that seemingly only xCode is sensitive to.
Using a different cable worked first time for me.
There seem to be a few variations on the exact error message with the same root causes varying depending on exactly what xCode was trying to do at the exact moment it failed: I'm on xCode 12 and for me it was:
Failed to start remote service on device
Failed to start remote service com.apple.installation_proxy on device
For Past 4 week i observer when i run my Xcode application on simulator on first time simulator launch it consume around 500MB internet data.
This is not project specific issue. Every time when i shutdown and start the mac and run Xcode as soon as simulator open it will consume same amount of Data.
Can any one help me What is the issue?? or any background service run??
Xcode version: 11.6 (11E708)
simulator: 13.6
OSX: 10.15.6
Please help me unnecessary every time my Internet Data is consume i have to fix this
This issue is still persist after updating to xcode 11.7
Thanks For #Rado for suggesting the https://apple.stackexchange.com/.
After posting the question on https://apple.stackexchange.com/ i fond the answer.
Orginal Answer: Xcode simulator constantly download something
Answer:
rename the file com.apple.nsurlsessiond(Dont delete) in
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/System/Library/UserEventPlugins/com.apple.nsurlsessiond.plugin/
to something -com.apple.nsurlsessiond
and also the file nsurlsessiond(Dont delete) in
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/usr/libexec/
to something -nsurlsessiond
Apps with admob works perfectly also no problem with safari
If you don't need an internet connection for testing you application, you could simply disable the network.
You could run wireshark and see what it is actually doing, or at least see where it is connecting to.
I used tripmode firewall don't give simulator internet access only give when you need it.
Works fine but when you forget to turn it off and start the simulator next time, you feel horrible :(
I'm running into an issue where my iMac, with over 100G free, gets Disk Full Error after running Flutter for an hour or so.
When I reboot I get dozens folders in my Trash "Recovered Files" that are around 2G each.
The issue is actually described fairly well here (with screenshots): https://github.com/flutter/flutter/issues/56270
However, the moderator closed every comment as "off topic" (seems like several people are having this problem). So I figured it may be a good idea to bring this here to see if anyone else has found a solution for this?
I'm running VSCode and when I run Flutter Doctor I'm 100% compliant. Using the latest Flutter/Dart/MacOS/Xcode/Android Studio versions. I am primarily building my Flutter app to macOS platform (desktop).
I tried the suggestions in the above issue post and none of these worked for me (re-installing cocoa pods, re-installing Xcode, re-installing Android Studio).
I actually ran into this issue about a week ago. The comment linked to had put me on the right track, where they mentioned it only happens when they have an iOS device attached to their machine.
If you see something like this error in your VSCode output log when launching your app, then it's likely the same issue.
Failed _shouldMakeReadyForDevelopment
If you have a device attached and it's locked, I believe something in the Flutter env attempts a connection over and over causing these files to fill up.
However, this happened to me once even when I didn't attach a device and I found out it was because I had "wirelessly" attached a device in Xcode when I was doing iOS development for another project. So just sitting at my desk with my iPhone nearby was enough to cause it to try to connect over and over again, even if it wasn't attached.
I removed my iPhone from Xcode's wireless device list and that seems to fix it.
Can confirm, running flutter with an attached ios device eats disk space.
This is happening to myself and another developer on my team. I lost 200 GB of disk space yesterday. It's a frustrating productivity killer.
I am using the latest flutter
flutter doctor reports everything as fine
xcrun --find simctl is fine
Using Android studio 3.6.3
Latest patched Catalina 10.15.4
This morning I opened the Android Studio IDE with an android device and an ios device connected. I opened a get info window on my hard drive and left it open. Then I did nothing but watch the info window. No builds or anything. Over the course of a couple minutes, I watched 7 GB disappear.
I shut down the IDE and the loss stopped. I reopened the IDE with only the android device attached. I waited and watched for a few minutes. No loss of disk space.
Then I reopened the IDE with just an ipad attached and the losses started again. Then I unplugged the ipad and left the IDE open and the losses stopped.
Same here but happens also when just running Android Emulator.
This needs to be fixed A.S.A.P - its a dealbreaker!
When the problem happens and the disk runs full, my system slows down so much I can hardly do a thing. To free up disk space and get operational again quickly, there's two options:
Restart. Then the cache files are either deleted or end up in "Recovered Files" in Trash, as described by #william-t, from where you can delete them.
Directly delete the cache files in "TemporaryItems" (for me that's below /private/var/folders/bc/gw57z9dn4rn2v6df7306k9sh0000gn/T)
I know this is not a solution to the root cause of the issue, and it still helps a lot, as long as there's no true fix...
I am having trouble loading a game app on genymotion. The game is Star Wars Force Collection. I can load the game, get the splash screens, then it crashes.
I have done some research before I posted here. The possible problems found in the genymotion logcat file:
There was a line noting Google services was out of date, "Google Play services out of date. Requires 4030500 but found 3225136"
Fatal signal 11 (SIGSEGV) at 0x00000364 (code=1), thread 1796 (RefQueueWorker#)
W/NetworkManagementSocketTagger( 280): setKernelCountSet(10040, 1) failed with errno -1
Some have pointed out ARM Translator problem and OpenGL.
Then again I'm really not sure the problem, and I want to post the logcat file here but I don't know how to attach it.
For problem 1, I have seen other thread here that may have fixed it with code, I'm not savvy enough for that and my Google is not updating itself.
That's about it. A few details about genymotion and the VM. I am running the latest version of genymotion and virtualbox. I am using the downloaded Custom image 4.3 as provided by Genymotion. I flashed the ARM Translation v1.1. I flashed the Gapps onto it, (I tried a higher version of Gapps to try and solve the problem, but that just made it crash) and then Star Wars Force Collection, most up to date version.
Also, worth noting that the app was running fine for v2.++, until an update to v3.++ made the game crash. I updated my graphics drivers to try and mend any graphics issues.
So there it is, any suggestions will be appreciated.
The "verifying application" step of the build process in fully updated XCode 4.6 (and previously 4.5) often takes upwards of two minutes on my machine. Coworkers building the same application on similar computers have this step take only a couple seconds. My machine used to, as well, but does not anymore, for the past few months.
Does anyone know what could be causing this and how I can fix it?
Update your device to the latest version of iOS, 6.1.
Had the same issue, fixed after updating my iPad3.
Try rebooting your device.
I had the same problem using XCode 4.5.1 and an iPad 6.0.1, but didn't want to update at the time. In additional to a long 'Verifying Application' step, I noticed that copying resources over was also slower. After that, I disconnected the iPad and tried to delete my App, but discovered that even the device's delete alertview took several moments. So, obviously, for me, this was a device issue, and after performing a shutdown / restart of the device, xcode performed up to previously normal speeds.