I've developed a game in Cocos2d-X for iPads. I've tested it on several iPads and it worked great but after I published it to the App Store a few users complained that the game is completely unresponsive, meaning, all the animations are running but the game doesn't respond to touch events.
I have tried reproducing the problem but even if I use the exact same device with the exact same iOS version I still can't reproduce it. All the users who complained are running various versions of iOS9.
I have quite a few installs so it appears the problem only affects a small percentage of my users, but it still affects them. And for these users the game is always unresponsive, no matter how many times they run it or install\uninstall it.
I'm working with cocos2d-x 3.6.
Did anyone encounter such a problem or have any idea what might cause it?
Thanks!
Strangely enough, the problem was the MFMailComposeViewController. I mistakenly attempted to allocate it at startup without checking its canSendMail method. Apparently in iOS 9 it causes some kind of problem that blocks touches to my app.
Related
We have a really weird bug in out game where when we upload it into Beta and send it out through test flight, so phones play the game as intended and other phones have a weird issue pictured below:
From the image you can see the problem. One it does a ghosting type of thing with the characters as they move. Two, it acts like no scene is actually closing, but keeps stacking them on top of each other.
This problem does not occur on iPhone 6s or iPad Pro. It also doesn't occur on Android. We have only seen it on 5S and iPads.
We have looked at versions and that doesn't seem to be an issue either. We are using Unity 5.3 for this build (we reverted to this build as we felt it was the most stable, just to make sure that wasn;t an issue)
Anyone have an idea of what could be causing this problem?
Keep in mind that the things that are being seen are in different scenes.
in your camera settings you probably set clear flags to Dont clear set it to Depth only
I am completely stumped here. Created my game, all working in XCode' simulator and also on my device when directly deployed from XCode.
I Submitted my app and they rejected it and asked me to run in Ad-HOC mode in my device to test since the app was not working.
I can replicate the issue in Ad-HOC mode.
Issue: Once replace scene is invoked, the tile map is not populating
the Sprites from the sprite-sheet created using the TexturePacker
software. The app does not crash, however the Scene is empty with just
the background without any Sprites loaded in it.
Not sure how can this be a code issue since works fine when I install directly from XCode.
Please help, thanks in advance :)
#LearnCocos2D, Thanks, I found out the bug last night. I did not use CC_CONTENT_SCALE_FACTOR() when placing sprites using tilemap co-ordinates. Amazing thing is, it worked in debug mode but did not as soon as I released the binary :)
I am writing an app which displays a simple Apple Map across most of the screen. However, when I compare the speed of scrolling, there is a significant slow-down comparative to the native Apple Maps which come with iOS 6.
In my investigation of why, I noticed that the Facebook App (which also uses Apple Maps), the same performance hit is present.
This is most noticeable on iPhone 4 with iOS 6.
Does anyone know of a special view-related performance enhancing step or set of steps which I need to take to increase performance? I would like my maps to move as fluidly as the Apple Maps app.
I was having the same problem, and it looks like it could be due to having Development enabled on the device.
On the Apple Dev Forums I posted to ask about this for my problems (my post) and someone rightly reminded me that a lot of developers have been complaining about sluggish development devices.
So I went to the Organizer and Ignored my device from there, removing it as development enabled. I restarted the device and sure enough my MKMapView was a lot snappier. It was still sluggish at times, but the performance improved significantly.
Try it out for your device and see if you notice a difference.
I're released an iPad game which is developed on the Cocos2d framework. Ive tested the game on a number of devices iPad 3, and iPad 2 and never had any issues.
Now i'm getting a few reports back that its not launching properly on some devices. People are saying they are seeing the default.png images then the app is closing.
Any ideas?
Without crash report this is just a guessing game.
By all means try to reproduce the problem on your side.
Possible problems:
1. If the app takes too long to launch it will be closed by iOS.
2. If it does not have enough memory it will not launch as well.
Try the following:
I. Open many other heavy apps in the background so there is not much memory.
See how it affects your app launch.
II. During launch try to use as many fast taps as possible and fast gestures.
There is possibility that very early taps are not serviced properly or at all
and that can cause the crash.
III. Test on many devices as you can - especially low end.
I found the issue, it was to do with the social framework running on older devices where it isn't available.
I have some strange problems of memory management on iOS 5.1.1, I'm NOT using Automatic Reference Counting in the project. Everything works well on iPad 3 5.1 or other devices with 5.1 or lower, this issue happens to two different project (one game and one app). So I think I have coded the right retain/release stuff.
Generally some Objective-C objects are released before it should be. When access it later, app crash. This happens on an iPad 3 LTE, an iPad 3 Wifi and an iPod Touch 4, all running iOS 5.1.1. It never happened on any device running iOS 5.1 or lower. I haven't found any pattern for this. Sometimes even an UIView which is still one the screen get released, if user touches a button, app crashes.
I understand these kind of issue can be debugged with NSZombies. But when I enable NSZombies, this kind of problem never happened.
It looks like a bug of iOS 5.1.1 to me, I'm wondering if it can be fixed on app side.