Dan Johnston Feb 03 •
Update: 3rd Mar. As mentioned last week in the release notes for v1279, we do have a no-ads and no analytics version of GM available via the Helpdesk. If you would like a copy, please submit a ticket asking for v1282. Strictly speaking, it's not really "no-ads" as iAds still works, but no other ad providers and no Google Analytics or Flurry. You only need this version of GM if you want to submit a game with no ads and analytics or *only* iAds to Apple for the iOS AppStore - if that's not your game, please stick with the normal release v1279.
Update: 24th Feb. We are now aware that Google Analytics' and Flurry's SDKs both make check for ads being enabled also, and these checks are still enough for Apple to reject your submission. A fix for this will be coming as soon as we can.
Update: 12th Feb. We now have a pre-release version of 1.2.1266 available if you need to submit to iOS in the immediate future - please submit a helpdesk ticket requesting a copy. The next EA release will also have the change made.
We were already transitioning advertisers to being individual extensions, mainly to optimise package builds and clean your projects, but now that Apple have made this change it does mean that instead of an advertiser migrating one-at-a-time and no loss of functionality, we must remove all of them now and then add them back in as they are developed. This will mean that over the next few releases of GM advertisers will be added gradually back in. Please bear with us during this process.
iOS apps made with the current version of GameMaker are failing iTunes Store submission due to a change in Apple's approval process. Apps can no longer include an advertising identifier if they don't make use of advertising in the game. As GameMaker includes this identifier by default, any game that does not utilise advertising on iOS will currently fail submission.
We can't say exactly how soon the fix will be as the work is still in development and will then undergo testing - and we do not announce release dates in advance anyway - but be assured this is a priority issue for us and we are trying to address it asap.
We are seeing if a quicker and smaller fix to GM: S is possible, but unfortunately this was an unannounced major change by Apple and we have to change significant underlying parts of how we build iOS packages in order to be compliant with their new requirements.