I'm seeing the following error during compile time when working with the latest version of Xamarin.iOS that was released yesterday:
UIActivityViewController.h:23:1: note: 'initWithCoder:' has been
explicitly marked unavailable here
- (nullable instancetype)initWithCoder:(NSCoder *)aDecoder NS_UNAVAILABLE;
I don't recall ever having this issue before and my code hasn't changed much between the last update and now. Can anyone help me figure out what's going on?
It's a known issue which is harder to diagnose because of a clang bug, i.e. it has nothing to do with UIActivityViewController.
You might be able to workaround this by removing [Export ("initWithCoder:")] inside your code. That should be fine unless your managed object needs to be created from native code. YMMV
Related
After a couple of times changing and saving a .cshtml file, the view starts to get frozen.
I recorded a video, you can check it right here.
Does anybody know how to solve it?
this is a known bug in VS for Mac and it will be fixed in an upcoming release. You'll need to update to the latest version (I'm not sure when that will be released, but hopefully soon).
Sorry for the inconvenience!
We have latest Xcode(7.2) having Swift(2.1.1) installed in few mac systems. Here developer didn't find any errors in his code which was checked in, but the same code used at other end were observing errors(most of them related unwrapping variables).
verified all settings and version details not able to find any difference. Any help or suggestions will be appreciated. Thanks
Most likely the machine "at the other end" is not running Xcode 7.2. There is a tool for converting Swift 1.x to 2.x, but not the other direction. But without code sample illustrating the problem, we can't help you much. In addition to shifting unwrapping conventions, there is new syntax later versions of Swift (e.g. guard, error throwing, etc.).
But, if you're going to share a Swift project amongst multiple developers, you probably just want to make sure everyone is using the same version of Xcode. And with Swift progressing as quickly as it is, you might want to encourage everyone to use the latest production version of Xcode.
I should mention that I originally posted this as an issue on Neovim's tracker, but it hasn't been getting a ton of traction there lately and I'm beginning to suspect that it's more an issue with my setup rather than Neovim itself.
Essentially, I had stopped building neovim nightlies for a few months. Having heard that it's getting integrated terminal support I decided to rebuild using the latest source, only to get a persistent, odd error. No matter what my build settings are, it always boils down to make hitting an error when it has to compile a file called loop.so. I hadn't noticed this issue with any other software I try to build, but I suspect it could be an issue with my environment.
Does anyone here know what this file's role is, and why the compilation could be failing at that point?
You might need to install the full Xcode app and not just the command line. This fixed the issue for me.
The issue turned out to be a bad typedef in a libuv header, object.h.
I just started Xcode 6.3 with a project that I have been working on for a while. I did some changes and than ran the previously working program. Result: a build failure with the message
Compile ZXParsedResult.m...
So the ZXing library can suddenly not be compiled any more. I guess this is another XCode bug (the program will not run even after a reset of all changes to the previously working code base). Is it possible to disable this error message?
I already triggered a successful clean on the project.
Looks like problem has been solved in latest version of library, see discussion on this issue https://github.com/TheLevelUp/ZXingObjC/issues/208
If you are not ready to upgrade to latest version, I'd prefer this fix from discussion
(id)parsedResultWithType:(ZXParsedResultType)type {
return [(ZXParsedResult *)[self alloc] initWithType:type];
}
More on such kind of errors
new in Xcode 6.3/iOS 8.3: using self alloc for convenience constructor causes build error
Xcode 4.5 (but also earlier I think) reports build errors, but I just created a successful build. And it also depends on which file I select in the project browser. Some files give errors, others don't.
This leads me to believe that there is a bug in the auto evaluation of my code. It seems to loose the #imports or deeper links to other headers...
I have been without the problem for a while, but today it returned. Very strange and annoying.
Is there an autocompletion cache to delete or something.
(Deleting derived data didn't help, or cleaning the build.)
Has anyone found a way to fix this?
edit: still happens in Xcode 4.6
Might help to use #class more in headers, but unverified.