Xcode 4.0.1 was released a few days ago, which means that I am once again downloading the 4.5 GB beast to update. Does anyone know if Apple plans to introduce a better update system?
I wait for a torrent these days. Not quite as frustrating as getting it 80% of the way downloaded and losing connection.
If you are registered apple user then u can download directly from apple site,otherwise you need to get it from torrent. like www.thepiratebay.org etc
Since 4.3 the whole Xcode toolchain is bundled into a single Mac App Store application. The Mac App Store supports delta updates and the update to 4.3.1 that I’m downloading right now is ~900M, compared to ~1.5G for the whole app. So it looks like the update sizes are finally coming down, if slowly.
Related
I'm trying to find the Metrics Launch Time of my app by using Xcode Organizer but it does not show the result of the 3 most recent versions. Only for older versions.
I'm using Xcode 12.2 (12B45b), and even after upgrade to 12.3 (12C33), still doesn't work!
Does anyone run into the same problem and know how to fix it?
TLDR: Versions with limited usage will not appear in the Xcode Organizer Metrics.
We were curious why this is happening to our app aswell. We had 52 releases in 2021 and the Battery Usage section from Xcode Organiser Metrics menu shows us only 5 of them, while Scrolling section shows only 4 at the moment of writing this answer.
After doing some research and watching this WWDC20 session on Diagnose performance issues with the Xcode Organizer I have learned that apple is using some usage threshold for each version of the app to determine wether it should show up in the metrics or not. According to the linked session, in Xcode 12 they have lowered the required usage threshold by a factor of five.
Another thing is that now you will see a limited usage icon attached to versions which have passed the new threshold but their usage is still low enough so you will need to be aware of the margin or error while analysing those metrics.
So even though the threshold have been lowered, it's still not really helpful If you update the app often like we do. Which is sad since we are not really able to provide improvements to these metrics since we do not really know with what we are dealing with. Let's hope future versions of Xcode will at more information about how much usage is enough, because apparently tens of thousands of users on a version are literally not enough for it to be included on a list.
Resources:
Diagnose performance issues with the Xcode Organizer
We're trying to automate the release of our app to the Mac App Store. I've been trying to achieve this using fastlane. I managed to get this tool working for submitting the apps' metadata (release notes, screenshots etc).
I can also build the app using the gym module, however this results in a .app and not in a .pkg that is needed for submission to the App Store. Even when I use
export_method: "package"
I cannot imagine I'm the only one trying to achieve this, but I cannot find an answer if it is possible at all. And if possible, how to achieve this.
I have a (old) work in progress PR made for this - https://github.com/fastlane/fastlane/pull/12195. Majority of our users are mobile so it has been hard for me to get testing on this :). If you'd like to comment on that PR I would be happy to revive it and work with you on making this work for you!
TestFlight is a welcome change for iOS. It makes distributing beta versions painless for both the developer and the testers.
Does Apple support TestFlight for Mac OS as well? I've done quite a bit of searching and haven't found anything conclusive one way or the other.
We have an OS X app store app that turns out to have an install problem with Yosemite. We failed to do a first install test against Yosemite, so we missed the problem.
I developed a fix and would love to have some new users try it out. It's petty complex, difficult and disruptive to have current users delete the entire "container" directory and kill the preferences process in order to simulate a fresh install.
I also don't like the idea of distributing an unlocked version of our app. If that gets out, it could damage sales of the app store app.
I've done things like added an expiration date to a test app (weak protection) or created developer ID builds that will only run on machines from a specific list of MAC addresses. The last approach works, but it's tedious and painful to maintain, and requires that the tester give up uniquely identifiable information about their machines.
I'd really like the ability to create apps that will only run on beta tester's machines, like TestFlight does for iOS.
This is a developer question more than a code question. It isn't a great fit for SO, but I can't think of a better Stack Exchange site to post it. If anybody has a suggestion of a better site to post the question I'm happy to move it there.
This document at Apple Developer explains it.
It says you should register the testers' devices and generate a provisioning profile that includes them. Which means, theoretically, the app won't run on any device not in the list.
Here is the strange thing about it however: I have two Mac computers and I didn't register either of them with my provisioning profile (in fact the list of registered devices is empty right now), but I can run the exported app image on both easily. The app is sandboxed and signed, ready for App Store distribution, but nevertheless it runs on unregistered computers. It might be that with an empty device list it allows to run on any, or it might be that I'm doing something wrong with code signing.
I will update the answer once I figure this out.
Good news for everyone (including me) waiting for TestFlight for Mac - it just got announced on WWDC21.
Unfortunately, it might take another few months until it is out of beta and publicly available for everyone. But since this question is almost more than 6 years old, its just a fraction!
I"ll update the answer if there are more details available
Update
TestFlight on Mac will be available to download on the Mac App Store. It will be similar to the iOS version of TestFlight offering almost the same functionality to both developers and testers.
It supports both native Mac apps and iOS apps on Apple Silicon!
It is now available.
TestFlight is not available for Mac apps.
source: https://testflight.apple.com/
😕
A few system updates ago I had trouble receiving the OTA for the Tango. It appears that a similar problem has occurred again.
My Tango core has successfully updated to the Pythagoras revision, but my kernel version still reads build KOT49H.150505. I have tried the obvious things such as clicking on "check for updates" in the "About tablet" settings menu, but I still get that my system is up to date.
On the developer release notes it says that the kernel build should be KOT49H.150609.
A couple of questions, has anyone successfully downloaded the latest OTA? How can I get my tablet to download this new kernel version?
I am worried about this mismatch between tango core and OTA since last time it rendered the tango basically unusable. This time around things seem to be relatively stable, but I am worried that perhaps there might be performance degradation.
New device unboxed a couple of days ago. Cannot use OTA to upgrade, says current software is up to date even though it is not. Without a current kernel I cannot download tango core, etc. So the device is basically non-functional (other than a plain tablet :-)) out of the box.
Same problem as this question:
Cannot update Tango Core - "Package file was not signed correctly"
Factory resets did not fix the problem. Unlike the previous question, waiting 48 hours provided no resolution. Several users on the Google+ developer group are having similar issues with this batch of devices, so this seems to be a common problem
Thanks!
We had an error in our OTA server configuration that we fixed this morning. This might take some time to propagate, but you should start seeing updates soon. Sorry for the inconvenience!