Mac App Store - Submission Feedback - One Last Hurdle

[Pencil]

I submitted my LiveCode application to the Mac App Store and received a feedback email from the App Review Team saying that the application needs one change before it can be listed in the Mac App Store.

This is the text from the rejection email:

We’ve completed the review of your app but cannot post this version to the App Store because the user interface is not consistent with the Apple Human Interface Guidelines, which is not allowed in the Mac App Store Guidelines <https://developer.apple.com/appstore/re ... lines.html>:

6.1 Apps must comply with all terms and conditions explained in the Apple Macintosh Human Interface Guidelines

We have found the following issue:

When the application has unsaved changes, the close button should display a "dirty document" (Document with unsaved changes) indicator. A screenshot has been attached for your reference. Please refer to Chapter 14 of the Apple Human Interface Guidelines for more information about this issue.

Please evaluate whether you can improve the user experience and resubmit your app for review.

They failed to attached the screenshot, but according to Chapter 14 of the Apple Human Interface Guidelines:

When a document has unsaved changes, the close button should display a dot.

I have searched, but cannot find how to display a dot in the Close button with LiveCode. I know I've missed something, with this being such a basic feature of Mac OS X.

Any help with this one last detail would be very much appreciated.

Thanks.

Dwayne

[Klaus]

Hi Dwayne,

unfortuntely you cannot do this with he build-in capabilities of LiveCode!

There is a Mac external available that makes this possible, check this:
http://www.revdevelop.com/
but no download address, hmmm...

You could ask the "Support" there where to get the external.


Best

Klaus

[Pencil]

Thanks Klaus,

I've submitted a help ticket on the revdevelop.com Support page.

I also searched for any information regarding a download link for the external, but only found comments saying that the external is not longer available.

I'm hoping revdevelop support will help.

Thanks again.

Dwayne

[shaosean]

ssMacExternal is no longer available.

[Klaus]

Hi Sean,

ssMacExternal is no longer available.

huh? C'mon, no kidding?

What happened? Any technical or personal reasons you might want to tell us about?


Best

Klaus

[Pencil]

Hi Sean,

I'm desperately hoping you will change your mind.

The Mac App Store Review Team tells me that my application cannot be listed in the Store without the "dirty document" flag indicator in the Close button. I can't find any other way to set the flag in my LiveCode app.

Thanks,

Dwayne

[jiml]

Tell Apple you'll comply with that guidline as soon as their Address Book does.

[Klaus]

Tell Apple you'll comply with that guidline as soon as their Address Book does.

I doubt Apple will be amused if you do so


Best from germany

Klaus

[FourthWorld]

With its non-standard appearance and that it downloads its own updates, iTunes itself fails to meet Apple's criteria for inclusion in iTunes.

Will Apple reject it?

[Pencil]

Hi Richard,

Thanks for mentioning this in your "Roadmap: App Store compliance" post and raising the awareness on HIG compliance issues. After the time I've spent getting my app ready for the Mac App Store, the inability to set the closebox dot "dirty" flag is a stunning show stopper. Dead stop, one foot short of the finish line.

Thanks,

Dwayne

[Pencil]

After many hours with the LiveCode External Creator, XCode, C++ and Google, I managed to build a "one trick pony" external that sets the "dirty" document indicator. The external is very basic, but it helped me meet Apple's HIG requirement.

My application has now been approved for the Mac App Store and is listed as "Ready for Sale"!

I'm still hoping Sean will make her "way cool, super amazing, feature packed" external available again soon. There are so many wonderful things in there!

Thanks for all the feedback.

Dwayne

[FourthWorld]

It's good that you have a solution for now, but FWIW I've heard a rumor from a reliable source that support for the unsaved-changes indicator will be available in the engine in an upcoming version.

[Pencil]

Fantastic!

I would much rather use a property within LiveCode

Thanks for the update.

Dwayne

[RRobert]

By the way: Did someone already wrote some lines to validate app store receipts?

Robert

[kwinkler]

Regarding the "dirty document indicator", apparently LiveCode 4.5.3 has "experimental support" for this feature. Has anyone figured out how to implement this? I can't find any documentation in either the Dictionary or on these forums. Thanks.