General BETA F.A.Q.

How do I get more information on errors/How can I help diagnose bugs?
The BETA versions of our plug-ins have logging built-in. It would be extremely helpful if you include a copy of the log when corresponding with us about problems you are experiencing. Logs can be viewed using Console (located in Applications - Utilities). Including the log output in your support request by copying and pasting it into a text file you attach to your email will help us track down the root cause of the problems you encounter during the BETA period.

How do I report bugs and crashes?
If you encounter any unexpected behavior while BETA testing, we ask that you send us a bug report via email. To assist us in tracking down the bug, we ask that you go to the BETA page for the plug-in you are testing and use the bug link (located on the right). to report.
Tips for reporting:

  • Use the subject line--having descriptive text in the subject line is incredibly useful for us, and will help ensure your issue is addressed promptly. (This is a really good place to indicate whether you're using the Aperture or iPhoto version of the BETA.)
  • Include version numbers--different versions of an application or operating system might handle the same code, well, differently. Thus, it is essential that you include the BETA, program (Aperture or iPhoto), and OS X version numbers you are using.
  • Send us your Console log--this can not be over-stressed (which is why we're mentioning it again).
  • Check out the Activity Monitor--like Console, Activity Monitor is a Utility included with OS X (located in Applications - Utilities) that will have some very useful diagnostic information if the BETA hangs (i.e., becomes unresponsive while showing you the spinning beach ball). In Activity Monitor, select the program you are using (Aperture or iPhoto) from the list of processes (it'll probably be highlighted in red), and click Inspect. A new window should appear. Clicking the Sample button in this new window will generate a text output that you'll be able to save and attach to your bug report.
  • Send in your crash log--each time a program on your Mac crashes (i.e., shuts down unexpectedly) a crash log is automatically generated. Crash logs can be found at the following path: home - Library - Logs - CrashReporter - name of application.

This may seem like a lot for you to do, but including this information will go a long way in ensuring the problems you encounter get fixed.

Can I submit any feature requests?
We'd love it if you did. Just drop us a note by going to the BETA page for the plug-in you are testing and click on the Feedback link. While there's no guarantee we'll be able to implement all of the requests that are sent our way during a BETA, we will keep them around for future releases.

Could my images be lost or corrupted by using the BETA version of the plug-in?
BETA versions of products are, by definition, unfinished. Thus, anytime you use a BETA, there is a small possibility that the data you use to test the product will become lost or damaged. While we've made every effort to minimize this risk, you should take it into consideration prior to participating in any BETA test. That being said, there are some simple steps you can take to protect your data.

  • Never use irreplaceable files for BETA testing--always ensure the files you will be using are backed up prior to testing.
  • Always work in a test environment--when testing plug-ins that connect to other services (such as our Gallery and Picasa Web Albums plug-ins) you are strongly urged to create a secondary account so that, in the event of a serious issue, your primary account will not be impacted.