Before submitting a bug report or questions please carefully review the contents of the page. If this does not help, feel free to follow the link at the bottom of the page to contact us.

When you open the App Store on your device, you are automatically notified if there are updates available for any of your installed applications. If you are unsure, you can click the Updates button on the bottom right.

You install updates the same way you install new applications. Simply click "Free" and then click "Install".

Sometimes shutting down your iPhone or iPod touch and restarting it can resolve problems with crashing applications. This is common to all applications, including Apple provided ones. It is a good first step in resolving the problem.

To Reset:

• hold down the screen lock button until you see "slide to power off" on your screen.
• Slide the indicated area and wait for your device to completely power off.
• Hold down the screen lock button again until the device turns back on.

If your application continues to crash, please contact us. We strive to make our applications stable and will do whatever we can to resolve the problem. Any information you can give us to reproduce the problem will help greatly.

Good information to include:

• Are you using an iPhone (3G / 3GS) or iPod Touch (1st / 2nd generation)?
• What version of the device system software are you on (2.0, 2.1, 2.2, or 3.0)? This can be found under Settings > General > About > Version.
• A description of how to reproduce the problem (what menus you opened, text you entered, etc.).

If the game does not seem to be running smoothly, try closing and opening the application a few times. Your game will be saved automatically and you can continue upon re-opening. Locking and un-locking the screen may also do the trick.

This is a common problem on 3.0 devices, particularly the iPhone 3GS. If you are running 3.0 please upgrade to 3.1. This free upgrade includes OpenGL performance fixes.

Opening the OpenFeint dashboard on an iPhone 3GS can cause the game to run slowly for the remainder of the session. This is related to bug mentioned in the previous question. Please follow the aforementioned steps for a work-around.