For some odd reason every time I use Xcode on the latest El Capitan beta, my CPU starts spiking and I start hearing the fans in the computer. I decided to check Activity Monitor and realized PTPCamera was the culprit.
Why is it being launched and what is it being used for? Quitting the process doesn't affect Xcode in any way and the CPU usage returns to normal. There are no other devices connected to my computer other than my iPhone.
I'd be very grateful for an answer because this is getting really frustrating. The only helpful link I found online was this one.
Image:
Related
This is happening intermittently, but frequently iOS devices are connecting to my MacBook Pro (mid-2014) and then quickly disconnecting. Without any clear error or log to indicate why.
Where should I look for event logs that may help indicate what the underlying error is? I've tried to look through console logs for system events but I haven't seen anything that jumps out.
I've gone through many of the recommended solutions for Xcode not recognizing iOS devices:
Clean Project
Delete DerivedData folder
Restart Xcode
Restart the Mac
Restart the iPhone
Reset device permissions to re-trigger the "Trust Computer" prompt
Deleted iOS DeviceSupport folder
Alternated USB ports
Kill USB process
Deleted and re-installed the latest version of iTunes
Swapped out 4 different lightning cables
Tried 5+ different iOS devices with various versions of the OS
Went back to Xcode 8.2.1 to see if it was an issue with 8.3.1
Corporate IT reset my SMC this morning. I put in a request to have them disable Sentinel Agent to see if that's a factor, but it's not the clear culprit since other developers are still able to connect.
Very rarely, the connection will hold and I can use the device just fine. I have yet to determine what combination of astrological events leads to that case though.
Had the same issue and tried 10+ of the things you listed as well. Even tried uninstalling a few things that could have been interfering. As soon as I switched USB ports it worked and stayed connected. Turned out to be lint/dust in the USB port. A little duster in the port and it works like a charm. Sometimes the answer is so simple.
This is a disappointing solution, but IT reimaged my machine and the device connection has been stable ever since.
So if all else fails for you, start over.
Update:
This ultimately was narrowed down to an issue with Mobile Labs Device Bridge. Removing their launch daemons and restarting the system is the much simpler solve!
I have an app that is available on AppStore, it is a biological recognition app, so there's lots of C/C++ code in this app, and it goes well on iOS7 to iOS9, but when I tested in on iOS10, it always crashed dued to memory issue after several trials, I tried the Allocation instrument, not much leaks.
When I tested it in xCode, I found something interesting(I already shut down every app that run background), the memory usage of other process increased dramatically on iOS 10.
iOS10_iPhone5s
But it didn't increase so much on iOS9:
iOS10_iPhone5
So I have several questions here:
what's in other processes, it should be the apps that run background, but why the memory usage increased even I shut down all the other apps?
why I can only reproduce this issue on iOS10? and it runs well on iOS7-iOS9.
Can anybody help me? thank you.
"Other Processes" includes literally every other program that is currently running on your Mac. That number has nothing to do with the simulator. It does not measure processes that run in the simulator.
If you run iOS Simulator Xcode shows memory stats from your Mac.
Please refer this as well
Running out of memory in 'Other Processes' in Usage Comparion Xcode iOS9
iOS Memory Management -- Other Processes RAM Increasing
Today, my builds suddenly started taking a long time to install & launch on my iPad (using XCode 7). During the "Performing Install Actions" phase, it hangs for about a minute, and then when the launch screen shows on the device, it takes about another minute for the app to launch. After the app launches, it runs normally without any issues.
I've restarted Xcode, cleaned the app, deleted build folders, deleted DerivedData, restarted OSX, restarted iOS, deleted the app from my iPad, and even upgraded iOS on the iPad to 9.0.2.
Edit: This issue originally seemed to be specific to the iPad Mini 3 I was using; it didn't happen on the iPhones I'm testing with. Now, after the weekend, it's happening on an iOS 8.4 iPhone 5s that I'm also developing on.
Edit 2: This was happening sporadically yesterday and it now seems to have cleared itself up, on all my devices. Still no idea what steps to take to fix this if it happens, though.
Edit 3: It continues to happen, but much more rarely.
I've been dealing with this same thing, but connecting the phone to WiFi seems to unblock my installs. Who knows why... but give that a shot if you're still running into this issue.
I recently ran into this problem and resolved it by restarting the device. I have no idea of what the cause is so I am reticent to suggest this is a universal solution but it did work for me once in a row.
Fix : Turn off iPhone wifi. restart it and install the app now. Now you turn on the wifi. and it works. Fixed.
I had a similar problem, but for me the app wouldn't launch at all. This might have been happening because I was connected to a WiFi that didn't have internet access. Changing to a WiFi with internet access solved the problem for me. It started happening suddenly for me as well, so not sure what triggers it. I've now changed back to the WiFi without internet access, and it seems to work again.
I met this problem in Company, but not at home, when debugging on device.
So if you are working under a company WIFI, just Changing WiFi to Internet Access will solve the problem.
I had the same problem just now.
What does NOT work for me:
Restart Xcode
Clean the project
Unpair and reconnect the device
(Re)connect to wifi
What DOES work for me:
Restart the device and build again
Another possible cause is low disk space on your Mac. Make sure your mac has enough space - I was running with 13mB space remaining... This will impact cacheing etc. and will cause delays on your build.
I have this issue when my Apple Watch are on me. Maybe some problems with paired devices.
I'm trying to debug a potential javascript memory leak on iOS. My approach (was) to monitor Mobile Safari on my iPad using Instruments, but there's a problem: no matter what process I attach Instruments to, I get no data at all. After setting up the items to watch and starting the monitor, it runs along happily, but shows no memory usage, no CPU usage, nothing. Is there something I need to do with my iPad or Instruments to enable collection of this data?
I also had this issue with xCode 6 where the instruments would show like it's recording data although there was no actual data presented or collected.
Restarting my Mac Mini, restarting xCode, cleaning the build and disconnecting and connecting my iPad did not solve this issue.
However, my other devices were profiling just fine.
The solution I found is to reboot the iPad. (You reboot your device holding the home button and the power button for a few seconds. Then to turn it on again you press the power button).
This solved this issue and I was told it can solve other xCode related issues like when your program keep running on Debug even when you run it on Release.
Hope this helps.
I'd like to understand why, and find a solution obviously. I can't figure it out, given the console disappears as soon as the device reboots and is then reset when it comes back from the reboot. So I don't have any clue of what's going on there.
iphone4, ios 5.0.1 installed, jailbroken when the latest redsnow & untethered JB. I tried in safe mode, same thing.
I noticed that everytime I connect the phone osx mounts a developerdiskimage volume while xcode is displaying "checking DDI symbols", and after that then the phone is considered valid for dev by xcode. After the phone just rebooted, it's shown as invalid for development in xcode, until I unplug / replug it. I don't think I ever noticed that before, could it be related?
With the new ios 5.1.1 jailbreak out. You might want to revisit it again. I had a similar problem where I could mesure leaks but trying to mesure CoreAnimation or anything else would restart the device.