Actually what causes rejection of Marmalade app?

Home / Forums / Marmalade Archive / Deployment, devices and platforms / Actually what causes rejection of Marmalade app?
2 replies [Last post]
by: WIliammm
Status: Offline
Joined: 2012-06-13

I am finishing an app and beginning to feel little anxious about some specific requirements that AppStore might impose on apps, espacially if build with Marmalade.

For example, v. 6.0.3 has splash screens broken? And splash screens are required by AppStore.

Or: google says general statements about "Not using external APIs". One app got rejected after using a framework from OSX. How does this fit to Marmalade's modules? E.g. protocolbuffers is an external API, isn't it? Or tinyxml.

by: roo
Status: Offline
Joined: 2012-03-23
Splash is awful but I never

Splash is awful but I never was rejected because of splash

by: WIliammm
Status: Offline
Joined: 2012-06-13
You probably mean the

You probably mean the Community splash. It probably fulfils the Apple's requirement of startup splash screen. But if you use Indie license, you will have to provide your own splash screen, and this is apparently broken, at least on my 6.0.3

Latest Posts

Latest Comments

Top Contributors

  • amanda
  • riaan
  • alexand3
  • alexand4
  • alexand7
  • alexand889
  • alexand12191
  • remote9991
  • remote9992
  • test