I have created a location based app, and it works fine on the device. But on the simulator there appears to be sporadic issues where the location services just stops working. Everyday for the past few days, I have worked on the app using the simulator without issues, however when I come back into work the next day and start the app again, I am getting the usual error
didFailWithError: Error Domain=kCLErrorDomain Code=0 "The operation couldn’t be completed. (kCLErrorDomain error 0.)"
This happens to every location app I have, I have a few custom code examples I have I use for reference to check the issue is not just happening to my application. So this confirms that it is not a coding issue
Usually I can fix the issue, after a few attempts of resetting simulator, deleting derived data, double checking I have setup a simulated location under edit scheme. It usually takes a few attempts of trying this various techniques to get it working. But today I cannot get it working at all on the simulator.
Now I am sure after playing about with for longer, I will eventually get this working again on the simulator, but I would like to know the root cause of this issue. I am getting tired of every morning, repeating this routine of resetting sim, deleting data, as it is wasting time that could be spent actually coding.
Is this an issue with the Xcode 6.1 simulator? Why does this seem to happen quite often and does anyone else have a better solution to this issue?
I have filed a bug report with Apple as suggested by Jeremy Huddleston Sequoia. However for the time being, if anyone else has this issue, the only work around I have found to truly fix this is, first reset the simulator, secondly delete the derived data folder, then finally reset the mac. It is frustrating, but every day this week I have had this issue, and for the time being, this is the only solution I have found that seems to work, well sometimes. Hope this helps if anyone else is having this problem. If Apple respond to my error report, I will update my answer
it happens often to me and use xCode 6.1.
Usually Cmd + Shift + K, which is about the equivalent of resetting the simulator , I can make it work.
Other times , change device , launch the iPhone 5 on the simulator and on the iPhone 6 and then I go after ...
Strange thing ... I agree with you that it may be some sort of bug or poorly procedures initiated by the compiler.
Also because then once part after is always the simulator
Related
My app is using Firebase Analytics and I believe starting in iOS 13.2 started getting the errors described here: Why I get the console warning: [Process] kill() returned unexpected error 1 when I load a WKWebView in iOS13.2?
I guess it wasn't a big deal
Since I planned for my app to go live in January, I began bigger tests in physical devices. I noticed after a while the app started to behave erratically, specially after receiving a [general] Connection to daemon was invalidated error. This doesn't occur in the simulator
Searching the internet I found a post that describes the same problem: https://forums.developer.apple.com/thread/124306
In my case, only Firebase seems to be calling WKWebView, but every time I open the UIMenuController I get the error described in the console and the app appears to be missing inputs. This is specially troublesome with UIScrollViews, which my app uses a lot. The pinch gesture seems to work at will. On an iPhone 6s, the issue isn't as noticeable, on an iPad, it's like a 50% chance the pinch gesture will work properly
Outside of removing Firebase, is there a way to mitigate this issue?
1 June 2020: The console message still persists, however, I have seemed to resolve the UIScrollView issue by deactivating delaysContentTouches, now the pinch gesture seems to work most of the time
23 October 2020 If anyone notices their app starting to behave erratically with no apparent reason I HIGHLY suggest to test it on an iOS 13 physical device if possible. Seems that Apple removed the warning from iOS 14, but testing it on iOS 13 you can pin point the exact reason after the warning appears in the console
Upon further testing, I've reduced the view down to a dead-simple UI view with a single SwiftUI TextField and the 'Connection to daemon was invalidated' still appears after I type the first character into the field. Soon thereafter the app crashes with a sigAbort. (So I don't think the reason is the UITextView wrapper I was using in the previous post). Once the invalidated message appears the app is doomed to crash, not right away but soon thereafter.
I have no idea what causes the 'invalidate' message and a Google search seems to imply that no-one else does either. Some folks appear to have made (experimental?) changes to their UI that stops the message but it appears to be impossible to determine a definite cause. (and like before it only occurs on a real phone)
Same issue without using Firebase at all. What I did: Delete build folder and compile again. Issue does not appears again.
On Xcode:
Clean the Build Folder
This will delete all of the products and intermediate files in the build folder. To clean the build folder you can use the shortcut Command+Option+Shift+K or Menu Bar → Product → Hold Option Key → Clean build Folder.
On Flutter:
Just delete build folder.
I have searched around and have not found the particular answer that I am seeking for. I just went and updated my App to a Swift 3 Language from swift 2. It obviously threw out a host of errors which I went through and fixed to the best of my abilities and now I do not have any errors. I can run the app but I cant tell if anything else is working because the Login or Auth sections of the app are not working. I know that I can just bypass to test but I have been working on it a lot and trying to get this feature to work that worked well before the language was changed..
Very simple my question is this:
I upgraded to Swift 3. Do I need to upgrade the cocoa pods to support the change in language? If not is it just an issue with the way that my code is and because of the change to swift 3 that i need to keep tinkering with?
Thanks for any help
sorry posted that about 12 hours to early. After doing a lot of research it looks like I found the answer. have not tested yet but I think I am getting the same errors in the compiler.
"We've noticed what seems to be an issue with the latest iOS 10 simulators (up to beta 6 at the time of this writing) that causes Firebase Auth to throw an error due it to not being able to write values to the keychain. This issue does not affect real devices." This is from a Firebase Blog
Hello I got this problem on the device and not on simulator, my device is iOS 9.3.3 and the strange thing is that when run from xcode it works just fine
But when I open from device after stopping debug from xcode, the error will occur
And after some digging, I found out that if pod is only using firebase, it connect just fine even opening from the device
But if I add just 1 pod, it will error like above, so I don't really understand what is going on
And yes already try using keychain sharing
Any tips?
Edit: it works fine on other devices running iOS 8.1
I've encountered a problem that has completely stumped me, and unfortunately I don't really know how to go about trying to diagnose the problem either.
Basically I have a client who's website loads and then just hangs using FF25 on OSX 10.9, it only happens on this website, no other website. I've heard of problems before with this combination that resulted in people having to disable their plugins, so I told them to disable plugins/clear cache and get back to me. They've done this but to no avail. I've also read that it may be a CSS issue with fonts(no idea why it would be).
I've been all over the Mozilla forums but no one has raised such a query that replicated my problem on just a single website. Here probably isn't the best place to raise such an issue, but I'm sure someone must of encountered the same problem and resolved it some way or another.
Thanks.
There are memory allocation issues that appeared in FF25 (certainly on Windows; FF26 and 27 seem much "better"). These issues seem to be js/heap related. See, for example, https://bugzilla.mozilla.org/show_bug.cgi?id=936784
You can investigate yourself how the browser is using memory by browsing to about:memory in a new tab.
It seems a little odd that this does not happen if the browser console is open - and even after closing the browser console and refreshing the page it continues to load fine.
What might be happening (or not happening) with the console open which would prevent this error from happening?
We've tested it on 10.7, 10.8 and 10.9 and all three have this problem, but only on Firefox 25.
In response to Codacoder, that bug appears to be related to leaving Firefox unattended and an ongoing incremental memory usage issue - this happens the second the page loads, rendering the browser un-usable and requiring a manual kill of the browser. Not sure if it's the same issue?
Ruth
By some mysterious reasons I got myself a jailbroken iPhone 3GS from a vendor whom I am finding difficult to track.
My task is to test out in app purchase functionality on it.
Currently it has iOS 5.0.1 with cydia installed.
No, it does not have Appsync.
I am installing my build through testflightapp API which works without issues with my app so far.
However when I initiate in app purchase, I don't get anything in response.products so far.
I have added productIDs and all in itunes-connect already, checked twice that they are fine, since 48 hours.
I tried testing with iPhone simulator 5.1, but all I got was no values from storekit. I would love to hear if there is any workaround with simulator.
Worked around this finally - deleted my app from itunes connect, re-added it.
It complained about name being already used.
I changed the language of name. And it worked.
Maybe, my prior app setup was right, but I had something else messed up.
In between, I rejected my app. That maybe one of the reason behind this issue.
Lesson?
Don't developer reject your app.
Symptoms: Running any iOS 5.1 application from Xcode 4.4 (and 4.4.1) will launch the iPhone simulator but result in a plain black screen. In the Xcode console, the message "error: Failed to attach process to id " is displayed, being different each time. Attempting to 'Stop' the application from Xcode does nothing, and only Force Quit will return Xcode to a working state. Pressing the 'Home' button on the simulator shows that the app was successfully installed. Sometimes, opening the app from the simulator will show the UI, but no console messages are displayed, even after manually performing 'Product->Attach to process.'
Attempted Solutions: Xcode 4.3.x was originally installed on Lion, working charmingly. The problem started at installation of Xcode 4.4 in early August, for a project which was working before. I upgraded to Mountain Lion, didn't help. I reinstalled Xcode, didn't help. I upgraded to 4.4.1 Aug 7, didn't help. I deleted all trace of Xcode data, running: find / -name '[xX]code' and deleting all super-folders where it seemed relevant. That (not surprisingly) caused some OS issues, since subsequently reinstalling Xcode just didn't work. I then did it again, reinstalled Mountain Lion (to restore some OS files I probably killed), then reinstalled Xcode 4.4.1.
For projects, I typically ran new, single-view projects each time. Lately I've tried using this sample project from Apple, per link 3 below. I tried all the clean builds, etc., but honestly, one would assume opening a fresh project should just work. Just for kicks, I put a single 'Label' object in the iPhone storyboard at times.
After doing some homework I managed to find the following questions most similar to mine, but none are exact nor do any of the solutions work (in order of decreasing relevance):
xcode-4-4-ios-5-1-simulator-problems
crash-of-xcode-4-4-for-mac
failed-to-attach-to-process-id-xcode
unit-test-target-doesnt-run-on-xcode-4-5
xcode-4-4-freezing-on-project-close
simulator-keeps-crashing-in-xcode-4-4
Any help would be greatly appreciated. I apologize for the lack of brevity, but I've spent probably 15 hours trying to find/implement solutions to a seemingly trivial problem, and I would rather provide all relevant information than to have you guess at what I did. I'm not going to specify all the build info, just because it's whatever comes stock on the fresh install of Xcode.
I had similar problem (although with different configuration) and found incredibly simple solution by chance. I just used Product->Stop, then Product->Run (through keyboard shortcuts if that matters). Just once! Then the problem disappeared.
configuration: XCode 4.2, iPhone Simulator 5.0
symptom difference: process attaching didn't fail
It seems to me that the problem stems from the XCode-Simulator communication, and that's why I've shared my experience here despite the differences.
EDIT: It comes out Stop; Run didn't provide permanent solution for me. The problem is recurring from time to time. Still it is a temporary workaround for me.
I got this a few times, especially when I kept running my app and cancelling it or interrupting it too often, it's not something you can put your finger on, but yes I always managed to get back up and running by deleting the app in the simulator, cleaning project and build folder, deleting derived data (in Xcode organiser > projects view), restarting simulator and Xcode.
This also happened a few times on the device, and I needed to restart the device, iPhone in my case. I hope these infos help you out.
I got this to work by building and running the simulator using the Xcode 4.5 developer preview. I then closed it out and reopened Xcode 4.4.1 and it built and ran fine.
While none of the solutions above worked for me, thanks for putting this all together. I figured I'd answer here since this was the most comprehensive.
While this isn't exactly a solution, after today's OSX 10.8.1 update from Apple, this issue has been resolved. It's safe to say that some bug arose in the process of installing Mountain Lion and Xcode 4.4 that was fixed with this update to OSX.
I think I've cracked this one for my particular case, and I admit it's somewhat a mistake only newbies should do but I had overrided
viewWillApear:(bool)animated {}
in a ViewController of mine, without calling back
[super viewWillApear:animated]
It might be a good idea to search for all view lifecycle methods in your project and see if you have similar problem.