Firefox Composer package generates keychain errors

nadams
New Contributor III

Hi All,

Yesterday I built a Firefox installer package with Composer. FF version is 49.0.1 (latest). I installed it, launched it, cleared the prompts about importing from other browsers, and the check for default browser. Set the homepage and called it a day.

When I install the package created by Composer, I now get two keychain errors on login.

A keychain cannot be found to store "MiniBuddyUser."
A keychain cannot be found to store "localdevicef1cecfc1-9fc5-57d3-9a21-50d4d7db5414-AuthToken."

When I look at the composer package it appears to just have preference files in it, so I'm not sure where the keychain info is coming from.

Any insight?

6 REPLIES 6

mpermann
Valued Contributor II

@nadams what all did you capture with Composer? Can you show a screen shot of what you captured in Composer? That may help us figure out what's going on.

mpermann
Valued Contributor II

@nadams what all did you capture with Composer? Can you show a screen shot of what you captured in Composer? That may help us figure out what's going on.

nadams
New Contributor III

@mpermann Sure, see attached. The Firefox profile is where the bulk of the preferences are stored.

9aafefc359eb4ce4a72ae376269307d0
60bfb7693b2d4ba7b89b677b2b037615
6aed37eaaa014ac29a156dc8dea2ebaf

mpermann
Valued Contributor II

@nadams you probably won't want the following items in the install package:
Containers folder and everything in it
Logs folder and everything in it
Preferences -> Adobe folder
com.apple.diskimages.fsck
com.apple.frameworks.diskimages.diuiagent.plist

I think some folks would say capturing the ~/Library/Application Support/Firefox folder might not be the best idea. They would suggest other methods of tweaking a Firefox install like using CCK2. If you only plan to deploy this package at imaging time you can probably get away with capturing the entire Firefox folder. But if you plan to use this to upgrade people that already have a version of Firefox installed you are going to be adding stuff or potentially writing over some of their configuration files. Which will make your users grumpy. I have captured the ~/Library/Application Support/Firefox separately and used it as a starting point for new computers/users and it's worked fine. But the only tweaking I've done in that profile involves setting the default homepage. I never ran into the issue you're running into. What all are you changing in Firefox before you quit and finish the snapshot?

nadams
New Contributor III

@mpermann I installed FF, launched it, selected the option not to import anything from other browsers, deselected the default browser option, and chose to not have it check in the future. I then went into preferences, set the default home page, and changed the search engine from Yahoo to Google. As far as I recall, that was it.

This package will only be used to install FF on computers that do not already have it, as well as adding it to our post-image process.

Thanks for your help so far!

mpermann
Valued Contributor II

@nadams my Firefox folder template that I've captured in Composer looks like the below. I've not run into the keychain issue when using this as a starting point on a freshly imaged computer. 0ae2b6c535154624b5dda9758194d3d6