After updating to Xcode 6.3/Swift 1.2 I'm getting these errors. (.NoCase can't be found, and .insert doesn't accept (Setter, Setter).
Did something change in the SQLite swift API?
SQLite.swift is still young so the API is still a bit in flux as things tighten up. Sorry for the inconvenience!
Collating sequence names have been un-camelcased. See: https://github.com/stephencelis/SQLite.swift/commit/74e80d3eb4b1108b37c2acec3321cf27f5037843
Upgrade path: .Nocase.
Insert's overload returns an Int64 now. See: https://github.com/stephencelis/SQLite.swift/commit/5380d5b502bd76ea99fe0ec54785f6bacd1cb8c1
Update path: return Int64? from saveNotes.
Related
Can anyone suggest what to do about this message that I get when submitting my Xamarin Forms app to the iOS store?
Comment on possible duplicates
This question was asked before and not answered; I don't think an answered duplicate exists.
This is a known issue which was recently closed by the Xamarin team issue can be found here https://github.com/xamarin/Xamarin.Forms/issues/7323
And the fix is and i qoute
All the bits are in place, solution time! TL;DR: all is described in this piece of documentation here.
Make sure you are using the latest Visual Studio (for Mac) on the stable channel, that should put you on the right path. At the moment, you will need to use the Xamarin.Forms 4.5-pre1 preview release. I understand that this might not be an option for all of you, but rest assured, the stable package will be out well before the deadline. Stable 4.5 is planned mid to end of February.
Lastly, put the --optimize=experimental-xforms-product-type flag into your iOS additional mtouch arguments setting and you should get rid of the deprecation warning by Apple. If you don't have any references of your own to UIWebView of course 🙂
I would like to ask you to try this at your earliest convenience. Maybe not to release an actual new version to the store based on the Forms preview package, but at least upload a build to verify that this solution works correctly. Whenever you do, you can just update to the 4.5 stable package and release a new version with confidence.
If you do run into anything with this solution, please feel free to reach out to me directly (gerald.versluis [a with a long tail] microsoft.com) or open a new issue on the repository. Of course positive feedback is always appreciated as well 😉
I'm getting some errors after updating from Firebase 2.5.1. It seems to me that GeoFire has lost some critical components, and being a beginner I am immediately lost. Has anyone seen this issue yet?
Below is a screenshot of my list of errors.
To add a little more info, here are the lines where the errors are occurring in GFQuery.h:
- (FirebaseHandle)observeEventType:(GFEventType)eventType withBlock:(GFQueryResultBlock)block;
- (FirebaseHandle)observeReadyWithBlock:(GFReadyBlock)block;
- (void)removeObserverWithFirebaseHandle:(FirebaseHandle)handle;
The current geofire version is not compatible with Firebase 3 the team is currently working in a compatible version
You can follow the issue here
https://github.com/firebase/geofire-objc/issues/37
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.
Xcode 7.1 is now available on app store but before I update xcode I need to be sure that my existing project won't breakdown because of the update. So would updating from xcode 7 to 7.1 run the migration assistant for swift 2 and breakdown my project?
It appears that there weren't any breaking syntax changes. Mostly just quality of life updates for the language (being able to put string literals in string interpolation statements, function covariance/contravariance, etc).
I've been writing a Swift application over the last week using the latest Facebook iOS SDK v4.0.1. After updating to the latest XCode 6.3 and Swift 1.2 today, I've got a lot of errors. I've been able to fix most of them, mainly new syntax errors like casting, but this error shows up and I haven't been able to find the cause.
if result.grantedPermissions.containsObject("email") {
...
}
'Set<NSObject>' does not have a member named 'containsObject'
If anyone has any advice that would be appreciated, thanks.
It seems that result.grantedPermissions is a native Swift Set
which was introduced with Swift 1.2 (Xcode 6.3) and bridges with NSSet.
To check for membership in a Set, you can use its contains()
method, for example:
if result.grantedPermissions.contains("email") {
...
}
For more information, see "Sets" in Collection Types in the Swift documentation.