JCLM Software LLC Apps and more

Camera Vault 3.5

Several users pointed out various issues with the last release of Camera Vault 3.4.  In particular, users running iOS version 3.1.3 were unable to open the application.  Other users pointed out issues exporting multiple images to their photo library, as well as exporting images that were still being processed.

While version 3.4 was, in general, an improvement over 3.3, I have been aiming to continually improve the application's stability.  With this in mind, I have uploaded version 3.5 to Apple and hope it will be released later this week or early next week.  Over the next several weeks, I will continue monitoring user feedback and reports to focus on improving stability even further.  Once the application has achieved a high level of stability, I intend to continue adding new features.  In the meantime, please be patient and upgrade whenever convenient.

Thank you, all Camera Vault users, for your support.

Camera Vault Settings Issue and Camera Vault 3.4

A kind user has pointed out an issue in the latest Camera Vault regarding Settings.  In particular, the Settings screen is not opening correctly, which prevents editing the passcode, among other important items.

Today I will be correcting this issue and sending Camera Vault 3.4 to Apple for review as an upgrade.  Thank you for your patience, and please continue to let me know if there are any issues discovered in this or any other version of Camera Vault.

Camera Vault 3.3 Pending Release, More

It has been a little while since I've been able to pull everything together into a new release, and I'll apologize for how overdue it is.  First, let me thank all my users, even those who hated my apps and immediately deleted them.  I'm not one of those types that can create something and simply enjoy the fact that it exists, like some hidden artwork or tree falling in the forest.  I sincerely appreciate anyone who even looks at the pictures of my apps, let alone those who use my apps day to day.  To all of you, a big thank you!

Now, that said, I'm releasing a series of updates to my applications.  For some of them, like SeekCache EZ Loan Calc, there are minor bug fixes and not much in the way of enhancements.  I like to think stability is still a good reason to release an update, even if everyone says "bug fixes" in their update information.

Camera Vault 3.3, however, does include some new error tracking enhancements.  One detects when an image has become corrupted.  Occasionally, there may be times when an image is not saved properly - perhaps the application is closed before it's finished, or an issue with the application misplaces a few bytes of data.  Whatever the cause, this can sometimes lead the application to crash when it tries to process the image, and since it retries processing until an image is processed, this may crash the application forever.  This new enhancement stops this endless cycle after two attempts to process an image.  If your application has been crashing, load it twice more and see if it can recover from the problem.

Another addition to Camera Vault involves error reporting.  To help me track down problems faster, you might be prompted to send in error reports.  There is no information included to identify you individually, though some phone information is sent to help debug problems.  Again, no private information is sent - no pictures, no passcodes, nothing.  You only benefit yourself by sending in error logs.

If anyone likes what they see, I thrive off of positive criticism and the occasional bit of praise, so please email whenever you'd like, or post something nice on iTunes.

Thanks and good day!

Camera Vault 3.2 Pending Review

Last night, another upgrade to Camera Vault was sent to Apple for review.  This update resolves a few more issues reported by users and adds a fall-back for the image import feature.  If the application can not load photo library information into the more advanced import screen provided in the 3.0 update, it will switch to using the old method from earlier versions.

After much research and support from users, it appears that a majority of the problem lies in how Apple has designed the iOS4 operating system.  To avoid being too technical, I will simply say that Camera Vault's access to the Photo Library, which is important for advanced features in the Import functionality, is allowed or disallowed based on whether you have opted to let Camera Vault determine your location.  If you answered "No" to letting Camera Vault know your location, it will also not be given access to your photo library, which in turn prevents anything from appearing on the screen.  This seems to be an odd and misleading aspect in iOS4.

Keep in mind that Camera Vault uses your location when you take pictures to record the location the picture was taken at.  If you would like to test a work around, at least temporarily, or if you would like to adjust how Camera Vault detects location, you can adjust your location permissions via the Settings application, under General > Location Services > Camera Vault.

I would like to thank all my users for their patience and apologize again for the rampant trouble it has caused.  I would also like to send out extra thanks to those users patient enough to answer my questions and provide me with information about the problems they have seen.

Camera Vault 3.1 Update

The Camera Vault 3.1 update was released yesterday with the aim of resolving a few issues users have been having, particularly an issue importing images.  Unfortunately, this issue is still affecting some users and another release will need to address these issues.

As a small time developer, sometimes it is difficult to reproduce issues that users are seeing due to the variations in devices, versions of iOS, and even phone configurations.  Because of this, some releases may have flaws some users experience that will take some time to iron out completely.  I apologize for this, especially in times like this when a resolution is elusive.

The Camera Vault 3.0 update was a large project with changes touching on many aspects of the application.  The goal was to create a foundation for adding the features users want most, while also standing as a great improvement over the older 2.x releases.  While the problems users are currently experiencing certainly detract from the update and damage the reputation of Camera Vault, I am confident that the issue will be resolved soon and the improvements provided by the update will become more apparent.

Let me thank every one of my users, who support me and my development of Camera Vault, and who are patient and help me troubleshoot the reported problems.

Camera Vault updated – but with an issue

There was recently a major update to the Camera Vault application aimed at improving the user experience, providing high definition graphics, and revising how users manage media.  It also laid the foundation for such project as adding support for video, or improving the camera's functionality.

However, users have pointed out a serious flaw in this new update that did not appear during standard testing due to an anomaly in the testing device.  Specifically, users are not able to import images from the iOS standard library because the screen appears blank.  This flaw has been recognized and an update aimed at fixing it has already been sent to Apple to be released, but in the meantime, users can work around the problem by copying images from the standard library and pasting them into Camera Vault.

We apologize for this issue and for the trouble it has caused our users, but we also thank our users for support and hope they will have patience until this issue is fully resolved.

Update: Other users have also been reporting issues with the application closing unexpectedly after deleting an image from a folder.  This issue is currently still being investigated, but I hope to have a resolution made available as soon as possible.

A third issue has been pointed out that images in the bottom row of a folder are often covered by the toolbar region, which prevents them from being selected.  This issue has been resolved in the update that will next be released.

If users have any other issues with the new update, please let me know and I will work to correct them.