smb big sur

Having read the rest of the thread I see you've obtained a new system and it works fine there. You might want to check the type of connection you have between your test device and the machine. Did you use the same network/wifi setup in both environments? After that I would un-install and re-install XCode. If that doesn't do it then I'd do a re-install of the OS and see what that does. I worked with iCloud for our latest app and anything more than 5 seconds would be way out of line. In fact even that would be pusing it. Most often the first contact with the database was something less than two seconds and subsequent operations after that were measured in milliseconds.As you've discovered the CKAsset type does take considerably longer than others, this is to be expected since it not only downloads the record but the file itself. Naturally your connection speed will have an effect and the overhead that XCode requires to track statement execution also affects the speed at which you will see things in the log. Wor

And as an addition to my earlier post, Apple also would be well-served to bring back a real enterprise hardware offering, such as server hardware that is suited to run in corporate data centers. This offering does not have to look like the XServe, but it should be an updated server that is designed for both corporate data centers, as well as hybrid cloud setups. Apple is very much an enterprise technology company today, so any comparisons to what Apple was like in the 1980s and 1990s, and even into the 2000s, are unfounded.Apple's big blunder in times past, was to make proprietary systems that could not interoperate with other systems very well. They walled themselves off, and did not make it easy to interconnect Apple devices with those of other companies. Yes, today, iOS devices are much more closed off than their Mac counterparts, but even there, iOS devices can connect to standard Wi-Fi networks, and can be managed with standard MDM offerings, which in effect, makes them a lot less proprietary th

This is a big problem for many Devs throughout much of the world. There are quite a few other threads here on the subject.One workaround is to use a VPN for the UK or Germany (two of the few places for which iTC still works)Or you can try the workaround given by Matthew Lenton on his Twitter Feed:twitter.com/psyclr/status/623099998687789057I'm sure he's tried to post his workaround here, but he probably included links to the before and after pics in his post, which would have sent it into moderation (a state of limbo that can last many days).It's been confirmed as working on 9to5mac.com (It has it's own article). The pictures are a little hard to read due to being low res, but basically:Open https://itunesconnect.apple.com in ChromeUse the built-in JavaScript debugger in Chrome Developer Tools under the Sources tab.Look at page-wrapper_cntrl.jsAdd break-point at line 29 of the script (or earlier)Reload pageRemove line 46 });In line 32, substitute data.data; with {};Remove line 31 Unpause the debugger

I experience this problem too.I add a new language for my app in itunesconnect and click in the Save button. It shows the errorWe're temporarily unable to save your changes. Please try again later.Then I delete all images that are copied from the English language(the main language that I used). After that I click in the save button, then it works, but this is a big problem, I need to re-add all images again in the new language, this process must be repeated for each new language that you add. If you want to use the English screenshots, you need to readd all of them in all 5 sizes(4.7, 5.5, 4, 3.5, ipad)

I agree, it's all changed and seems like a big incomprehensible mess to me. And when clicking on a '?' to find out what something means it shows nothing but the label next to it - completely useless. :-(

Mine the same. Installed very fast, but spin forever when launched.At least now it installed fast, and that's a big improvement. 🙂Now have to spend another 2 weeks doing Android Wear development instead. 😟

I had to restart and re-download a few times. Big waste of time but it works.

Not sure why people are asking about QA - its a developer beta (as usual).Each beta addresses some bugs - some fixes may cause other bugs or they may just be focusing on specific things in a specific beta - this is why there is a big statement to say only install in development devices. People do really seem to think that a beta is just a pre release version. In development terms beta is where all the main work is done and its just for findingt and fixing bugs.From my experience in fact its all much smoother and is certainly better than beta 2