I setup a new project using Firebase SDK and only get this error when I add FirebaseFirestoreSwift-Beta. I have it in other projects that was built before Mar-8th and have no issues running them but it won't work on any new projects. I have went back and watched videos to make sure I wasn't missing a step when installing. I am using Xcode 12.4
Is this an issue with the Beta or is there something I am missing on my end?
Many apologies, the issue was introduced by me.
It appears that symbol resolution has changed slightly in Swift between Xcode 12.4 and Xcode 13.
I have made a PR that fixes the compilation issue on Xcode 12.4 here:
https://github.com/firebase/firebase-ios-sdk/pull/9438
Until then, if possible, you can update to the latest version of Xcode.
If that is not possible, then if you use a package manager where you can make local edits, you can rename the variable data to something else (like d) to make it compile.
If you can't do that, then a more substantial workaround would be to fork the repository, check out the release tag, create a new branch and fix the error, then pointing your package manager to you own branch including the fix.
Another solution is of course to stay on 8.12 of Firebase until the PR above is merged and released.
I upgrade a Plone site from 4.2 to 4.3. The upgrade steps are basically:
running install.sh to have a 4.3 environment
copy Data.fs to var/filestorage and custom dexterity package to src
running upgrade in ZMI
Everything seems fine. But when I add/edit Page items, TinyMCE toolbar is missing for the body field. Only showing a Text Format dropdown. Note: I do see the toolbar trying to render (first 2 icons appear), but fail and disappear.
What am I missing? Any hints?
No definitive answers, but a few suggestions. I have 9 plone sites all running the same version of Plone (4.2) and have some where TinyMCE works flawlessly, and others where I can't make it work at all.
Check /portal_javascripts and make sure that you have ++resource++plone.app.jquery.js (I think you also need jquery-integration.js and ++resource++plone.app.jquerytools.js, but I may be wrong about those), as well as tiny_mce.js and tiny_mce_init.js).
check /portal_kss and ensure you have ++resource++tinymce.kss/tinymce.kss
check /portal_css for ++resource++tinymce.stylesheets/tinymce.css
I saw your edit about the toolbar beginning to display after I posted this response. You really need to use the development tools for your browser-of-choice (e.g. Firebug) and look at the console. If it starts to display and then fails to finish, there's sure to be an error in the console log.
Check to see whether you have outstanding upgrades to the Products.TinyMCE:TinyMCE profile in Upgrades in portal_setup via the ZMI. If there are any, run them and restart your Plone instance.
I had the same issue with the same version upgrades and there were outstanding upgrades. They must have been missed somehow, presumably a bug in the Plone upgrade process from 4.2.5 to 4.3.4.
FWIW, I just ran into this issue in an upgrade from 4.1 to 4.3.14.
In my case, the problem was that the site uses the Plone Classic skin instead of Sunburst. The Classic skin for some reason did not have the tinymce layer registered. The giveaway was that jquery.tinymce.js was registered in portal_javascripts, but marked in orange as (resource not found or not accessible). I grepped the buildout eggs and realized that jquery.tinymce.js lives in a skin layer of Products.TinyMCE-1.3.26. From there it was easy to figure out why it was not found.
I'm developing an app which is iOS 4 compatible, so my deployment target is set to iOS 4.0.
Whenever I drop a UINavigationController onto a UITabBar, I get these two warnings:
warning: Attribute Unavailable: Defines Presentation Context is not available prior to Xcode 4.2.
warning: Attribute Unavailable: Defines Presentation Context on iOS versions prior to 5.0.
The UINavigationController functions as expected, in fact, the entire app runs perfectly. But these two warnings are driving me nuts!
Also, the moment I delete the UINavigationController the warnings disappear.
Just uncheck the "Defines Context" checkbox in the attributes inspector. (Double-click on MainWindow.xib, select the navigation controller, then go to View->Utilities->Attributes Inspector.) That'll get rid of the warnings.
You are getting these warnings because you are using iOS 5.0 SDK features with a 4.x deployment target.
All, if not, most of the new 5.0 hotness, including ARC and Storyboards, is completely backwards compatible with iOS 4.x (I don't remember if 4.0 or 4.3 is the lowest supported version, check the docs), it will work as intended, but Xcode is going to warn you anyways.
You should be able to disable that warning if it really bothers you, but I wouldn't. That said, Apple does not currently accept applications built/archived with the Xcode 4.2 beta for submission to the App Store. This means you need to use Xcode 4.0/4.1 in a production environment.
Before we go any further, you should know that Xcode 4.2/iOS 5 is beta software, it is under NDA (you agreed to this when you joined the Apple developer program) and cannot be discussed in the public domain. This means you won't be able get much help from places in the public eye, like StackOverflow, as good as it can be. But, since I'm here and this is a very high level question, I can help :)
In the future, if you have iOS beta questions or issues, you should hit up the Apple Developer Beta Forums (an excellent resource, always search before you post), or #iphonedev on irc.freenode.net for not-beta stuff (I'll be there, say hi!)
If you're developing an application for release on the App Store:
You need to be developing with Xcode 4.0 or 4.1, Apple will not accept applications built/archived with 4.2. (I know I repeated myself, but people seem to miss this often)
And, although 4.2b7 supports developing for older frameworks better than previous Xcode betas have (by allowing you to install previous versions of the simulator), you will still find yourself accidentally using 5.0 SDK functions all over the place, as the code completion/interface builder very aggressively favors all of the new hotness. This is because the beta is for trying new things, not stable application development.
This means you need to switch back to using Xcode 4.0/4.1 for production, if you don't have it installed, or you overwrote the stable version with the beta, do not try to install 4.0/4.1 on top of the 4.2 beta, weird things will happen and both versions will start acting really weird and and Xcode will crash at least twice as often.
The best thing to do in this situation, is to follow the below steps. Make sure you don't skip anything, otherwise you'll have to restart the whole process.
Make sure you have your code committed and pushed up,
uninstalling Xcode like this temporarily removes git. (This was an
issue for me at work once)
Download the installers for Xcode 4.0/.1, and 4.2 if you intend to keep experimenting. (if you already
have both downloaded, this whole process won't take more than 5
minutes on an SSD)
Uninstall the Xcode beta from the command line using this command:
sudo <Xcode>/Library/uninstall-devtools --mode=all (more info here)
Restart your computer (this is important, do not skip it!!!)
Install the most recent non-beta version of Xcode and resume development.
If you want to use both versions of Xcode (4.0/4.1 and 4.2):
You must install the beta AFTER 4.0/4.1 is installed, otherwise you will be overwriting new things with old things, and this will give you many, many obscure headaches. I also recommend restarting between installations.
You need to install 4.2 after 4.0/4.1, and to a different folder (I use /Xcode4beta/, don't put it within the folder that contains 4.0/4.1, either). I've found I learn about the new hotness best if I keep separate iOS5 branches of my work, and update what I can when I have some free time.
If you have the iOS5 beta installed on your phone, and Xcode 4.0/4.1 won't let you build to your phone:
This is because Xcode needs to grab the debug symbols from the phone before it can be used for devleopment, but only the Xcode beta can do this for an iOS5 beta device, so follow these steps:
Make sure your phone is plugged in and turned on, and that your provisioning profile/certificates all check out.
Close the project in Xcode 4.0/4.1.
Open the project back up in Xcode 4.2, and check organizer. You should either already have a green dot next to your phone (assuming all of your provisioning is working), or it should be gathering the debug symbols. Let this finish, and then build your project. It doesn't need to be a successful build, nor do you have to install the application to the phone, sometimes you don't even need to build, Xcode can be a fickle mistress.
Close the project in Xcode 4.2.
Open the project back up in Xcode 4.0, you should now be able to build and install to your phone as you normally would.
Xcode 4.0/4.1 should now be able to use your device for development until you restart the computer.
Resolution is here:
How can I fix "Freeform Size simulated metrics are not available prior to Xcode 4.2" warnings?
You just need to change the development version of your xib file to Xcode 4.2 (default is Xcode 4.1)
View Controller and Navigation Controller setting or options name ( attributes inspector )
Define Context ( Checked ) unchecked.
I followed the instructions for using a phonegap template in xcode 4 and dragged and dropped the autogenerated www folder into the project. The problem is that on each build it re-autogenerates the index.html which is overwriting my code. How do I stop this happening each build?
That was a bug with the release. Try downloading 0.9.5.1 again and reinstalling the package. It should work now. You may need to set up your project again though.
For anyone having this issue see this link:
http://www.google.com/url?sa=D&q=https://github.com/phonegap/phonegap-iphone/issues/103
There will be a new installer soon apparently
I recently started a project using Xcode 3.2 and the vstsdk 2.4 and then I purchased Xcode 4. When I open the project within Xcode 4 I get the "missing base SDK" error which I can fix by changing that to either Mac OS X 10.5 or 10.6. After this though my .vst file is still red in the file tree. I have also tried to delete the file and re-add it but when I do it adds it as a folder instead of a .vst file. Without this I cannot build the project as the target is missing.
Any ideas?
Cheers.
The file "yourplugin.vst" (or whatever it's named) in the Xcode group is actually the product's output target, so you shouldn't delete it. If it's red, that simply means that you haven't built the target yet.
If you are using source control, I would advise reverting back to the version before you deleted the .vst file and trying to build from that point. If you're not (and why aren't you?! ;) ), then you can try re-creating the target manually.
I have also written a tutorial on how to make a VST plugin in Xcode which you might find useful. I will be updating this for Xcode 4 soon, so if you run into any problems, post a comment there.