Recently I was interested in screensavers. And while I was looking for a way to write it, I found that it was supported by Xcode.
ref: https://whichline.wordpress.com/2015/07/13/os-x-screensaver-swift-2-part-1/
But my Xcode 9 does not seem to support screensaver project.
There are no way to write screensaver on Xcode 9?
Screen saver is listed for me on Xcode 9.2, in the "Other" section:
Related
WARNING ITMS-90901: "Missing full-screen support for the latest iPad mini display. The “ExpoKitApp.app” bundle includes UIRequiresFullScreen=YES in the Info.plist or supports only a subset of UISupportedInterfaceOrientations, and is built with the 14.1 SDK. To take advantage of the full screen size, recompile with Xcode 13 and the SDK for iPadOS 15 or later."
We have two options here
UIRequiresFullScreen=YES to your app’s Info.plist in order to keep your app full screen during multitasking, you’ll need to recompile with Xcode 13 and the SDK for iPadOS 15
Don’t include this key in your Info.plist file if your app supports iPad multitasking and is capable of running alongside other apps. If this key is absent, or is present and set to NO, the system lets your app share the screen with other apps. Can work with Xcode 12.
You've to recompile your code in XCode 13+
and for further details please visit Apple's News and Update
i had the same issue, i sorted by upgrading to latest expo sdk and including this in the app.json expo.ios.infoPlist {"UIRequiresFullScreen": true}
I was completely upgrading my macOS(12.2) and Xcode. Currently, no warning message showing.
As the message says, recompile with Xcode 13.
I am using Xcode 12.5, and I am trying to paste some text from a file into my ios Simulator (iPhone 11 ios 14.5). This does not work. Any thoughts or ideas on how to fix this?
I have looked at a number of other posts but they all seem outdated and don't work for me.
Also I am using an Apple M1 Mac mini ...if that makes a difference. I am also building my application with Xamarin.
The steps I took:
I turn of Automatically Sync Pasteboard
Copy the text (which is just letters from a .txt file)
Click send pasteboard from the edit menu.
Click on my Editor control and select paste
The outcome is that it shows the bubble at the top saying myappName pasted from CoreSimulatorBridge. However, it doesn't actually paste the text.
I answered this elsewhere, but it took so long to find I am repasting a couple places I looked first. Essentially, with Apple M1 Silicon, iOS 14+ pasting doesn't work. Switching to a simulator running 13.7 or earlier fixed it.
it seems it was an issue that Apple fixed in the latest XCode updates, copy/paste works with me on a simulator with IOS 16.2 and XCode 14.2
Now with XCode 14 I'm not being able to build 13.7 or earlier.
We have tried both iOS 14 and 13. In both cases, the storyboard screens show up like this.
Has anyone else faced this issue and was able to solve it? Or should we revert back to xcode 11 or 10 in order to solve this?
Empty storyboard screens
I have similar issue with Xcode 12.4 on M1 Macbook Pro. As a workaround disable Rosetta Mode when working with storyboard. Follow the below steps
Quit Xcode and open finder and go to Applications folder
Right click on Xcode App and select Get Info
Uncheck "Open using Rosetta" option
Open Xcode, storyboard will work now
Note: With Rosetta Disabled, I wasn't able to build/run the app. So I was toggling the Rosetta mode. I think Apple will fix it sooner.
UPDATE
Xcode 12.5+ fixed this issue.
I tried on Xcode 12.5 beta on my M1 pro is work well. That's Xcode issue with 12.4 on M1.
Selected a device from the list in Device in Xcode fixed it for me:
Tap Device:
Then select a device:
Edit: Probable Bug. Seeking fix or workaround…
How can I get the system’s text styles to be available in the interface builder when using Xcode 11?
I just started using Xcode 11 this week. In the interface builder (storyboard mode), when I go to assign a dynamic type text style to a Label or Button, using the Font -> Style pop-up, all the text styles are missing from the popup menu.
I do have the Dynamic Type “Automatically Adjusts Font” checkbox checked, as well.
I’m not sure if this is a bug, an intentional change I can’t find documentation for, or something else.
The expected behaviour is described in Apple’s developer documentation “Scaling Fonts Automatically”. Specifically, in the “Configuring Text Styles Using Interface Builder” section.
Further exploration: I’ve tried it with new projects, old projects (from Xcode 10), projects targeting iOS 12.2 and 13.1. All had the same problem of no text styles in the popup menu.
I experience the same problem when upgrading from Xcode 11.0 to Xcode 11.1 or 11.2 beta 2:
Xcode 11.0:
Xcode 11.1:
I also filed a bug report (FB7415999) with Apple and also opened an issue with them.
**My curren solution at the moment is a downgrade to Xcode 11.0 for UI development and a parallel install of Xcode 11.2 beta for on device runs **
This is probably a bug in Xcode 11.1. I ran into the same thing and filed a bug with Apple (FB7368959). A colleague running Xcode 11.1 on Catalina did not have the same problem, nor did another running Xcode 11.1 on Mojave.
Here is a workaround that got me back on track: I opened the problematic project in both Xcode 10.3 and 11.2 beta. In both, the dynamic type styles were available in IB. I didn't change anything, but reverted to Xcode 11.1, and now the styles are there, too. Hopefully this works for Grant and anyone else that runs into this annoyance.
Edit Mar. 17, 2020: This problem has reoccurred for me on Xcode 11.3.1. It seemed to happen with a specific project, and the problem spread to a second machine as soon as I opened that project. My workaround didn't help when I opened the project in 11.4 beta 3.
I've encountered strange issue. My app running on simulator shows only English/Emoji layout for UITextField.
BUT! The spotlight shows English/Russian/Emoji, and it's correct.
I use Xcode 6.1 and iPhone 4s iOS 8 simulator.
What's wrong?
Dupe of iOS8.1 Simulator always uses US keyboard layout despite german hardware keyboard
As mentioned there, this is a known issue and is mentioned in the Xcode 6.1 release notes.