“smb big sur”

I find it baffling that a company as big as Apple cant handle a simple auth system, not even respond. Why do we pay 99U$ for a service that doesn't even exist?

Same here, iMac late 2014 5K doesn't wake the screen from sleep, though keyboard and mouse probably work fine. I have to restart using a linux side kick.Otherwise el capitan not a big deal compared to Yosemity (should have waited with the update apparently : )) Oh, and yes Apple support wanted money for a helping hahaha, nice guys!

We experience the same problem with any iOS 9.x so far. Our software was released before iOS 9.x came outand many users that upgraded to iOS 9.x reported that our software has become very unstable. The crashesoccur randomly. So far only iOS 9.x was affected, we have not seen these crash logs for iOS 8.x. Most devicesseem to be 1GB devices, but we have seen the crash happen for 2GB devices as well.The relevent crash log portion looks virtually identical to the one posted by the OP:Thread 0 name:Thread 0 Crashed:0 AGXGLDriver 0x0000000180b42db8 agxuKillClientContextStateError() + 12 (agxu_kill_client.cpp:13)1 libGPUSupportMercury.dylib 0x000000018ce06ec4 gpusSubmitDataBuffers + 172 (gpui_context.c:602)2 AGXGLDriver 0x0000000180b30db0 glrAGXRenderVertexArray(GLDContextRec*, unsigned int, unsigned int, int, int, unsigned int, void const*, int, void const*) + 628 (agxu_vertex_array.cpp:271)3 GLEngine 0x0000000185bdaf34 glDrawElements_ACC_ES2Exec + 428 (gl_vertex_array_draw.c:154)I have managed to have a look at th

I just tried the Adventure game in iOS 9 on an iPhone 5, I'm getting around 30 fps. I don't remember what it performed like in iOS 8 so I can't comment on that. On an iPhone 6 with iOS 8 it runs at consistant 60 fps though.There is a pretty big difference at the main menu. In iOS 8 the number of nodes is around 150 and the number of draws are 29. The exact same project running in iOS 9 shows 259 nodes and 131 draws...and about half the framerate (though the two devices aren't the same so it's not a fair comparison).Visually they look the same though.Back to the waiting game I guess....

The problem is that the brand new machine does not have the private key used to sign apps using your existing certificate. You can download all you like from the Member Center, but your private key is not there. It never leaves the machine that generated it - except when you export the developer profile, copy the resulting .developerprofile file over to a new machine, and import it using Xcode. That will move the associated private key.If you didn't export your old developer profile before changing machines, should be no big deal - revoke and delete the existing certificates on the Member Center, go into Xcode preferences -> Accounts and delete any local copies of code signing identities and profiles. Then try and build again. Xcode should offer to Fix Issue - it would be nice if it actually explained what it was doing, but I believe it is emulating the old manual process. It generates a new private key, stores it in your login keychain on that Mac, generates a certificate signing request using th

Really need a fix before the release of the Apple TV.That's a big concern, and the user gets blocked if he accidently click the remote ! No possibility to switch pages !@AppleStaff ? Is it a known bug ? Thanks,ManOnTheMoon

the advice in the dialog does not in any way line up with reality.which is an insane way to run a business.quote: You have a valid Developer ID Application certificate in the Member Center, but it is not installed locally. If your signing identity is installed on another Mac, you can export a developer profile on that Mac and import it on this Mac. You can also reset your current certificate.in this block of text we find out that the member center has a Developer ID Application certificate. Great. I do not have access to my previous developer profile, The particular machine that had a developer profile installed, ate itself and the hard drive, poof. So our only option is this bit: You can also reset your current certificate. IF we're using english, then when the dialog says : current certificate it means that Developer ID Application certificate. I know... it's a bit of a strecth that the only object in a different sentence is the implied object in a following sentence. I found the Developer ID Application ce

It seems you are using an old outdated tutorial. The code you have shown above looks like an old-fashioned Swift 1.1 style.(Swift 1.2 was a big change, and the chage in Swift 2.0 was bigger. And now Swift is getting near 2.1.)And another important thing is you don't understand the error message about optionalities. How to treal Optionals is one of the most basic (and also the most difficult) parts in learning Swift.Without knowing how Optionals work in Swift, and just getting told how you can fix that single line, you might need to ask hundreds of questions about most code snippets in your tutorial.This is just my recommendation and you can expect some other would tell you that single line fix,but you should better find an updated tutorial which describes well about Optionals before writing about segues.

you pretty much need to watch allocations in intstruments to realize what is happening with your app. I found that using a shared instance to retrieve atlas references had a big improvement on this....without a code example, pretty much what you do is:implement a shared instanceimplement a public getAtlases function that loads selected atlases (or not if they are already loaded)implement a protocol which contains a callback that returns an array of texture atlases (use preloadTextureAtlases:iAPTextureAtlases withCompletionHandler)

How much physical ram?How much free space on your boot (SSD?) drive?Same issue with release version Xcode?How big is that project?If you just installed it, perhaps it's tied up downloading docs/etc. in the background?

Here's an example.I have a main fragment shader which callsA raytracer whch calls a...raymarch function which calls ...Five different mapping functions .. all of which call a common...Noise function.The noise function needs a texture and a sampler.Only the main fragment shader can see the texture and the sampler.So, I guess I have to create this big chain of parameter passing. Roughly 31 lines of code needed to be changed, just so that one function can get at a variable it needs.In C++ I can place variables at the global level. In MSL I cannot.I can see this is sort of pure. But it makes the code verbose, much more cluttered and way more expensive to make changes to.I hoped there would be a more elegant solution.

Problem solved.I got NO answer from filling out webforms/raising tickets, so I got on the phone after googling Apple Support, rang their 1300 number and within 2 minutes the person who answered had fixed the issue. Although they didn't go into details on what the actual issue was, it seemed like the automated initial provisioning had got stuck at a particular stage. The operator was able to rectify immediately.Thumbs down for the Apple web/email based support.A big thumbs up for Apple phone support.