iPad app rejected due to orientation of native widgets (web popup, keyboard, alerts)

My iPad application was just rejected due to the native alerts and keyboards being stuck in portrait mode. More specifically, the app was rejected because I’m using the facebook connect lib that comes with Corona, and the web popup, native alerts and native keyboard are all locked to portrait mode.

Is there ANY method now included in corona to change the orientation of these items? I have the beta version and have worked tirelessly to find a solution but I’ve not yet found one. The only option I currently have is to completely remove facebook any other text input or web popup features (I’ve already removed the alerts and replaced them with a lightbox confirmation effect) from my game which really limits my offering. Especially at a 1-2 weeks per submission/rejection/approval cycle.

Any ideas? Does anybody from ansca know when rotation for these items will be available? I’ve tried every combination in the plist settings but to no avail.

This is a pretty sad day for me. Out of my 6 current apps and 11 submissions I’ve never had a rejection until now. My perfect streak is shattered!

In the interim I’m going to remove facebook and a few other things and I’ll resubmit my app. An app in the appstore is better than an app in perpetual development.

  • Nick [import]uid: 70 topic_id: 989 reply_id: 300989[/import]

Ouch! Sorry to hear that Nick. :frowning:

The good news is, handling the orientations shouldn’t be *that* difficult to do (for Ansca), so hopefully they can get this type of thing handled soon and released as soon as it’s ready.

My team is very close to submitting our App as well, but I think we’ll wait until these things are correctly handled in Corona now.

Thanks for the info!

Scott [import]uid: 5659 topic_id: 989 reply_id: 2336[/import]

Nick, I’m sorry to hear about your rejected app. I have two days left on my Corona SDK trial and I’ve been on the fence about purchasing Corona. It’s not the money but issues like this that make me think twice about investing my time and effort into a tool with such limitations.

I’m not a game developer and every great idea I have for an app can’t be done because of the missing native features. Users (and the App store) are not going to stand for an app that implements standard features (like a landscape keyboard) in a non-standard way. I totally understand about building a tool to support a common set of features (iPhone/iPad and Android) but my focus is iPhone/iPad right now and I’m looking for a product that will support that.

I’ll wait until the next beta release to see what’s been added and if all the outstanding bugs have been addressed. It’s my feeling that things have improved over the past few weeks and I’m hoping it will give me a reason to buy.

Tom [import]uid: 6119 topic_id: 989 reply_id: 2338[/import]

Case # 188 opened [import]uid: 54 topic_id: 989 reply_id: 2396[/import]

Has anyone checked to see if the keyboard orientation problem has been fixed in the Beta 3 SDK? It doesn’t appear to be on the list of fixes.

Tom [import]uid: 6119 topic_id: 989 reply_id: 2425[/import]

I checked but the behavior is the same as before. [import]uid: 70 topic_id: 989 reply_id: 2437[/import]

This should be fixed as of Beta 4 (released May 27, 2010). The current release is Beta 5. [import]uid: 3007 topic_id: 989 reply_id: 3094[/import]