I am developing a TvOS app and having issue with interface builder, when I drag objects like Buttons, labels, segments and etc... the current view show me nothing!!! only a blank rectangle that shows position and area of that object
When I run the application objects will be shown fine!
What is wrong with the interface builder?
Xcode Version 7.1 (7B91b),
OS X version: 10.11.1 (15B42)
At the top of that screenshot there is an error.
"An internal error occurred. Editing functionality may be limited"
Solution :
I had transferred all my files via Transfer Assistant form old mac to the new one , so I think this might cause the problem ! the final solution was I created admin new account and the problem is gone ! Unfortunately updating to Xcode 7.1.1 did not any help !
If you face with the same problem be careful backup all data from your current user account.
I get this a lot. I usually just quit out of Xcode and open it again and it will work most of the time.
Just update the Xcode to "7.1.1 (7B1005)", I hope this will solve your problem
I tried to put the buttons on the storyboard its working fine
Related
I am trying to make a WidgetKit widget for macOS Big Sur. The widget itself works -- the same code on both the Mac and iOS. The issue is that on the Mac the intent (settings) does not work. When I click "Edit Widget" the options I defined do not appear. When I press "Done," it's replaced with a screen that says "Unable to load."
This seems to happen with a brand new target and just a simple new text parameter. These are the steps I took:
Create a new Mac project
Add a new Widget target
Change the generated Intent, adding a parameter. You also need to add a "Siri Dialog Prompt"
Click "Run"
Click "Info" in the Widget Simulator
Click "Configure Intent"
Am I missing something or is this a bug?
This has been an issue since at least Big Sur beta 5 and Xcode 12b6. I opened a ticket with Apple, but I'm also asking here as it seems that some people have it working and it's entirely possible that I'm missing something!
This seems to be a bug of the Widget Simulator. When I run the same Widget in the Widget panel of Big Sur, I see all configuration options.
The problem turned out to be an older copy of the app on my disk and macOS getting confused and looking in the wrong place.
I'm adding a Widget to an existing app that doesn't currently have one. I have the current, App Store version in /Applications. I've been running the updated version from Xcode or exporting it to my desktop and running it from there. The Widget itself -- as noted in the question -- runs just fine. But it seems that when looking for the Intent used for the configuration, it prefers to look in /Application rather than the Xcode version. As soon as I deleted the original app, the widget and its settings immediately started working.
Thanks to Ely for pointing me to this blog which didn't give the answer but pointing me in the right direction.
I updated to Xcode 10.1 today, and noticed that when trying to utilize the User Interface Inspector that it continuously loads. I utilize this feature a lot to check how constraints are behaving. Was wondering if anyone else had the same issue?
Steps that I have taken to try and resolve it:
Reset all simulator data
Cleared all derived data
Cleaned build
Tried multiple simulators with the same issue
Just had the same issue. Creating a new simulator on the latest iOS that came with Xcode fixed it for me.
I develop mainly IOS apps but, recently, I worked on an OSX app. Both are possible with Xcode (I use 8, with swift).
Unfortunately, when I switched back to my already-existing IOS project (after restarting Xcode), the storyboard selection menu for the object library shows only OSX objects, not IOS (e.g. UIImageView).
I have googled without success and tried restarting Xcode, also without success. Can anyone help me fix this?
I did a lot more searching and came up with:
Xcode is loading in OS X objects instead of iOS objects
There there are other solutions proposed but the one that worked for me was to close the assistant editor and then, in the file list ( leftmost window in Xcode 8), I double clicked on the storyboard file. Problem solved. I am surprised that this bug still exists in this latest version...it is very troublesome.
I am trying to create a Table View Controller in my storyboard and when I change from "Dynamic Prototypes" to "Static Cells" Xcode stops responding until it eventually crashes.
What I tried so far:
Re-installing Xcode;
Clear Xcode folders under ~/Library (including DerivedData);
Creating in a new project (still crashes);
Ask a colleague to create a Table View Controller with static cells in the same project. He can do it on his computer. I can see the Table View on my computer and even edit rows, but I cannot add sections.
Tried both Swift/Obj-C projects, with or without Core Data;
I am using XCode 6.1.1 (6A2008a), the same as my colleague.
Please help! Thanks!
Yes , I have faced similar problem .please try with Xcode 6.3.x or later version .
Not a fix but may help some. I noticed this was only happening to me when I had two windows of my current project open. Was reworking a storyboard, so I had the old and new side by side. When I closed the windows of my project that I was not currently editing, Xcode did not crash. With more than one window open, editing a Static Table View would crash Xcode EVERY time.
I found a temp Fix. I also noticed that my dock isn't working fine (I can drag and drop things into it or in it). So I rebooted the mac and this fixed the dock problem, I tried quickly in Xcode and it worked. I guess it's something with Mac OS not just Xcode
I just loaded Xcode 6 GM seed. Now I want to submit an update of my app.
Archiving works so far. But when I click "Submit", as soon as the upload loading bar appears Xcode crashes.
Do I need Yosemite?
I had to download the Application Loader from Apple because Xcode could not find it.
Do I need Yosemite?
No. Mine crashed the same way, so i uploaded my app using Xcode 5.1. It worked fine.
The Application Loader seems the only thing that works right now. Had the same problem, while uploading or even just validating.
Just export via Organizer and Upload via Application Loader helped.
I was faced same problem. Now it works fine.
Solution : Just accept new changed terms and condition from apple developer account and resubmit it.
Please Make sure you've accepted all of the new agreements & condition in the Member Center.
To check if you need to, you can go to the preferences -> accounts in XCode, and chose to view details of an account and attempt to refresh button. Here, XCode will warn you that you need to accept new agreements in the Member Center before you can refresh.
or just login to developer account and go to here https://developer.apple.com/membercenter/index.action
I was able to make Xcode work, but I had to go to iTunes connect and start the process there first by going "My Apps" and clicking on the plus sign. Fill in the info and hit save. Then try submitting with Xcode and it should work.
OK. Here's my $0.02.
1) Xcode 6GM crashes every single time for me. I am running 10.9.4. I have no idea how widespread the issue is, but it is 100% repeatable for me. I cannot use Xcode 6 to submit apps for review.
The crash happens during the upload. I have submitted a RADAR report and given crash logs.
2) I was able to submit using the App Loader. Here's how you do that:
2.1) In the Organizer, after you have done the Archive, select the latest archive for submit.
2.2) Instead of "Submit," select "Export."
2.3) Select the first choice (App Store).
2.4) Open the Application Loader.
2.5) Select "Choose."
2.6) Select the .ipa that you just saved in the export.
2.7) That will work. You may get a message teling you that the API file is too big for analysis. I got that for all 9 of the apps I just submitted. In my case, I ignored it.
I think they rewrote the whole application load from scratch, and that Xcode is still buggy as hell.
They had a deadline, and rushed it. It shows.
I expect both the server (Web) component and Xcode to apply patches soon.
In my case, I'm quite annoyed, as I had to rush out a fix for the arbitrary decision they made to change the way that the CLLocationManager works, which broke all my location lookups. The fix is simple, but there will be a period of time when I receive hate mail from the users that upgrade to iOS 8, and the app stops working.
Joy.
I just installed the official version from the App Store and now everything works fine.
I had the same problem. When XCode crashes during export or submit it means that you have non-valid certificate or provision profile in build settings.
Here is the solution:
Accept new changed terms and condition from apple developer account. (Just like Sandeep said)
Go to here to generate new provision profiles, for App Store & AdHoc (Tutorial)
Double click new provision profiles you downloaded to install them, and then XCode will never crash.
The problem is caused by XCode 6.0 does not handle provision profile migration properly. Developers should regenerate provision profiles for XCode 6+, but Xcode 6.0 fails to display this error message properly and crashes. (If you use XCode 6.1 Beta, it will display error messages for you, no crash. Then you will know that the problem is caused by "invalid"=="legacy" provision profile.)
After that, you can submit app and export Ad Hoc distribution for Testflight.