Deploying to real iPhone became very slow at CopyingFile - xamarin

Deploying from Visual Studio for Mac (latest version 8.8.8) to my iPhone (latest iOS version 14.3) has become very slow, much slower than I remember.
As a test I'm deploying a very simple app (almost a bare project) and it's taking over 3 minutes (!) to get it done.
In the 'Deploying to device' window it takes ages to complete copying:
CopyingFile - Path: /Users/adamsfamily/Documents/VisualStudio/sample-app/sample/sample/sample.iOS/bin/iPhone/Debug/device-builds/iphone13.3-14.3/sample.iOS.app/META-INF/com.apple.ZipMetadata.plist
CopyingFile - PercentComplete: 10%
...
CopyingFile - Path: /Users/adamsfamily/Documents/VisualStudio/sample-app/sample/sample/sample.iOS/bin/iPhone/Debug/device-builds/iphone13.3-14.3/sample.iOS.app/Xamarin.iOS.dll
CopyingFile - PercentComplete: 10%
...
I am deploying over WiFi in my local area network. I make an Ookla speed test to verify my connection and both my Mac and my iPhone are well over 100Mbps.
The total size of the bundle is ~170MB.
Any tricks that can speed it up?

Related

Why is Nativescript on ios so slow?

In my app, I timed the duration it takes to navigate to one particular screen.
In Android simulator about 700 ms and about the same or faster on the device.
In IOS simulator about the same but on the device over 4000ms - 5x slower!
On the device in debug mode but on the release version also super slow.
I'm trying on iPhone 6.
What could cause such a slowdown?
Do I need to optimize the build - config file somewhere.
Maybe the iPhone6 has a processor that needs to be built for - arm???

Xcode uses huge Ram memory (90gb)

Has someone noticed the same problem?
Currently installed version are macOS Catalina 10.15.1, Xcode Version 11.2 beta (11B41) .
While opening project - sometimes indexing takes to long, simulator does not launch, and all system slows down.
In activity monitor process swift appears and very fast - during couple of minutes it shows 73-90gb memory use, after which i have to restart, computer stops responding.
I am having trouble with working in Xcode, any help is much appreciated.

Xcode Too Slow to Work

I've been searching this question for quite a while but still none of the solutions work, this time I got the error message, Xcode playgrounds don't work and if I make a regular iOS app project and run it in the simulator it will have the loading screen for around 15 minutes and then gives the error message: The operation couldn't be completed. (Match error -308 - (IPC/might) server died)
I've recently tried using my iPhone to run projects which works. Is there and way to make Xcode work normally.
I am using a Mid-2012 MacBook Pro Non-Retina with 4GB RAM.
I had similar errors (if overly slow apps are an error). Your problem is that one process awaits another and has an expire timeout. The other process takes a large time to load.
you might be able to solve this by adding a substantial amount of ram and moving the simulators to a RAM disk, alternately you might upgrade to an ssd.
realistically your best bet is buying new retina MacBook Pro. Thats how I solved it...

Xcode simulator with react-native takes to long

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.

Terribly slow compiles using Xcode 3.2.5 and 3.2.6

OS X 10.6.7, Xcode 3.2.6 (although 3.2.5 shows the same behavior), Mac Pro - 2 2.4 GHz Quad w/ 8GB of RAM.
We have several of these machines, all but one are running great. A normal clean/build takes about 5-7 minutes. On the "naughty" machine it takes about 30 minutes.
Before starting the build the machine has over 5 GB of RAM free, CPU utilization usage is practically zero. We can't see anything that would be eating up resources.
This is just a pretty simple iOS project (using gcc 4.2) - nothing out of the ordinary. Once we kick off the build the XIBs are compiled quickly. It isn't until we get into the 15th-16th implementation file (.m) that the build process slows to a crawl. At that point we still have tons of RAM available and there is very little CPU usage.
Any recommendations as to how we might track down the issue with this machine?
Thanks!
Are you building with the release or the debug configuration? Stripping binaries (release configuration) can be pretty time consuming during build times.

Resources