smb big sur

Yes your're right, I'm using a self signed certificate. Is there an issue due with this?Yes. ATS is pretty much fundamentally incompatible with self-signed certificates.In itself, that's no big loss IMO. Self-signed certificates are a bad idea and you're much better off avoiding them and instead using a custom CA instead (Technotes 2232 and 2326 have the details of this). However, that approach is also incompatible with ATS as things currently stand.In short, to work with ATS you will have to get a certificate issued by a trusted CA. The alternative is to disable ATS (only for the domain you care about, of course) and then, if necessary, do your own custom trust evaluation.ps borgiscool and Lucky7, please start a new thread for the b4 regression; I'd like to use this thread to help sebastien78 with the more fundamental problem.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

I have modified my code a bit, so the issue of two events always is still there, since before there could be more than two, which means that it still always results in 12 or 13 cards.Right now in the Game class, I have a nest loop combination of two four loops, which I do not really understand why that works, but using a while loop as the outter loop, which is what I should be doing, generates more rows than necessary (beyond 13 cards).For now, it is not as big a deal, but I would still like help.

Can't even switch back to the default - it's stuck on vibrate., frustrating to say the least.... It also negates tones on my watch when paired... (Consider the fact the Watch doesn't vibrate - big disadvantage).....

Pavel,We are using push with sound, always have been. It works perfect when app is in background state, just stops working when app enters suspended state. have you had any luck updating an app that is in suspended state? I personally notice even big budget apps like Skype, Evernote, etc seem to do a refresh when they launch to get new data and am beginning to wonder if this is the reason they do such a thing. Would greatly prefer to let push trigger the refresh if possible... Just can't seem to get it to work. Have followed all the docs and triple checked our work, but just doesn't happen when app reaches that suspended state.

ObjectHub wrote:I suggest using CFAbsoluteTimeGetCurrent() …CFAbsoluteTimeGetCurrent is based on gettimeofday and thus will change with the system clock. benrimmington wrote:For real time threads, see Technical Note TN2169 …Mach absolute time may well be the right option here, and all of the APIs you mentioned are based on Mach absolute time.The big gotcha with these APIs is that Mach absolute time stops when the CPU sleeps. @OmniOnline, if you only need to track time while your app is in the foreground, Mach absolute time (or one of its derivatives) is your best option. Otherwise things get more complex and you should post a follow-up with more information about your goals.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

No help so far , this is really disgusting , How come this Lack of interest on help from a big Company like Apple ? the Incident #588659 Open since 12 days now

Thanks - I found those instructions on another thread and they worked.What was frustrating was that I thought I was required to upgrade to El Capitan to get Clang 7.0. Turns out I already had a copy of the 7.0 tools under Yosemite, but I hadn't configured them in XCode, but loading them onto 7.04b doesn't activate them; You have to manually change the setting via preferences, as I comment above. A lot of time wasted and now I have a big commitment to the El Capitan beta cycle. Oh well.Still can't quite figure out how to create an archive that has a rebuilt BITCODE_ENABLED static library, which is the reason I needed Clang 7 in the first place. If you know, please pass along. This has been quite a rat-hole.

If this helps you to get your simulators back, good, because it fixed my situation. Executive summary is that my ~/LibraryApplications Support folder needed to be cleaned up by removing the iPhone Simulator folder. Then all simulators worked, again. My method below to figure this out is to make sure it was not because of one version of OS X or one version of Xcode, since always there are many. TL;DR to follow.First off, release notes say Xcode 7 only runs iOS 9 simulators, so that should be the expectation on either 10.10 or 10.11. Also, the Preferences > Downloads panel shows that other simulators may be installed, but I have seen a radar referenced on that issue; try as you might they cannot be installed. So right away, I used Xcode 7 for testing XCTest UI test features, primarily, under what I had which was a 10.10.4 machine. but, I could run on any device in 10.10.3 or 10.10.4.I needed to resolve what I had done with all these installs, so I went back to running Xcode 6.4 on my 10.10.4 machine and this

This (modifying the version plist) is probematic for me because I need to determine what is broken in our existing ecosystem (including the installer and system configuration needs) under the new OS version before I know where I need triage. By modifying the version to install our current tools and app, I can do this. Yes, I can build and run fresh on the platform without the installing the package, but that takes out a big part of the user-proof testing. The developer can always get their app to run .I don't appreciate what I've run into so far, but I'm in a the jury's out mode on SIP until we get closer to user release. I already know of 3 universities that will turn this off on every roll-out as soon as they have to install 10.11.One question that I really don't expect to be answered - why not use a skeleton overlay system like some ***BSDs that reset the protected environment paths on reboot so that even an exploit can be undone by a simple reboot? If you want to modify a skeleton level file, reb

Hi Prashant,The Dutch Localization issue is proving to be a big hassle for others too:https://forums.developer.apple.com/message/34077https://forums.developer.apple.com/message/33975

Before going further I recommend that you brush up on the model-view-controller design pattern. This is formally covered in the Model-View-Controller section of Cocoa Core Competencies.https://developer.apple.com/library/ios/documentation/General/Conceptual/DevPedia-CocoaCore/MVC.html#//apple_ref/doc/uid/TP40008195-CH32-SW1There is, however, a lot more information about this technique available from both Apple and non-Apple sources. I'm not in a position to recommend non-Apple resources but on the Apple front I'm a big fan of WWDC 2010 Session 116 Model-View-Controller for iPhone OS.It's an old 'un but a good 'un.In my experience the best way to address this issue is to put your networking code at the model layer. That is, have your view controllers simply arrange to display model objects and have the networking code populate and mutate those objects like it would with any other model objects.This approach has some really important advantages:It decouples the view controller from the networking, whic

So long as your MacBook is relatively new (last 5 years or so) then it can be put into Target Mode by connecting it (physically, not over the network) to another Mac with a FireWire or Thunderbolt cable.Then boot the MacBook holding the T key until the screen shows a big connector icon in the middle of the screen.On the other Mac, your MacBook's internal drive will now appear as an external drive and, once you've downloaded the Yosemite Installer on the other Mac (If you've downloaded it before you'll have to hold the alt/option key while you click on your Purchases tab in the App Store), then you should have no difficulty selecting the MacBook's intenal drive to install to.You will have to erase the El Capitan install before being able to install Yoseemite though because the installer prevents installing an older version of itself over a newer version. So, of course, anything you need from MacBook needs to be copied over to somewhere safe before you erase. This should be easy because of your MacBook