AppStore downloaded version has problems that testing versions don't reflect.

cocos2d for iPhone » iTunes Connect /App Store / Cydia

AppStore downloaded version has problems that testing versions don't reflect.

(5 posts) (3 voices)

Started 1 year ago by Happy Otter
Latest reply from AkumaStreak

Tags:

Happy Otter
Member

My app is having a couple problems after being downloaded from the app store. These problems do not occur with the simulator or any of my testing devices ( iPod touch, iPhone 3g, any OS version). I have now released an update fixing some other bugs with no change. (hopeing it was a bad build or something.) the problems are:

- sprites are not appearing properly untail the first target is hit, once a target is hit, the sprites work.

- the other problem involves unlocking content with the email challenge. Only one should unlock after one challenge. The downloaded version is unlocking all three with one challenge. Would apple change my code without telling me?

These seem like simple problems to fix but I can't reproduce the errors with my testing devices.

Anybody have this happen to them?

Or maybe somebody has an idea on how I can debug.

Thanks.

Posted 1 year ago #
Happy Otter
Member

The game having the problems is called Clay Shooter

please grab a promo code here

http://www.cocos2d-iphone.org/forum/topic/5260

Im working with

MacBook OS X 10.6.2
Xcode 3.2.1
Cocos2d 0.99

Testing devices

Xcode Simulator
Iphone 3g Versions 3.0 - 3.1.3
Ipod touch 3.1.3

Posted 1 year ago #
riq
Key Master

I took XKX7MX3L7MR7
The sprites are OK.
I didn't try the challenge because I don't have any email account on my devices.

Tip when testing: Don't forget to remove your applications from the device, and to purge the simulator (iPhone simulator -> Reset Content and Settings)

Posted 1 year ago #
Happy Otter
Member

@ riq Thank you for your reply. And thank you thank you thank you for all the work you put into this project.

I should have been more specific about which sprites are having the problem.

-The background, "Pull" , shell , and stat label sprites are all working fine. These are all set up in my Game Scene.

-The clays that fly up work fine. These are set up in the Game Layer header file.

-The sprites in question are a "Miss" (should appear where screen is touched if the clay is missed), and a "Reload Reminder" (should move over the top of the shell sprite) both of these are set up in the Game Layer.

Once a clay is successfully hit the sprites in question react properly.

The REAL problem is that this dosent occur on my testing devices only on the downloaded app store versions.

-note : Before making my distribution build I clean all targets and test on a "clean" device. (deleting the old version first).

my only theories so far are:

- Im doing something wrong with the build?
- Apple is changing my code?

not likely I know but Im stumped.

thanks again for looking at it.

Posted 1 year ago #
AkumaStreak
Member

I would suggest cloning your app store configuration (call the new one something like AppStoreDistributionClone) and changing the code signing identity in the clone to your developer one (the one set in your release configuration). Then you will be able to build with this configuration/run this version locally. This build will def. be functionally identical to what Apple is signing/putting into the store. After verifying that the problems are present, diff the project.xcodeproj/project.pbxproj's configuration-specific sections (finding any erroneous differences between your release configuration and the new cloned configuration). You should be able to isolate any differences, fix your prior app store configuration by making any necessary changes (make the same changes to the clone and verify that the problems go away), and then delete the clone configuration as you won't need it anymore.

This is all assuming that you have configuration issue(s) that could affect your build functionally -- seems unlikely to begin with, but I can't think of any other ways this could happen atm.

Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.