Ralf Rottmann's dashboard

J, I'm sorry that you've got an issue with the iMiles app for the iPhone. Could you please take a look at this thread

http://getsatisfaction.com/grandcentr...

and respond here. We'll involve Engineering asap to get things sorted out.

Also: Could you please send the email you've used to register to support@planetimiles.com .

Thanks!

We are sad to see that iMiles seems to not work as expected on your device.

The application has undergone exhaustive beta testing and we never experienced the crashes you are reporting. Given that we have not yet been aware of the problems it is extremely valuable for us, to get your feedback and nail this down to the root cause.

But: We do need your help!

Some initial questions:

- Which exact iPhone OS version are you running? (Settings > General > About > Version)
- Do you have a regular iPhone or did you apply any jailbreak / unlock?
- Did you allow Push Notifications on the very first start of the app or decline?

Finally: In order to identify what exactly caused the crash, please include iPhone Crash Reports with your next response. These crash reports will allow us to identify the exact source code line which caused the crash on your device. Without the reports, it's almost impossible for us, to further track down the root cause.

Here is how you can access those reports:

When an application crashes on the iPhone or iPod touch, a "crash report" is stored on the device. Crash reports describe the conditions under which the application terminated, in most cases including a complete stack trace for each executing thread, and are typically very useful for debugging issues in the application.

When you synchronize your device using iTunes, crash reports are copied to a directory on your computer.

Getting crash reports requires your cooperation. Specifically, you will need to retrieve the crash report from the directory where it was copied by iTunes.

Depending on the platform, the directory is:
• Mac OS X Leopard & Snow Leopard:
~/Library/Logs/CrashReporter/MobileDevice/<device_name>

• Windows XP:
C:\Documents and Settings\<username>\Application Data\AppleComputer\Logs\CrashReporter\MobileDevice\<device_name>

• Windows Vista:
Windows Vista: C:\Users\<username>\AppData\Roaming\Apple Computer\Logs\CrashReporter\MobileDevice\<device_name>

<username> is your login name for the computer. <device_name> is the name of the iPod touch or iPhone, for example, "John's iPhone".

We are only interested in .crash files. The crash report's file name begins with the application name and contains date/time information. In addition, <device_name> will appear at the end of the file name, before the extension.

Please zip the reports and attach them to your next response.</device_name></device_name></username></device_name></username></device_name></username></device_name>

So, who are you?

Thanks for contributing to the iMiles user community, Sander!

We wanted to keep the initial version of iMiles as simple as possible, therefore the only performance indicator iMiles takes into account is distance – at least for the moment.

The idea of integrating country points into the equation is definitely interesting.

The next steps on our roadmap mostly address opening up the iMiles platform for affiliates and location providers, so you will likely not see country points in the *very* near future. But: We've put it on our backlog of cool ideas.

So it's not at all off the table!

iMiles Version 1.2 (planned for 2nd half of December 2009) will add options to post Google Maps and more detailed location information to your Facebook profile, though. So you can at least let your bodies know where you've been!

Version 1.0 of the iMiles application for the iPhone tries to get your location as precisely as possible.

In some situations (inside buildings, etc.) or when you try to swipe your iMiles card while you're moving fast, the iPhone's GPS module does not deliver accurate results.

In Version 1.0 this can cause the iMiles application to wait for GPS updates "forever". You then have to manually stop the process by tapping the "Cancel" button.

In Version 1.1 which is in Apple Review, as of this writing, we've added two features to resolve this issue:

1. The maximum time the app will try to get GPS updates is 10 seconds. If no accurate GPS info is received within 10 seconds, the app aborts the process and informs you.

2. In case you're in a region with a weak GPS signal, you can lower the required accuracy. Open the iPhone's Settings application and change the "GPS Accuracy" to "Low".

Note: Lower GPS Accuracy might result into less precise location detection but it'll allow you to use iMiles even in weak GPS signal situations.

Version 1.2 of the iMiles iPhone application will automatically cache your swipes in case no data connection is available.

Once you reconnect when you're back home, the cached updates will automatically be transmitted to the iMiles affiliate system and your miles will be granted.

Good idea, thanks for your feedback.

We will release a version targeted at the Android (1.x and 2.0) platform soon. Symbian is currently under consideration.

We might offer a Web based version before. HTML5 does provide access to the current location via JavaScript, so this might be next.

We let you know once the status for Symbian changes to "planned".

Ryan, were you able to make the change for me?

Thanks, Ryan. Can you change my default community to be The Next Web, please.

Also: Will you add the ability to post into the right community when running on more than one somewhere in the future?