Do I really have to download 4GB XCode just to update it from 4.0 to 4.0.2?
I updated my device to 4.3.1 and now I can't debug on it.
yes, you really have to. Unfortunately, Apple has no incremental updates.
If it makes you feel better, I updated to 4.0.1 in the morning and 4.0.2 was released that afternoon.
If you dont want to upgrade you should be able to change the version on your device using the Organizer. If you have the ipsw file you should be able to put the version you want on it.
It IS necessary. And while I do agree that some of the large updates from apple could be incremental, a lot of the changes are deep within the debugger and other areas, so while Xcode is 4GB as one download, an incremental update might only save you a few hundred mb depending on the changes. Incrimental updates may also take longer to create, but I'm not sure on that.
File it as a bug on radar.
I'm not kidding either -- I did, and I know a lot of people who did as well.
If you want to make some noise about this issue, that is the place to get heard.
Related
I am using the two finger swipe gesture to go back on Xcode a lot.
At least I used to because it seems to be broken since a few weeks now. Instead of going one step back, it now appears to jump two steps, making the feature completely unusable for me.
What I have tried:
restart Xcode
restart Mac
go through ~/Library/Developer/Xcode and delete or change various settings (getting desperate)
...but to no avail.
So I am starting to think that this my be an actual software bug in the particular Xcode version (I am using 12.5) but it seems unlikely because an issue like this should be easily caught by the engineer even before submitting the build to QA – just by the developer building the Xcode version, presumably with Xcode itself.
Does anyone else experience this? Is there some broken setting or cache that needs to be reset? Or can the hypothesis be backed up that this is indeed a software bug and all we can do is sit on our hands and try to reprogram years of muscle-memory to use control-command-left instead?
Xcode13 release fix it.
"methods
Additional bug fixes and stability improvements"
It appears that a large fraction of Tango users are experiencing issues since Leibniz was pushed out. I found this post in another thread and thought it might be why I am seeing so much instability in my app after the update:
This is from: TangoService_connectOnFrameAvailable() gets stuck or crashes using Google Tango Leibniz Release 1.10
"Apologies, that you are experiencing problems. Is this still happening? I am asking this because, there was a bit of leeway in timing between when the TangoCore was updated on PlayStore and when the OTA went out (which can potentially cause this issue, if OTA and TangoCore are mismatched). I just want to make sure that you are are updated on both TangoCore and OTA before diagnosing it. Also, make sure you have permissions for camera in the android manifestl." – r4ravi2008
I am pretty sure that the reason I am having problems is because I do have the mismatch described above. I have Tango Core updated through Google Play, but if I got to "About Tablet" I see:
Build number: KOT49H.150320
Also, my Kernel version has an updated date of Friday March 20th.
This build number is exactly the build number referenced here: https://developers.google.com/project-tango/hardware/depth-test
However, on this page it says that this build is for Kalman (not Leibniz). When I try the suggested step of going to "System Updates" and clicking "Check for Update" the system says that it is up to date (even though apparently it did not receive the latest OTA).
Two questions:
Am I correct in that Kernel (OTA) and project tango core are mismatched?
If so, how do I fix this?
Thanks in advance...
Apologies in advance as this is rather a comment than an answer to Voxel Scanner Voxxlr's post... But as I don't have 50 reputation points I cannot leave comments...
Well, like Mark I reset the device to factory settings and carefully updated everything (PlayStore, System Update)... Then, I made super sure that the correct tango_client_api.h/.so is used in my project... Et voila, suddenly it worked... Generally, it seems to be a good idea to spend as little time in the callbacks as possible... Otherwise you can observe these "hiccups" Mark is reporting... After considerable rearrangements in my code everything runs smoothly again... I can also confirm that the color frames are OK... If you are interested in my converter code: I posted it here link
My solution was to use a blunt instrument - force the Tango to do a full factory reset and let it start all over again- I can say that Explorer seems to work fine and the unity pointcloud and tracking samples work, but I'm just getting started and absolutely nothing in this statement should be misconstrued as an endorsement - remember, YMMV :-)
Yeah, no. The Unity Point Cloud sample hiccups all the time with respect to displaying point clouds, and crashes after a minute or two :-(
I believe so, I had similar problems where point cloud and motion tracking would get lost every couple seconds and eventually the app would crash. But just yesterday, my device said there was an update, while previous manual system checks kept saying it was up to date. After updating, the build number lists KOT49H.150414 (Kernel date is April 14, 2015), so that seems to be the actual Leibniz release on the device (not just the Core and SDK), and things are much more stable now.
Also just got the color data and displaying it like an AR image, but it's still in YUV format so everything is red. Working on converting it to RGB, but things seem to be working much better now.
Not sure if this technically qualifies as an answer, but I received this message from Google tango support:
Hi there,
What you are experiencing is a known bug that we have found fix too. Please stay tuned to our next OTA update that will fix this issue. We hope to push this update as soon as possible and thanks for your patience.
Best,
Monty
Project Tango Support
I am honestly not quite sure how to interpret this. What exactly is the bug? That my device won't download the latest OTA? Based on Brian's post, it really does seem that I have a mismatch between Tango Core and the kernel that needs to be remedied to get acceptable performance.
See Google+ Tango Page for info on the issue - there was an OTA update issue - it is being corrected
I am using latest xcode 4.2 and whenever I open existing project, it is going for indexing files, I am not able to stop it and my Macbook is going to busy with processing indexing... how can I stop it or let me know if any setting where we can avoid and get the all features like smart editor.
Thanks
Manu
check this question out...i think it will help. if not, you could try to disable ARC.
We have two different 'suites' of software: the windows-side software and the firmware. And, unfortunately, only certain versions of the windows-side software work with certain versions of the firmware.
For example, if a customer calls up with firmware version 10 we need an easy way for everyone (techs, developers, secretaries, etc) to know what this certain firmware works only with versions 12, 13, 14, and 15 of the windows software.
We have a wiki page just listing the versions and it worked fine, but there are enough 'hiccups' of people not following the process that we needs something a bit more forceful.
We have mercurial as a versioning system, but I can't see how this would be helpful for this problem (we are fine with forcing everyone to install hg).
Any ideas of programs / setups / anything that will help us alleviate the problem?
EDIT: So far most of the discussion is what I can do with the code from now on. I'm working on fixing that, too, but what can we do about all the previous releases where I can't go back and change any code? Thanks everyone for your help so far! Very appreciated!
To add to ChristopheD's comment, one way would be to make the software check the compatibility:
either through Internet (to download the latest updated list of compatible firmware and see if one of those version is present on the local computer)
or through a simple local text file if no WAN connection is available (which is easier to communicate and update than a full application release)
You might take a look at ClickOnce deployment. It allows more advanced configurations such as minimal versions. The deployment server might be on the internet or on the intranet.
I do think that you will have to change the implementation to solve this problem anyway. You cannot force an update (if you could that would be very virus-like)
I suddenly thought of this.
Think in the case of your software developed in .NET, and as well as the .NET framework (various versions). Maybe you want to follow that.
The client's host may be installed with firmware version 10 and 11; but your application requires firmware version 12. so your installer will download and install version 12.
However if your application requires firmware version 10, and the installed version is 12, maybe version 12 will also contain files from the previous versions (non-conflicting) and thus allowing the application (which requires version 10) to run from version 12.
I hate to answer my own question, but I wanted to mark something as the answer (it's ruining my perfect score!):
All that we did (and it ended up mostly fixing this problem) is rearranging the wiki so that if you wanted a windows version, you had to select which firmware you were using (and vice versa). I guess people ignore text enough, but forcing them to click on something was enough to get them to think.
I'm running ReSharper 4.1 and was wondering if anyone is using 4.5 beta? how stable is it, etc.
Also how do people feel about using beta VS plug-ins in general on work systems.
I switched to the 4.5 beta two days ago, and for me at least, their claims of less memory usage are valid. I actually had to request a new computer because things were slowing to a crawl, and it looks like it was ReSharper causing it. 2GB of RAM fully used and constantly swapping out to the page file.
Of course, our solution has 92 projects in it, so it's not entirely their fault, but the point is, the beta seems very stable to me, but YMMV.
I installed it a few days ago, I've had Visual Studio freeze and crash on me three times and each time the only thing that would show up is the message "Parsing Source Files" from ReSharper. I'm not sure if the problem is the solution or the plugin, but other than that it is very stable, and much faster than 4.1.
I actually prefer using beta's on my development system because unlike my home computer I actually take care to protect my work and back it up. Not much harm running a beta plugin can do that I can't undo immediately.
i switched to beta and it has better performance than before.. you should try it.
We have been using the ReSharper 4.5 beta here with no problems. There is a noticeable difference in load time with 4.5, much faster. I highly recommended updating.