3.4.1 is coming

[Piotr]

Beta Testers and Apple have it for review now.

What's New in this Version:

30/09/2012   enabled C++ ARC
03/10/2012   fixed filter lock when returning from card details
04/10/2012   updated deck and binder scrollers to lazy load their pages
04/10/2012   prevented double-tap for floating card details view
04/10/2012   floating card details view should disappear when other card is tapped
04/10/2012   removed searchbar from landscape card lists on iPhone
04/10/2012   floating card details view will disappear when changing orientation
12/10/2012   fixed deck and binder scrollers slowdown caused by dark gray tint
13/10/2012   fixed background search crash in card lists
13/10/2012   fixed adding to Trading
13/10/2012   fixed some glitches related to card lists filter locking
13/10/2012   fixed slide position when returning to card list
13/10/2012   updated device recognition code

[swallowtail]

I really hope it improves the performance, because it is woeful, almost to the point that I'll not use it until its fixed. Scrolling on card pages, moving between binders in the small side scroll is just terrible. It's also been crashing a lot more than previously (e.g. editing decks, going into cards in a deck).

Edit - this is on an iPad 2

[Piotr]

It will, or I'll eat my shorts

[whitedrake]

It will, or I'll eat my shorts

I would like to see that... If it will not fix the problems u will do it on cam... And we will have fun at least...

[smokin terry]

It will, or I'll eat my shorts

You know with apple not letting you put out one update for way to long then with how much IOS 6 is screwing stuff up for you, I think they should give back all of their 30% of all your beer.

[reezel]

They seem to really just slow up their approval process.

[Piotr]

A lot of people are updating their apps these days, not only I messed up the iOS 6 thing. Apple did too with their maps, Google with their youtube are not exactly on the ball either

[MarduArrow]

Not to mention the new App Store is absolute 💩

[smokin terry]

Right now I'm entering cards from the boxes I bought into my trade binder and it will freeze up for a few seconds when I try to scroll down after selecting a card and when I try to select how many I have.

[planarchaos]

Come on Apple! I really need 3.4.1. : - )

[Piotr]

3.4.1 is fixing just a bunch of critical bugs, what you need is 3.6. In any case, the delay is really annoying.

[whitedrake]

I hope they will approve it quickly... Am really strugling with binders nowadays...

[Piotr]

Everybody on iOS 6 is affected. And I'm told that if you're on iOS 5, your scanner is broken (please confirm or deny).

[planarchaos]

Well, what you've fixed in 3.4.1 is what I really need. : - )

Need to finish putting in my collection, so I can start trading.

[Piotr]

2.23

We found that your app does not follow the iOS Data Storage Guidelines, which is required per the App Store Review Guidelines.

In particular, we found that on launch and/or content download, your app stores 17MB. To check how much data your app is storing:

- Install and launch your app
- Go to Settings > iCloud > Storage & Backup > Manage Storage
- If necessary, tap "Show all apps"
- Check your app's storage

The iOS Data Storage Guidelines indicate that only content that the user creates using your app, e.g., documents, new files, edits, etc., should be backed up by iCloud.

Temporary files used by your app should only be stored in the /tmp directory; please remember to delete the files stored in this location when the user exits the app.

Data that can be recreated but must persist for proper functioning of your app - or because customers expect it to be available for offline use - should be marked with the "do not back up" attribute. For NSURL objects, add the NSURLIsExcludedFromBackupKey attribute to prevent the corresponding file from being backed up. For CFURLRef objects, use the corresponding kCFURLIsExcludedFromBackupKey attribute.

For more information, please see Technical Q&A 1719: How do I prevent files from being backed up to iCloud and iTunes?.

It is necessary to revise your app to meet the requirements of the iOS Data Storage Guidelines.


For discrete code-level questions, you may wish to consult with Apple Developer Technical Support. Please be sure to:

- include the complete details of your rejection issues
- prepare any symbolicated crash logs, screenshots, and steps to reproduce the issues for when the DTS engineer follows up.

For information on how to symbolicate and read a crash log, please see Tech Note TN2151 Understanding and Analyzing iPhone OS Application Crash Reports.

If you have difficulty reproducing this issue, please try testing the workflow as described in <https://developer.apple.com/library/ios/qa/qa1764/>Testing Workflow with Xcode's Archive feature".