I am facing this crash. Has anyone faced something similar?
This occurs when there is a load more view which is in swift ui is loaded in a table view.
Related
I am getting random crashes while pushing to another view controller.
It was too difficult to find out such a crash, we spent the almost 2-3 days to solve this issue. seems like the crash was due to the one extra view outlet got connected to the main view in the storyboard. Which created the nil reference for some objects of the view controller and applications crashes.
But something surprising to us that how Xcode allowing me to connect the two outlets to the main view. I have again tried connecting the same but this time it is not allowing me to connect. Attaching the screenshot for the same.
Any kind of help/explanation is appreciated.
Please add crash logs. We should check them. Theres any data moving between two ViewControllers
It is problem with Xcode sometimes while editing the outlets.Find the controller on which app crashes and reconnect the outlets and run again.I don't know the exact reason but that solve my problem.
I've developed a social media app.
After iOS 9 launched, I've got a message
BSXPCMessage received error for message: Connection interrupted
XPC connection interrupted
Terminating since there is no system app.
and the simulator reboots by itself. and a real iPhone too.
when I touched UITextView on UIToolbar in CommentViewController. it's like text input UI of Message App, the base iOS app.
SIGKILL always occurs at any of lines in textViewDidBeginEditing: of UITextView's delegate methods, but not happen in textViewShouldBeginEditing:
But still works well in iOS 8.
THChatInput, SlackTextViewController, JSQMessagesViewController
, etc, I used many libraries, but all of those show me same crash.
I've already read a few of articles about this bug here, but their problem were caused by using CoreImage. unfortunately, I don't use anything about CoreImage
I appreciate in advance for helping me. Thank you.
I've found what causes this problem.
I've used a library called 'SWRevealViewController' for drawer menu in my project.
this is a wrapper class of view controller, so it includes some of view controllers and make a hierarchy.
In previous iOS9, it doesn't cause any problem.
In iOS9, its hierarchy of view controllers cause a problem, when popping up keyboard. it doesn't appear in other ordinary iOS9 project.
I don't say that some library I use have bugs, but some problems may be occured in iOS9.
I have been working on this app for months now and from as far back as I can remember I have never had an issue with segues. The code is unchanged in terms of calling performSegueWithIdentifier but since my recent update to Xcode 7 and iOS 9 I have not been able to tack this issue.
I have tried:
Deleting button and creating new button w/ segue link
Using a direct segue from button to view, without the use of performSegueWithIdentifier
Connecting button to new blank viewController
When I press the button, no initial load functions are called on the destination VC (Ex: ViewDidLoad, ViewWillAppear, etc). When I connect it to a blank view, the segue works fine with the same code in place.
Since the code never stops, or breaks, and just seems to "freeze" in place while still running on Xcode I can't seem to even narrow this down to whats causing the issue. I have a similar segue that is also called from another button on the same ViewController that has no issues whatsoever.
Any thoughts on the matter are greatly appreciated!
EDIT: I have narrowed the issue down to the UITextView's causing the problem. Once the Text Views were removed the page loads fine via segue. I wonder what changed between iOS 8 and iOS 9 in terms of UITextView as I will have to remove the text views and completely re add new text views.
So basically the segue was freezing because of the UITextView's I was using in the destinationViewController. The following fixed the issue:
Delete all UITextView's
Add new UITextView's
you must leave the default lorem imposed text and change this programmatically in the viewDidLoad()
This was the fix for me, and from the research I have done on the issue it seems this is a bug in iOS 9 and Xcode 7.
Cheers!
NOTE: Removing the text in the UITextView (or making it longer then ~12 characters) is sufficient to work around it, no need to delete and recreate them. This is fixed in Xcode 7.1.1 and later.
I ran into the same issue and the fixes in this post (Xcode 7 crash: [NSLocalizableString length] 30000) solved the issue for me.
The first is to enable a localisation other than the base for the storyboard (see https://stackoverflow.com/a/32688815/3718974)
The second is to turn off the base localisation (see https://stackoverflow.com/a/32719247/3718974)
I think I have the same problem: I have a UITabelView with cells created from a nib file, when a user tap a cell this method is called:
and when I have the following method prepareForSegue:: the application crashes:
if I delete the line 129 Everything is ok , the method prepareForSegue:: open the right view and the label contactName is shown with its default text.
If I modify the method as follows prepareForSegue:: get exactly what you expect, without having any type of error:
let me know if you also get the same result
Any one who is facing this issue, i solved it by turning off the "Optimize rendering for windows scale" option in Debug of simulator window. I already had tried all of the above answers but could not solve the issue.
In the method in the first viewController where you activate the segue, do you have beginIgnoringInteractionEvents anywhere? If so the screen you segue to will be frozen and will ignore interaction events like you describe. If this is the case you can fix this by adding an endIgnoringInteractionEvents method before your segue method:
UIApplication.sharedApplication().endIgnoringInteractionEvents()
self.performSegueWithIdentifier("editItemToMyGearSegue", sender: self)
I realize this is an old topic, but appears to be still relevant. I was facing the same problem in Xcode 9, iOS11. My UITextViews are embedded inside UITableViewCells. Same symptoms as described here. The tricks with default text and placeholders did nothing for me, but I solved it by turning off the scrolling indicators for the text view in the xib. They were on by default, I guess, though unused.
Edit: this is probably an important detail... the views that were hanging all had an image NSTextAttachment in the attributed string of the text view. I think the image was wider than the available table cell content. With scrolling turned off, they appear to downscale.
I have a UIViewController subclass called FLProfileViewController that contains a UICollectionView. The view of FLProfileViewController is added as a subview to another UIViewController's view. The problem is that the UICollectionView doesn't render.... only if I execute the code from XCode 5 (final release). Even when running the same project from XCode 5 DP 6, the UICollectionView is rendered.
What is more, another instance of the same class is actually rendered when adding its view to a different UIViewController of the project.
Debugging the code, I see that numberOfSectionsInCollectionView: is called and returns 1, collectionView:numberOfItemsInSection: is called and returns 47.
But collectionView:cellForItemAtIndexPath: and collectionView:layout:sizeForItemAtIndexPath: are not being called.
Has anyone find a similar problem? Any ideas about what could be going on?
I have found the problem.
My UICollectionView is shown in the first screen of the app. To avoid showing it empty I have a fake app splash screen that extends the default one. The fake splash is shown with presentViewController:animated:completion: and doesn't disappear until I receive the data from the server.
The problem seems to be that with the final released version of the iOS7 SDK, the UICollectionView is not rendered if it is not visible to the user. In my case I was rendering the UICollectionView while the fake splash screen was still on top.
As I said, my solution worked in iOS6, and the iOS7 version shipped with XCode 5 DP 6.
Anyway, this might help someone else.
I am using forge.setTitle to dynamically change the text of my topbar when my backbone.js application switches views.
Sometimes, doing so causes the Android app to reset on 4.1 Jellybean. I see the trigger.io splash screen again and my app returns to the default view. I am having trouble pinpointing why.
In backbone.js terms, I am calling this function in my Show block for the given view.
forge.topbar.setTitle("My new view");
It seems to work 'sometimes' which suggests a race condition but I am at a loss as to what could be conflicting.
Has anyone experienced this problem?
I should add that the setTitle function throws its success callback, so no error is detected there.