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
Related
I am testing an Android GPS tracking application in the Emulator and I am running into a problem when trying to figure out if the last known location is stale or not. Getting the system time gives me the correct time, but when I call location.getTime() for the last known location the time returned is off by a few hours. I did some more testing and found out that every time I send a GPS location from the Emulator control tab in Eclipse (similar to geo fix), the location's time is advanced by one second. This makes no sense at all! I would appreciate any insights into this problem.
As discussed this appears to be a bug in the emulator (I was able to repeat it as well). I filed a bug report at https://code.google.com/p/android/issues/detail?id=27272 if anyone wants to add details, star it, and/or follow along.
This bug has been fixed in the ToT dev branch for API 26. We will cherry-pick this fix to other branches and hopefully the public available system images will see the bug fix in the near future.
If any issue persists, please report at Google issue tracker they will re-open to examine.
I have just compiled an existing app with the latest SDK 5.4.0 GA and was surprised to see some weird issues that look like performance issues but I am not sure.
I use an activity indicator (Ti.UI.createActivityIndicator) while time consuming things like loading data in memory or fetching data from the app server take place, and with the new SDK the animation is really choppy. The same app under the exact same conditions but compiled with 5.3.1 GA shows the activity indicator nice and smooth so it is something related to the 5.4.0 GA.
Any idea what it might be and if this is a bug or something I might need to change in terms of configuration?
I have tried switching the run-on-main-thread property but it had no impact.
The overall performance of the app does not appear to be impacted - hard to tell really.
No such issues with iOS.
Any suggestions?
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.
I have a very strange problem with Apple Watch simulator in Xcode 8.3
The problem is with clicking buttons. The simulator detects feel completely in a different place than it is the button. Does anyone has the same problem?
Regards,
Mateusz
UPDATE: This is fixed in the latest betas.
Go download it from the Apple Developer Center.
Couple of things here…
First off, Xcode 8.3 is still in beta, so you're technically not supposed to be discussing things about it here. Instead, use the official Apple Developer Forums. Apple's own developers frequently respond to questions there, so it's a great resource. Take advantage of it.
Second, there's really not much we can do about it this. It's a bug. If you're having troubles, let Apple know, not us.
File a radar at bugreport.apple.com. When more developers report a certain bug, it gets its priority raised, which prompts Apple to fix it sooner.
See this article for more details.
To benefit us all, be a good developer citizen and file radars whenever you find a bug.
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.