Silence Swift 2.2 warnings?
I'm working on a project using Swift 2.1. I upgraded my Xcode to the latest and now see hundreds of warnings for Swift 2.2 improvements (mostly things like the change in selector syntax). Is there a way to turn off Swift 2.2 warnings in favor of Swift 2.1 warnings in Xcode? I can't go in an fix all the warnings because most of my team has not yet upgraded their copies of Xcode. I know in Build Settings for LLVM - Warnings - All languages I can set Deprecated Functions to No. But I'd like to keep the Swift 2.1 ones. I don't see anything like that for Swift in Xcode. And in Xcode 7.3 (7D175) when I turn deprecation warnings off for all languages, I still see tons of them for the Swift 2.2 stuff. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Silence Swift 2.2 warnings?
On Apr 1, 2016, at 07:35 , Eric E. Dolecki wrote: > > I can't go in an fix all the warnings because most of my team has not yet > upgraded their copies of Xcode. I don’t know if there’s a way of silencing specific warnings in Swift. The best place to ask would be the swift-users list over on swift.org (though I bet it’s already been asked there). In retrospect, it really seems that there should have been an obvious option for this. (Build settings that say LLVM compiler mean Clang, and don’t apply to Swift.) FWIW, my suggestion is that you hold off using Xcode 7.3 until the entire project/team is ready to transition. I suspect Swift 3 is coming very soon (WWDC is only 2 months away), so it’s a fairly short-term compromise. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Silence Swift 2.2 warnings?
Thanks for the response. I've been living with looking at oodles of warnings (268 currently) and it's mostly okay. Where there are blocks of notifications, I have to close my eyes for all the yellow ;) I can't wait to change all our selectors, it will be SO much better. On Fri, Apr 1, 2016 at 1:28 PM Quincey Morris < quinceymor...@rivergatesoftware.com> wrote: > On Apr 1, 2016, at 07:35 , Eric E. Dolecki wrote: > > > I can't go in an fix all the warnings because most of my team has not yet > upgraded their copies of Xcode. > > > I don’t know if there’s a way of silencing specific warnings in Swift. The > best place to ask would be the swift-users list over on swift.org (though > I bet it’s already been asked there). In retrospect, it really seems that > there should have been an obvious option for this. (Build settings that say > LLVM compiler mean Clang, and don’t apply to Swift.) > > FWIW, my suggestion is that you hold off using Xcode 7.3 until the entire > project/team is ready to transition. I suspect Swift 3 is coming very soon > (WWDC is only 2 months away), so it’s a fairly short-term compromise. > > ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Unable to create unsliced image from csi bitmap data.
Hi all. I'm back fleshing out my iOS bundle and framework and I just had a minor heart attack when I noticed that suddenly the images within our framework's bundle magically don't load on some versions of iOS and the simulator. I've been running from Xcode 7.1 and the framework was displaying the images as expected within the hosting apps on iOS 8 and 9 and the simulator. Today, I just ran the framework on various versions of iOS (8.x) on the device and in the simulator and suddenly, this is happening: Unable to create unsliced image from csi bitmap data. -[CUIThemeRendition newImageFromCSIDataSlice:ofBitmap: usingColorspace:] Unsupported pixel format in CSI got 65536 These images are being loaded from an asset library Looking in to this, this issue just started today for me, but it looks like a long standing bug: http://stackoverflow.com/questions/24643904/xcode-6-beta-3-unsupported-pixel-format-in-csi-or-unable-to-create-unsliced-i All of my images are PNG files and display as expected on iOS 9. Have any of you seen this issue before? Thanks in advance, Alex Zavatone ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Is it still possible to share Keychain items between apps under iOS 9?
I have a token stored in the keychain of my app v1. I would like app v2 (a completely separate app) to be able to access that token from the app v1's keychain. Turned on the shared keychain capability in my project. Found many examples on how to do it, most notably the example at http://shaune.com.au/ios-keychain-sharing-data-between-apps/. If possible, I would want to leave app v1 untouched, e.g. not release an update for it for this to work. That's why I thought keychain sharing was the best way. However, after configuring the keychain access groups in the Entitlements file created when you turn on the Keychain Sharing, the UICKeychainStore that is used in the example and that I added to my project is unable to retrieve the token from app v1's keychain. In app v1, however, I used the KeychainItemWrapper class provided by Apple to store my token. Token is saved as the value for the kSecAttrAccount key, which is 'attr'. Thinking that maybe something was wrong with it, I decided to do a test. I modified app v1 to use UICKeychainStore to store a value under a different key. I ran the app a couple of times just to make sure it was able to access the value, which it was. Back to app v2, I double-checked the keychain access groups in the Entitlements file according to the example. I had the $(AppIdentifierPrefix)$(CFBundleIdentifier) set as the first item in the keychain group and $(AppIdentifierPrefix).com.myapps.v1app as my 2nd item in the keychain group. Yet, when running app v2 on the iPad, it is unable to retrieve the token from the same key I used to save it in app v1. I found another article mentioning using a shared keychain group between the 2 (which would force me to release an update to app v1) but just for the sake of it, I gave it a tried. I changed the keychain group in both apps to be only com.myapps.shared for the only keychain group in the Entitlements file. Same result. App v2 cannot access the token stored by app v1. So, since all the examples were 2 or 3 years old, I'm wondering if that feature was somewhat deprecated by Apple. Anybody has any idea or pointer? Thanks in advance! -Laurent. -- Laurent Daudelin laur...@nemesys-soft.com AIM/iChat/Skype:*LaurentDaudelin* http://www.nemesys-soft.com/ Logiciels Nemesys Software ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
