how do other developers then get their FM runtime applications through review ? Haven´t heard of this kind of problem yet. Probably nobody is patching the runtime.
I was not aware any FileMaker runtime or solution could be distributed on either the Mac or iOS App Store. Because from a structual perspective they are primarily documents not applications. It would sure be great if we could get App Store distribution for FM Developers.
there are already several FM runtime based Applications in the appstore and there are tuts on how to get them there:
I wonder if FMI and Apple might not reconsider the issue of runtimes now that they are no longer selling FMGO12 but giving it away. An iOS-compatible runtime generated from FMPA12 seems possible, if Apple and FMI will let it happen, without any financial impact on FMGo revenue.
As for the App Store, the issue has been around since the App Store started. Still no indication that FMI or Apple will open it up to allow FM Developers to compete with FM Pro as an App. FMI revenue and Apple revenue have different interests when considering sales via the App store, but both would have to agree to overcome the current obstacles to FM developers selling Apps.
Well, this is quite simple. _NSGetCarbonMenu is a private function to get the underlying Carbon Menu for a Cocoa Menu. Seems like this is used by Filemaker internally. And this function triggers the scanner from Apple's App Store team.
You could talk to Filemaker and Apple about this issue.
The link you provided reads like an instruction manual, but th author's own followup indicates it has not worked yet.
Any links to successful FM-generated Apps?
there are several in the German language Mac OS X Appstore
Note that Cashbook (the English version of Kassenbuch) is available in the app store. But it has received terrible reviews; including my review. It did nothing but crash for me.
I traced this to a conflict with 2Empower Developer Assistant. I contacted Draconvention and they noticed that the FMWrapper.framework was not in the app bundle for the Cashbook runtime.
I don't know if this was an oversight; or something the Cashbook developer had to do to get their app into the app store. But when I manually included the FMWrapper.framework in the Cashbook app bundle, it no longer crashed.
Has anybody checked to see if a FM12 runtime uses this private function?
Perhaps FileMaker has already addressed this issue.
Just as a test, I tried creating the runtime in kiosk mode and submitting that to Apple...sure enough _NSGetCarbonMenu is no longer an issue with them. Perhaps it is because no menus are available in kiosk mode so the function isn't called? My app was rejected nonetheless because now, according to Apple,
"There is no way to resize the main app window to a standard size from the full screen."
It seems like a Catch-22...
Any thoughts or suggestions...
A question to intex:
Did you submit updates or new runtimes to Mac Appstore since sandboxing is needed?
I found that in the runtime there are subclasses which are not conform with sandboxing.
Thanks for your answer
We gave up with the Appstore - less to technical questions, more to financial reasons.
Thanks for your quick reply