“smb big sur”

I'm seeing the same behaviour as you are, I went in and deleted any other Administrators attached to each machine and each one of them came online, but I'm also seeing another big issue with the app when on 10.11 B5.Are any of you experiencing this as well? https://forums.developer.apple.com/message/34233#34233

Interesting. Try rebuilding the Photos library:Quit Photos if it is open.Hold down the Command and Option keys while you open Photos again.It should only take a few minutes even if the library is big...You may then have to trigger the iCloud syncing again by toggling the setting described in my first post.

Thank you for your reply. In your inspiration, I did a test in my code. Here are my results.I am using let options:[NSURLBookmarkCreationOptions] = [ NSURLBookmarkCreationOptions(rawValue: 0), .MinimalBookmark, .SuitableForBookmarkFile ]1 with option 0, the bookmark even a little smaller than the .MinimalBookmark option.2 I can not get a file alias from option other than .SuitableForBookmark3 the bookmark data on option .SuitableForBookmarkFile is almost as big as a file alias.4 although you can not get a file alias directly from other option, you can still get then from bookmark to NSURL, then re-get a bookmark with .SuitableForBookmark option, then get the alias.do { try bookmark.writeToURL(newURL, options:.DataWritingAtomic) try NSURL.writeBookmarkData(bookmark, toURL: aliasURL, options: NSURLBookmarkFileCreationOptions(0)) } catch let error as NSError { print(error.localizedDescription) var isStale:ObjCBool = false let newURL = try! NSURL(byResolvingBookmarkData: bookmark, options: .WithoutUI, re

As per this stackoverflow solution: stackoverflow.com/questions/2111076/push-notification-in-non-english-languagesFor Arabic and some other non-English languages, you need to pass the length of the UTF encoded string before the counting.Use...writer.Write((byte)0); //First byte of payload length; (big-endian first byte) enter code herebyte[] b1 = System.Text.Encoding.UTF8.GetBytes(payload); writer.Write((byte)b1.Length); //payload length (big-endian second byte)... to modify the following generic C# Apple Push Notification Provider:int port = 2195; String hostname = gateway.sandbox.push.apple.com; //load certificate string certificatePath = @cert.p12; string certificatePassword = ; X509Certificate2 clientCertificate = new X509Certificate2(certificatePath, certificatePassword); X509Certificate2Collection certificatesCollection = new X509Certificate2Collection(clientCertificate); TcpClient client = new TcpClient(hostname, port); SslStream sslStream = new SslStream( client.GetStream(), false, n

KMT wrote:Apple is a user here, just like us devs. JIVE Software (Portland, OR), makes and configures the (contracted) forum software (they specialize in Windows), so I wouldn't hold my breath on improvements/tweaks/changes any time soon.This is absolutely horrible. It took 30 clicks to find my way back to this forum.I will definitely put this on the table on our next Apple Enterprise Support call.I suggest you all do the same, shine a big bright light on this horrible new forum design.Sorry for the vent, just feel like an incompetent/incapable company outbid a competent/capable company and we are all impacted.Don

Yes, I also have problems to extract big (multi file) archives with Unarchiver. It crashes immediately.

What's even worst with this is that if you have iCloud with CoreData your users have a huge risk of losing data.CoreData stack with iCloud creates a folder named mobile~_identifierForVendor_ where it puts the sqlite file. On app update, the identifierForVendor changes, and a new sqlite gets created with a different path: this isn't a big deal as far as users had enabled iCloud, the data would just get downloaded again. However, if the users DOESN'T have iCloud enabled, this is a mess because the old file cannot be found anymore, and data is there but unavailable.I wrote to the technical support and they told me that this is a known issue, it shouldn't happen and it was going to be fixed server-sideAnyone else is having the same issue?

Any price change starts rankings over again.Marketing your app is the big question. What is your budget? What category is your app in?See my next post when it gets approved, since it contains an offsite link:

It looks like we are part of big group of people with interface builder broken.I later found this error:https://forums.developer.apple.com/thread/13170?sr=stream&ru=14325Here they say the solution is reinstall, I hope we get an alternative to it 🙂. https://forums.developer.apple.com/message/35962#35962

You could try setting the font size to something really really big in IB, and ticking the adjusts font size to fit width so it will auto shrink. But that would only work for static text, and might not look right on different OS versions where default fonts change. Ugly as it is, you might end up having to programmatically set the font based on some empirically determined formula (fudge factor * label width / superview width or something) in viewDidLayoutSubviews. Hopefully someone can come up with a better idea.Font sizes are specified in points, so the absolute size of text on different devices or platforms will depend on the DPI of the screen. The same font will have a different absolute (ruler) size even on different Apple devices that have varying points per inch.

I can confirm that these two patches work.http://swcdn.apple.com/content/downloads/43/22/031-29032/71ihp9c54k547fvol25w5g85z9323gqwnr/OSXUpd10.11.pkghttp://swcdn.apple.com/content/downloads/43/22/031-29032/71ihp9c54k547fvol25w5g85z9323gqwnr/FirmwareUpdate.pkgWhile this did give me back two working versions of Xcode, after rolling back with this method, all sound has stopped working (coreaudio does not appear to load). However I can see the audio hardware when I look at System Information. Some other telltale signs indicate that all is not well. My accessibility zoom and desktop switch show visible graphic lag. I will try the disabling SIP in the recovery mode. I may want to rollback to a prior backup using Time Machine if this fails. I think that loss of sound should be in big bold letters on your post (because I missed that in my first reading), hence:NOTA BENE: YOU WILL MOST LIKELY LOSE SOUND AFTER APPLYING THIS PATCH