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.
Related
There are a few part to this problem:
Running my intents extension scheme on the "Watch App" works fine. I can track the progress in the debugger, great.
But when I run the ap on my apple watch––simulator or real device, and not through xcode––I can't use my voice shortcuts. I get the message "sorry, there was a problem with the app" every time
The shortcuts work on iPhone all the time. Any iPhone, any build, from anywhere
Because this only happens while not debugging, it's very difficult to troubleshoot the issue
So unfortunately this is a pretty broad question: does anyone have any suspicions as to why this is? Any resources to help me troubleshoot this? I've been playing around with it for a LONG time without much success.
I've already tried a few things: switching up the schemes, iOS and watchOS versions, debug/release builds, etc. I'm beginning to think there's actually an issue with my code––my suspicion is that the shortcut is timing out––yet all the optimizations that I've made haven't amounted to any good results.
To give some background on my dev environment, I'm using Swift 4.2 and Xcode 10.1 on a Macbook running the latest version of Mojave. My test devices include a 40mm series 4 watch with watchOS 5.0 and an iPhone X running iOS 12.0.
Then there's the simulators. I've tried every version of iOS 12.* and watch 5.*
EDIT: Also, to clarify, this error occurs in the confirmation phase of my shortcut, not the handle phase.
I had Xcode v6.0 - v6.1 . I'm not sure which one. What I can remember is, it does not support iOS 8.2
The problem is that my team and I release a game app for beta testing ( test flight pre-release , on iTunes connect ) . Every user that got iOS 8.2 crashes at the very beginning when they open up this game app.
After, I upgrade my Xcode to v6.2 which support iOS 8.2. It solve the problem. But still my team and I are not 100% sure if this will solve the problem long term.
My game app framework:
- Cocos2d-x v2.2.6
My question is that:
1.) Is Xcode version the reason it crashes at the first place?
2.) If so, do I need to update my app and my Xcode every time Apple releases new version of iOS?
Thankyou. :)
You need to investigate exactly what is happening, for example by connecting a device running 8.2 to a development machine and debugging. It is most likely that you have some bug in your code that can strike at any time due to random differences of the environment; for example uninitialised memory will have random values that can be different depending on the OS and will sometimes crash and sometimes not. It is quite possible to have a bug that has nothing to do with OS or Xcode version at all that behaves like this. And that bug can reappear at any time.
Correctly written code will work on all future OS versions without problems. With emphasis on "correctly written".
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
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)
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.