Amen

Same here. It has been rock-solid from day one. I have 4,800 profiles in my collection and I've not had a single crash or glitch and I update it almost daily.

I agree.  Click on the Contact Us link at the bottom of this page and create a support ticket.

The app has been running smoothly for me on both my iPad and iPhone.

Very stable here, on both iPhone4 and iPad.

Suggest you run a database repair and then re-sync.

On my iPod Touch (3rd gen.), the app crashes very often (I would say about half the time). But only when I launch it, never during use.

I have to restart it 2 or 3 times before I can use it.

Latest build is running very stable here on both iPhone4 & iPad, both with the latest firmware

As someone who can crash the program consistently within 30 seconds, I'm amazed too. I have around 2000 titles and have used the Windows version for several years. I also have 31 years experience with computers and run a software company. I'm stating those facts because I want everyone to understand that I'm definitely a highly experienced computer person, so it's not an ID10T error or a PEBKAC issue. I have an open case with Invelos and made my database available for download quite some time ago, yet my issue remains "in queue" with no updated feedback.

Just because a program works great for the masses doesn't mean it is perfect. If a full backup were provided along with detailed steps for producing an issue, I would expect my programming staff to nail down the problem quickly, yet I have been waiting, and waiting, and waiting for my first stable release of this software. Is anyone looking into this or, because the majority of users say it runs fine, are the exceptions being ignored?

I would be thrilled beyond belief to have a reliable version running on my iPad. To date, I don't, and it is very discouraging not to hear back from anyone. Did you guys get my database? Did you make it local? Did it then start crashing as I described? It'd be nice to know what's happening, if anything. It'd be nice to get a working 1.14 or 1.15 before a bunch of new features.

So, it works for you. Great. It doesn't work for me. I've reported, I've shared error logs, I've shared my database, I've waited and waited. Now what?

Quoting Dr. Killpatient:

Quote:
Have you tried restoring your database into a new one and syncing that new one to the iOS device? I've seen issues that don't fix from a DB repair but do fix from a DB restore.

I'm thinking the same thing.  If I had to guess, I would say the issues stem from some problem with the database.  It's the most logical reason I can think of that it works so well for so many people but fails for a few here and there.

I see you've been here at the new forums for quite some time.  So I'm guessing you've been using the desktop version for quite some time.  I know from writing plug-ins that people can have very strange things in their database.  The only way to find them was to walk though my code in the debugger with their collections to figure out where it was failing and why.  Then I was able to program around those weird anomalies.

While you wait, you might want to look at the Database Query plug-in.  There are plenty of tools there that are meant to find issues with your database.  It's an annoying solution to problem.  But it may be quicker than waiting.  Or it may find nothing out of sorts and you've wasted a bunch of time.  But it certainly doesn't hurt to at least check.  Especially since your ticket seems to be making no progress at this time!