No developer settings in iOS 9? - ios

Yesterday I was studying iOS development. I had just updated my Xcode and was finally able to deploy my apps to my iPhone. However, all of a sudden, my iPhone got a weird bug where it wasn't working at all. I restarted it, only to find that the developer section in settings was gone. I thought it might be some bugs from the beta version I was using, and decided to finally do the update (I had my memory all used up, so I didn't do it sooner in order to not delete anything). I thought that would fix my issue, and at least give my iPhone developer rights again. But it didn't. I've been searching for ways to do it since last night and I am unable to find anything recent, as they are all for older versions of iOS or Xcode. I tried them, but either they just don't work, or the path they use is now not existent.
Any ideas what that could be and how I could fix it?

Related

WatchKit Simulator periodically gets stuck on load Spinner

I'm experiencing a similar issue as was posted previously in:
WatchKit Simulator Won't Load App
My WatchApp seems to be loading okay (I'm watching step by step w/ NSLog), but the spinner (sometimes) never stops and the Watch interface (sometimes) never appears in the Simulator, i.e.:
I've tried some of the workarounds posted at the above URL (and I apologize for not being able to directly add my comments there) and they seem to work some of the time.
But I'm looking for confirmation that this is a bug in the XCode 6.4 Simulator code or perhaps an incompatibility with my older hardware? (I'm running latest version Yosemite & XCode but on an older mid 2009 Macbook Pro).
It just seems un-Apple like for a development environment to be this buggy. I keep thinking it's gotta be my code and not Apple's XCode Simulator?
Anyone else still encountering these kind of "spinner and not displaying Watch screen" in the Simulator?
Thank you for any input, the previously suggested workarounds seem to help some of the time but having to go thru that many steps with each compile & run cycle is making rapid iterative Watch development in the Simulator extremely frustrating.

Designing existing app with IB has no effect on device (iOS 7.1 / XCode 5.1)

I have encountered quite a strange bug a few days ago. It turns out that any changes in Interface Builder don't affect actual design anymore when the app is being tested on the device.
Practically it means, that you can go as far, as completely remove all view controllers in Storyboard, but with no effect on the device — the application will look the same. No changes at all.
At the same time, IB still works normally if you run the app in the simulator. New projects also work fine, as well as my other existing apps. So the problem seems specific for this particular project and not easily reproducible.
If anyone has faced with a similar bug or knows its probable reason, please let me know. Any advice will be of great help. Thank you!
p.s. I have installed XCode 5.1 and upgraded my device (iPad 2) to iOS 7.1 just a day or two days before the problem initially occurred. An upgrade might cause the bug, but I haven't seen similar complaints on the web yet.
p.p.s Unfortunately, I had no chance to test this bug on iOS 6.x or <7.1 devices, but I will do it as soon, as I'll get access to one of these devices.
This is a bug in XCode.
Any changes that wont reflect at runtime, not even doing a Clean Build or even removing the app from the simulator or device.
Fix: rename storyboard to the old name (MainStoryBoard) and suddenly all changes were reflected.
see here

Why is newsstand my only app in IOS simulator?

At one point I had to do a timemachine recovery of everything on my iMac. Ever since then, when I open my IOS simulator, the only app it shows is Newsstand. I have upgraded to the most recent versions of xcode (4.3.3 (4E3002)) and ios simulator (5.1 (272.21)) and still see the issue. I have also tried removing ~/Library/Application\ Support\iPhone Simulator\ and that makes no difference. Has anyone ever seen this problem? What can I do to get other apps back? I really need to be able to use mobile Safari for some testing.
This happened to me before. I solved the issue by uninstalling xcode and the simulator file, which looks like the same path as yours. I then re-started my computer and re-downloaded xcode and it worked fine...
Good luck.
Just logging out and then logging back in addressed the problem for me.

Got stuck when deploy app on iphone

I got stuck when I try to deploy the test app on my device.
When I click run on XCode, the device is going to run the application. However, it stuck in the first view. And nothing is moving.
I was wondering if there is something wrong. Is it caused by jailbreak? My ios version is 5.0.1.
Then someone tell me what I could do to solve it.
There are some strange launch issues when debugging with LLDB.
Try using GDB instead
(EDIT) Latest Xcode 4.3 update with LLDB-112 should fix a lot of problems (but there are still bugs including reading of ivars)

Developing iOS/Xcode/PhoneGap app; randomly receive SIGABRT

I was developing an app in Xcode and everything was working just fine. I went to shut off my network on my Mac to try and simulate 'No Network' so I could test a setting I had just set using the Phonegap.js.
I suddenly got a SIGABRT notice and can no longer run the app on my iOS simulator. It builds just fine. This has happened to me before under different circumstances.
I have found that all I have to do is paste the same code into a new project and all is well. So it appears to not be a code issue.
I've researched it and found that many people around the web are reporting it but I could not find where anyone successfully fixed it.
That is why I was hoping that someone on StackOverflow might have seen this before and know how to fix it.
I did come across a suggestion to remove a line our of your plist info file but that was for an iPad target and I am targetting the iPhone (but I still tried it and it didn't work either way).
XCODE 4.2, PhoneGap 1.3.0, iPhone 5.0
I am about 99% convinced that it has to do with a bug in XCode and ARC.

Resources