Proxi Blog

5 Responses to “Proxi v1.2 released”

1. Justin Sako Says:
   July 19th, 2006 at 7:57 am

   Is anyone else having this problem?

   I have now had this problem twice and I don’t know what to do to correct it. The first time, I inadvertently installed an old version of Proxi instead of the (then) recently announced version 1.0. I think it may have been 0.2, but I’m not sure. Anyway, after correcting my mistake and upgrading to the 1.0 version, I found that the only “Trigger” that would appear in the Components window is “AppleScript” and the only “Task” that would appear was “Store Value”. I tried several times to get rid of all of the Proxi files and reinstall, but nothing helped. I ended up playing with Proxi a little on another computer, but I really want it on my MacBook Pro as it is my primary computer.

   So, after sending my MacBook Pro back to Apple for an expanding battery problem, I decided to wipe it when it came back and install from scratch. After doing this, I was able to install version 1.1 and it seemed to work fine, with all of the Triggers and Tasks appearing. This is a busy time of year for me and I didn’t get to do much with it, but when I saw that version 1.2 was available, I figured I should update. To my chagrin, I now have the same problem that I had before (”AppleScript” and “Store Value” are the only things that show up in the Components window).

   I have tried uninstalling Proxi with the instructions on the blog and reinstalling (both version 1.1 and 1.2). I have tried uninstalling, rebooting and reinstalling with no luck either. I don’t know if the “Triggers” and “Tasks” are little files that I should be able to find somewhere on the hard drive or if they only exist internally to the program. I am at a loss for what to try next.

   The only thing that I can think of that I could offer as a possible source to the problem is that I have Little Snitch installed and I probably told it to “deny until quit” when Proxi first launched and wanted to contact the mother ship (as I am in the habit of not letting outgoing communications take place until I am comfortable with the new software) and this may have screwed something up.

   Any assistance/ideas you can come up with would be much appreciated as I really would like to start using Proxi on my MacBook Pro without having to rebuild it from scratch again.

   Thanks.

2. Casey Says:
   July 19th, 2006 at 10:38 am

   Hey Justin, sorry to hear about the troubles your having with Proxi. Let me start off by saying the “phone home” mechanism is simply a check of the RSS feed for updates so I don’t imagine that could be the cause of the troubles.

   Proxi is broken down into a few components. The app itself doesn’t know a great deal and almost all of the functionality (triggers and tasks) are located in a separate file in /Library/Application Support/Proxi/PlugIns/ProxiCore.bundle. If this file is not installed, Proxi will launch as you described with only a couple of built in triggers and tasks. I’m not certain why this file wouldn’t get installed though. Perhaps there is a permissions issue at /Library/Application Support… then again, the Proxi installer is suppose to run with Administrator priviledges so this shouldn’t be a concern. Just to be sure, you could try installing while logged in as an administrator, perhaps that is something amiss with the installer?

   Please keep me posted on your progress I’m anxious to get to the root of the problem. I’ll let you know if anything else comes to mind.

   One other note: Most of the development and testing for Proxi is also done MacBook Pro, so we should be able to eliminate that particular platform as being involved somehow in the problem.

3. Justin Sako Says:
   July 19th, 2006 at 10:38 pm

   Casey -

   Thanks for taking the time to help me with this. I looked, and the ProxiCore.bundle file is where it should be and is version 1.2 from 7/12/2006. I tried deleting the file and reinstalling, but still no triggers and tasks, even after making sure the file was there again.

   So, I decided to try your suggestion (even though my account for daily use is currently–and has been–an admin account). I uninstalled Proxi as described on the Wiki, but I also removed the Proxi.pkg file from the /Library/Receipts directory. I logged in as the original administrator account and installed Proxi 1.2 from there. Darned if all of the triggers and tasks didn’t show up. Hooray, I thought, and logged out and back into my daily account, only to find that the triggers and tasks are still missing. Just for grins, I created another (non-admin) account and logged into that account. The new account had all of the tasks and triggers in the Components window just like it should.

   I have to guess that there is something left over in my daily use account that is preventing the triggers and tasks from showing up. Are there any other files (not mentioned in the uninstall directions) that are used by Proxi when it is running? I’ll do some poking around, but if you have any suggestions I’d appreciate them very much.

   Thanks.

4. Justin Sako Says:
   July 19th, 2006 at 11:29 pm

   I added the following files to the “uninstall” wiki entry:
   ~/Library/Caches/Proxi
   ~/Library/Application Support/Growl/Tickets/Proxi.growlTicket
   /Library/Receipts/Proxi.pkg

   and I’ve tried removing these before reinstalling, but the triggers and tasks still do not show up in my daily use account.

   Any ideas?

5. Casey Says:
   July 24th, 2006 at 10:24 am

   Hey Justin,

   Sorry for the delay, I’ve been out of the office. Unfortunately I’m completely bewildered by the symptoms you’re describing. Out of curiosity, you might try version 1.1 and see if it exhibits the same behavior. If not then we can narrow it down to some problem with the installer itself.

Leave a Reply

Name (required)

Mail (will not be published) (required)

Website