Xcode 11.3.1 from the mac app store supports the release version of iOS 13.3.At least in terms of being able to build to it.

I worded that poorly.I was able to build and run on my iOS 13.3 iPhone.

Did you try the usual quit xcode and restart it?It might also be worth rebooting your mac.

I wouldn't expect it to be possible without jailbreaking the device since that would be a significant privacy issue if third party apps could access a user's mail.

You can with limits...https://developer.apple.com/support/enrollment/There is a FAQ near the bottom that addresses it.I had the impression that device certificates have to be renewed on something like a weekly basis, but I've not used the free program myself.

I would imagine that you should contact Square to see what is involved and if they support third party software using their hardware.

I'm at work and just checked my home system and I see that limit too.That just means you can't create an app that can't be installed on anything less than iOS 13.3 though.If you need that it is of course a problem, but it does support running and debugging on iOS 13.3 devices.I am able to select and run my app on an iOS 13.3 simulator as well.

In my mind a ram disk would potentially be self defeating in that it takes memory that could be used more directly for processing and uses it through code simulating a disk drive with the overhead of the file system. There should already be caching of disk content to ram in what is likely a more efficient manner.I would expect allowing more parallel operations would, up to a point, increase the overall speed of compiling.Utimately the speed matters only to the extent it matters for you. If you are having to sit and wait the extra time then that can matter since time is money after all.

Where are you setting the frame?We have an issue with a client's app that on the iPad the screen size information isn't valid until view did appear.

Not Apple documentation, but developer.mozilla.org/en-US/docs/Web/CSS/text-size-adjust does discuss this functionality.

It seems unlikely since that seems to be a selling point for Apple.https://support.apple.com/en-us/HT210425

My reading of the documentation suggests you won't be able to know.Even if it is enabled, a low power state might cause it to not happen.

In my mind, not stopping at breakpoints makes sense.The app you are testing it with was built in release mode and wouldn't support debugging.I could also see that creating a potential security issue allowing debugging in that situation.You might be able to use the system logging to help understand what is going on.There is information on viewing the logs atapple.stackexchange.com/questions/165100/how-to-read-iphone-system-logsDocumentation on logging is athttps://developer.apple.com/documentation/os/logging

There is a suggestion of it being needed to use the system player at least...https://developer.apple.com/documentation/mediaplayerEDIT:A possible way to detect the music apphttps://stackoverflow.com/questions/41545283/how-to-check-app-is-installed-or-not-in-phone

Have you tried unpairing and repairing?https://forums.developer.apple.com/thread/99094