I am trying to refresh a Footer ( supplementaryElement). I am using the invalidatelayout method. Based on SO suggestions here. Apple documentation here.
I am getting the following error:
Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'the invalidation context
() sent to
-[UICollectionViewFlowLayout invalidateLayoutWithContext:] is not an instance of type UICollectionViewFlowLayoutInvalidationContext or a
subclass'
Implemented Code:
let footer_context = UICollectionViewLayoutInvalidationContext()
footer_context.invalidateSupplementaryElements(ofKind: "ActivitiesSelectMembersFooterView", at: [indexPath])
self.collectionView?.collectionViewLayout.invalidateLayout(with: footer_context)
Looks like invalidateLayout method is expecting UICollectionViewFlowLayoutInvalidationContext instead of UICollectionViewLayoutInvalidationContext.
I am using Xcode 8 and Swift 3.
My Storyboard in Xcode is here -
"Next" is the Footer that has the custom class "ActivitiesSelectMembersFooterView"
The error message accurately describes the problem. When calling invalidateLayout(with:) on a UICollectionViewFlowLayout object, you need to pass an instance of UICollectionViewFlowLayoutInvalidationContext.
Change this line:
let footer_context = UICollectionViewLayoutInvalidationContext()
To this:
let footer_context = UICollectionViewFlowLayoutInvalidationContext()
Related
I've created a XIB containing only a UITableView. I changed the parameters of the project to load this view at launch. But I get this "unrecognized selector sent to instance" error I don't know what it is. How do I fix this and get my app to show my view ?
I've searched the web and it seems that might come from Objective-C libraries ?
EDIT
I did some testing, it's look like it crashes when I link my TableView with my IBOutlet in the ViewController. Am I doing something wrong with the type TableView ?
The viewcontroller :
class Liste: UIViewController {
#IBOutlet weak var maListe: UITableView!
override func viewDidLoad() {
super.viewDidLoad()
}
}
The error stack :
2019-06-12 14:06:11.083905+0200 GuildWar[5905:8796162]
-[GuildWar.Liste _finishDecodingLayoutGuideConnections:]: unrecognized selector sent to instance 0x104f0ef40 2019-06-12 14:06:17.511280+0200
GuildWar[5905:8796162] * Terminating app due to uncaught exception
'NSInvalidArgumentException', reason: '-[GuildWar.Liste
_finishDecodingLayoutGuideConnections:]: unrecognized selector sent to instance 0x104f0ef40'
* First throw call stack: (0x21230f518 0x2114ea9f8 0x21222c278 0x23e4c2ef8 0x212314d60 0x2123169fc 0x23e874110 0x21c955f28
0x21c8f5304 0x212cdba4c 0x21c955f28 0x21c95616c 0x21c8f5304
0x23e151dcc 0x23e152958 0x23e4971e4 0x23e4977c0 0x23e495e24
0x23dd5a104 0x23dd6269c 0x23dd59d88 0x23dd5a678 0x23dd589c4
0x23dd5868c 0x23dd5d1cc 0x23dd5dfb0 0x23dd5d084 0x23dd61d84
0x23e494518 0x23e090f0c 0x214c89d44 0x214c93754 0x214c92f5c
0x104cbcc74 0x104cc0840 0x214cc40bc 0x214cc3d58 0x214cc4310
0x2122a12bc 0x2122a123c 0x2122a0b24 0x21229ba60 0x21229b354
0x21449b79c 0x23e497b68 0x1045ea10c 0x211d618e0) libc++abi.dylib:
terminating with uncaught exception of type NSException
It looks like, you might have created IBOutlet or IBAction and deleted later in the code. Revisit the connections in the storyboard connection inspectors and check if there is any warning symbol like the attached screenshot, then you need to remove that connection.
Or if you can share your code I can look into.
After migrating to Swift 3, the app crashes on
-[_SwiftValue unsignedIntegerValue]: unrecognized selector sent to instance 0x60800064d5f0
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[_SwiftValue unsignedIntegerValue]: unrecognized selector sent to instance 0x60800064d5f0'
When trying to access vc.view. Here is the relevant code snippet. The code is called from a UIViewController.
guard let vc = storyboard?.instantiateViewController(withIdentifier: "some-viewcontroller-id") else {
return
}
if let vc = vc as? SomeViewController {
let theView: UIView = vc.view
theView.translatesAutoresizingMaskIntoConstraints = false
}
If I stop on breakpoint before calling let theView: UIView = vc.view and po vc.view in the debug window, I get the same error in the debug window.
-[_SwiftValue unsignedIntegerValue]: unrecognized selector sent to instance
BUT if I po vc.view again I get... voilà...
Optional<UIView>
and the execution can be resumed. I am using Xcode 8.1. Reproduces both on iOS device and simulator.
Any suggestions?
I think it's not due to UIViewController.view. Your error says that it's Unrecognized Selector send to instance allocating at some kind of memory index. If one of ur selector method is private, put #objc in front of it. I can surely say it's not the Nil value error.
Make the storyboard-id of the view as "some-viewcontroller-id"
and it would work fine
ISSUE RESOLVED
To make a long story short, it is not related to UIViewController.view at all! It is related to the String.Encoding.utf8.rawValue issue described in this answer.
For some reason the crash on simulator didn't give much info except for I already pasted into the question. On device, it produced a much detailed report that helped me find the root cause of this crash.
This question already has answers here:
[NSManagedObjectContext delete:]: unrecognized selector sent to instance
(2 answers)
Closed 7 years ago.
I have three controllers, one to display all data, second the view deleted item and third to edit. All works fine besides from deleting the NSManagedObject, currently the app crashes with an error of;
unrecognized selector sent to instance 0x7f945b56a680 2015-08-17
18:35:08.835 AppTest[8008:435289] *** Terminating app due to uncaught
exception 'NSInvalidArgumentException', reason:
'-[NSManagedObjectContext delete:]: unrecognized selector sent to
instance ... terminating with uncaught exception of type NSException
(lldb)
Why is this error occurring and how can I delete a NSManagedObject within the UINavigationController and the popToRootController to segue back to the collection view ?
Heres what I have been trying to do in editViewController;
let context = (UIApplication.sharedApplication().delegate as! AppDelegate).managedObjectContext
#IBAction func remove(sender: AnyObject) {
context?.delete(self.selectedObject)
var error: NSError?
context?.save(&error)
self.navigationController?.popToRootViewControllerAnimated(true)
}
Update: I was not having a problem using the popToRootViewControllermethod but using the delete method which should have been deleteObject(). Now i know the problem I see there are many questions on it.
You want deleteObject(), not delete(), since delete is an unimplemented extension on NSObject.
Your code should be:
context?.deleteObject(self.selectedObject as NSManagedObject)
I have a framework I've written in Swift that contains a class that extends UIView and that has an IBOutlet property.
The class is visible from my Objective-C app, but Interface Builder won't see the IBOutlet. Here's the code:
#objc protocol MyFrameworkDelegate {
// My delegate methods here
...
}
#objc class MyFrameworkClass: UIView {
#objc #IBOutlet var delegate:MyFrameworkDelegate?
// The rest of my class here
...
}
I set my view's class to MyFrameworkClass in my storyboard, but the delegate outlet isn't showing.
I tried with and without the #objc modifier, no luck. When I inspect my class from Objective-C, the property comes up without the IBOutlet.
Anyone else came across something like that?
EDIT
Here's the code generated by Xcode for the Swift -> Objective-C conversion:
#protocol MyFrameworkDelegate;
SWIFT_CLASS("_Nc9a0xD6MyFrameworkClass")
#interface MyFrameworkClass : UIView
#property (nonatomic) id <MyFrameworkDelegate> delegate;
...
Also, here's the error message I get when I try to run the app:
2014-06-22 21:41:59.095 MyApp Test[75211:17812266] Unknown class MyFrameworkClass in Interface Builder file.
2014-06-22 21:41:59.099 MyApp Test[75211:17812266] -[UIView setDelegate:]: unrecognized selector sent to instance 0xcf5d650
2014-06-22 21:41:59.101 MyApp Test[75211:17812266] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[UIView setDelegate:]: unrecognized selector sent to instance 0xcf5d650'
EDIT
Here's a screenshot of my storyboard:
Your module is None, you should select it to your corresponding value.
reason: '-[UIView setDelegate:]: unrecognized selector
This makes it look like the object in question is an instance of UIView, not MyFrameworkClass. Check the type of the object in IB.
I suspect the word delegate itself is triggering some kind of underlying bug/mechanism/leaky abstraction.
How about calling it myFrameworkDelegate?
I am also wondering if dragging from IB shouldn't always give the best results by itself but I need to fire up Xcode 6 and test manually first to see what happens. New technology :)
Instead of
#objc #IBOutlet var delegate:MyFrameworkDelegate?
use
#IBOutlet var delegate:AnyObject?
than you'll be able to link your class to this property.
I have been spending days to make connection from a button on the storyboard to a new NSObject class in an IOS project. Methods I used in OS X no longer work in IOS.
I have no trouble connection the button to the IBAction on the original UIViewController class. According to the Apple documentation my new class is not a "valid connection destination".
To work around the issue I tried to call the method in the new class from the UIViewController class. I tried notification and delegate schemes, using the posts on Stack Overflow, but could not get them to work.
The closest I came linking to a +method in the target class, such as
+ (void) startToneGenerator
{
NSLog(#"Arrived in startToneGenerator");
// [self startPlay:nil];
}
However, from inside that method I can not call the -startPlay in the same class. Because the -StartPlay class is part of an audio unit construct I can not change it to a +starPlay class without breaking the audio unit.
Can anyone point me to some documentation which describes what "valid connection destination" really means, and how to make the attempted connection a valid one.
I used the method suggested in answer 1 in OS X, where it does work, but it no longer works in IOS.
I am restating the code you clarify the problem.
// code in VC
- (IBAction)RunPauseStop:(id)sender
{
NSLog(#"arrived in RunPauseSTop"); // OK
[uToneGenerator testMethod]; // OK
// [uToneGenerator startPlay:self]; // crashes
}
// code in uToneGenerator
+ (void) testMethod
{
NSLog(#"arrived in <testMethod>"); // OK
// [uToneGenerator startPlay:nil]; // crashes
}
- (IBAction)startPlay:(id)sender
{
NSLog(#"arrived in <startPlay>"); // Don't get here
}
The line [uToneGenerator startPlay:nil]; compiles (with a warning) but crashes with:
2012-03-06 13:20:25.509 Tinnitus Tamer IP[863:f803] +[uToneGenerator startPlay:]: unrecognized selector sent to class 0x6c40
2012-03-06 13:20:25.509 Tinnitus Tamer IP[863:f803] * Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '+[uToneGenerator startPlay:]: unrecognized selector sent to class 0x6c40'
calling from testMethod; compiles but crashes with:
2012-03-06 13:22:31.413 Tinnitus Tamer IP[885:f803] +[uToneGenerator startPlay:]: unrecognized selector sent to class 0x6c44
2012-03-06 13:22:31.414 Tinnitus Tamer IP[885:f803] * Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '+[uToneGenerator startPlay:]: unrecognized selector sent to class 0x6c44'
I noted that the error message can not find +[uToneGenerator startPlay:, but the method I am trying to call is -[uToneGenerator startPlay:
uToneGenerator *utg = [[uToneGenerator alloc]init]; works OK. In spite of the compiler warning "NSProject may not respond to 'startPlay'.
Thanks for helping me out. Much appreciated. I really was stuck.
You need to call whatever class method you want inside the IBAction method in your VC:
- (IBAction)myButtonPressed:(id)sender {
[MyClass myClassMethod];
}
If you want that code to work you must declare - (IBAction)startPlay:(id)sender with a +. Otherwise you will have to make an instance of your class:
uToneGenerator *utg = [[uToneGenerator alloc]init]; //or whatever you use
and then use that to call your startPlay method:
[utg startPlay:self];
Hope it helps.