I'm new to Apple's Game Center and while I'm studying it I added some of Achievements.
It seems that if the App is go on live, Apple don't let us remove Achievements data from Game Center. But before uploading App to App Store, is it possible to delete Achievements which is added for testing purpose?
Thank you.
according to itunes connect "Once an achievement has gone live for any version of your app, it cannot be removed." but I think you can still modify it to an usable achievement. or just hide it so player won't see it. can you?
I've been installing achievements into my iOS game recently using Game Center, and all appears to be fine.
What I'm wondering is is there anyway I can gather analytics on these achievements? I can't see anything explicit in iTunes Connect so I'm looking for something else I imagine.
If you use flurry analytics you can easily do this. If you are looking for an iTunes Connect or Apple way of doing this there is no feature.
Flurry is 100% free to use and extremely easy to install into your app. It's pretty much drag and drop a few imports and then you're just added one line of code to track specific things.
How I suggest you do this is insert the [FlurryAPI logEvent:#"EVENT_NAME"] call in the same statement that you call an achievement in your iOS game.
Currently you can see in my game what the analytics look like:
I'm developing an iOS game and want to add game center functionality.
I don't have finalized screenshots of the game play but after you register them with iTunes connect they can't be changed.
Is there any way to test game center functionality without registering the app? I need IAP, leaderboards and achievements.
am I missing something?
thanks in advance!
You can definitely change the screenshots after you've registered your app with iTunes Connect. I've done this many times before. You'll need to set up the leaderboards and achievements in iTunes Connect in order to test Game Center. It's the only way. These docs might be worth reading up on:
https://developer.apple.com/library/ios/documentation/LanguagesUtilities/Conceptual/iTunesConnectGameCenter_Guide/Introduction/Introduction.html#//apple_ref/doc/uid/TP40013726
I'm developing a turn-based iPhone game using Game Center. I created two Game Center accounts for testing but neither can find the other when I try to matchmake games. Both are in two matchmade games alone - neither found the other when matchmaking, in spite of the fact that the matches have 8 players max. What do you think could be causing this? Should I just put it on my physical device, because the games don't really work in sandbox, or what?
Gamecenter testing was a big disappointment for me, but I would enjoy to summarize some things that I learned in the process.
Make sure
-You enabled gamecenter support in both itunes connect's app information section and inside version details
-You completed a turn with a call to endTurnWithMatchData otherwise no other user will be able to connect to your game
-Know that simulator is able to connect to a game but it can't receive data only actual devices can.
-It is not a lag!
There is the possibility that your devices are actually able to match but there is a huge lag before they can, so you think it is not working. This happens to me with my iPad and iPhone for testing, it always takes around a minute to match another device. I have a asked a question regarding this lag here :Game Center Matchmaking GKTurnBasedMatch has significant lag (~1 min) Most replies told same things happens to them and problem is usually in apple's server not your code. I have also contacted apple for the issue by submitting a TSI, they have suggested doing many things (such as trying different gamecenter sandbox accounts, turning off the device, hard reset) but in the end all they told me was 1 min is well within the acceptable lag for turn based matchmaking. I have also submitted a bug report with ID #: 13635249 and its status is open.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 9 years ago.
Improve this question
Can anybody help me out to know the possible reasons for which Apple store can reject or raise objection to submit any iPhone application.
Here are possible reasons (unofficial, from here):
Vibration. It is not permitted to use continuous vibration in your apps - short bursts as warnings is all that is allowed. Don’t bother trying to set up a timer to keep the vibration going, it will cause your app to be rejected.
Linking to private frameworks. This is obvious, but somehow in playing around with stuff we had linked to the MoviePlayer.framework. That’s a no-no, and cost us about ten days while we unlinked that framework, recompiled, and then resubmitted.
Improper handling of editing in tableview cells. Also obvious, but be aware that if you enable table cell editing, you’ll have to manually specify which cells should respond to editing controls and which should not. We had some random prefs cells in one of our early apps that were able to be swiped to bring up a ‘delete’ badge. Of course it didn’t do anything, but Apple justly considered this poor design and rejected our app.
Icons. Make sure the 57 pixel icon is identical to the 512 pixel version. Also, use a different icon if you are creating ‘lite’ and ‘pro’ versions of your app (i.e., free and paid). Using the same icon for both sends your app straight to … you guessed it … the bin.
Copying existing functionality. This one is much more subtle and insidious, and has probably affected the great percentage of developers. In addition to the widely publicized Podcaster debacle, reports from user comments indicate that Apple is casting a wide net when looking for duplicated functionality. Mini web browsers, or apps that essentially show web pages, seem particularly vulnerable, even if they add new and/or useful functionality. Stay away from email clients as well.
Using appropriate keyboard type. If your app asks for a phone number or other numeral-only input and you present a keyboard that also includes the possibility of entering standard alpha-numeric input … yep. (Thanks Jeremy1026)
Version numbers. If your app is currently at version 0.99 or below, you’d better consider giving it a promotion as Apple seems to prefer 1.0 and above. One of ours was recently rejected for being .016, with a message suggesting that our version number wasn’t even numeric. When we resubmitted the same app from scratch as version 1.0, it went through.
Network Reachability. If your app requires any type of network access you need to make sure it works when that access isn't available. If it doesn't it will be rejected. Apple provides sample code to test this which you can use as-is in most cases: https://developer.apple.com/library/content/samplecode/Reachability/Introduction/Intro.html
And last, but not least:
Flatulence Don’t even try. ;-) UPDATE: sorry, this seems to be outdated by now. Apple makes a lot of money now with "fart apps": see this article.
Edit:
Here is a link to a recent article about ten iPhone Apps That Didn't Make Apple's App Store.
And a tip: Apple has a Mac app called Application Loader that you could install. Once you install it, it analyzes your app's zip file. It verifies all the certificates, icons, and other things are correct before submitting to Apple. Using the Application Loader minimizes your chances of app rejection.
Another interesting resource: App Store Roundtable: Transparency and the Approval System (appleblog.com)
Yet another edit:
New rules by February 2010: "No Swimsuits, No Skin, And No Innuendo" (source: TechCrunch article, Wobble author's blog)
By the way: during the iPhone 3.0 preview event (march 2009), an Apple spokesman told that 96% of all submitted application were approved.
Apple have now (as of 9th September 2010) published their official list of app store review guidelines:
appstore approval guidelines
(apple developer login required)
or a mirror here:
app store guidelines
Will apple want to create an app like that in the future? If (yes) reject.
Do you have a really awesome idea that apple may want to use in the future if(yes) reject
Here's the video of the SDK announcement that describes Apple published list of rejection criteria:
SDK Announcement
As others have noted, Apple also seem to have a bunch of other conditions that they don't publicise. Note that rejection notices are now covered by the NDA.
I can't confirm this but it makes sense, but people are reporting their apps being rejected for being too simple or too trivial.
Just got a bounce for handling network outages badly. If you connect to the network, be prepared to handle any error conditions that may come up.
My paid version of app was rejected by appstore.
After Purchasing and downloading app first screen was "User Agreement" and when user taps on " I agree" only then he is able to continue using app.
Apple described the reason of rejection "when user purchased app from appstore and download in phone then you must not restrict user to Agree with Agreement" instead display your agreement before downloading app in iTunes.
Amazingly, apps can get rejected for trying to keep their interface consistent with Apple's own apps. (ie, using pinch zoom/expand gestures)
There is a site I know which can help you generate great advertising ideas with iPhone. see this site:
http://itunes.apple.com/app/adpack/id359562015?mt=8
I submitted a paid app to app store but get rejected and i learned another possibility of app rejection
My app was Game Center enabled. When app starts first screen was login screen that prompt user to login through GameCenter to continue.
They rejected the app giving reason- As user will not be able to get services of your app unless he is not logged in with Game Center although he paid you to download app. You cannot restrict user to login through Game Center each time before app starts.
From 1st May,2013 onwards if we don't support iPhone 5, your app will be rejected.So iPhone 5 support is must.