So my app uses MapKit, and many of the people who have downloaded my app are complaining that it crashes right after the map loads. I can assume that its crashing once the annotations are being displayed on the map. I have no history of crashes in my itunes connect crash logs (should i??), but they posted in a review that they're using iphone v1, and iOs 3.1.3. I have never been able to replicate this crash myself, and I think it may be because the lower version supported by the simulator is 3.2.
Does anyone know who I can debug in this situation?
Check multiple annotation at Same Lat log.
Related
We are developing a Watch OS companion application for our iOS app. We currently get symbolicated crash reports for our iOS app on App Store Connect. We are trying to get the same for the Watch Application.
We are producing some forced crashes on a build we uploaded to TestFlight but crash logs are not getting there as iOS crash logs. Is there anything else that needs to be done differently from iOS to get them?
Do you know about any known issues on it?
BTW, we see the crash logs getting to the iPhone on the iPhone itself. They're just not uploaded. We are also able to get the logs on Xcode Organizer.
I am encountering a strange behaviour, my app runs smoothly on simulator but crashes on device.
Also when i try to detect leaks using instruments it just crashes on both simulator and device.
I am totally stuck as i am not even able to generate any error message on console, also NSZombieEnabled is on in the settings.
I can see two possible reasons for the behavior you describe:
device is short on memory; (but you would see some processing in this case)
your app uses a newer SDK than what you have installed on your device (like using the SDK 5 twitter framework and then running your app on an SDK 4 device).
Specifically, in case 2, you would not see any log messages because the app would fail as soon as it tries to load the missing framework in memory.
In any case, inspect the device log in Xcode Organizer window to have more info about the crash. This is the only way you can understand what is happening.
I have an already developed project for ios3 and ios4 developed on sdk4.but my app get crashed on ios 5 while it was working fine on lower version.
As my guess it's due to ARC concept of ios5.
So what i tried is
installed sdk 4.2.
refractor project from EDIT option for ARC.(I get some error while converting for arc.i continued).
Disabled arc from build settings.
also set the flag -fno-objc-arc
But no luck app still crashing.
it crash on accessing property value.
Why did you guess it was ARC? ARC doesn't even happen unless you specifically ask it to do so. I'm betting it had more to do with an API change between ios 4 and ios5.
My advice is to use your source control to go back to your version before you made those changes, run it again on ios5, read the stack trace, and find out what is really causing your app to crash.
I have run into a very confusing situation with maps on the iPhone. Everything had been running without a hitch on a maps based app that I was developing, and then yesterday my device and the iOS simulators started exhibiting some bizarre behaviour where the tiles the app was fetching for the map did not line up with where they should be.
Here's a screenshot of what I am seeing.
This is happening on both my device (after a factory reset as well) and on the iOS simulator. I managed to fix the simulator by reinstalling Xcode, but this problem seems to be back! I can't for the life of me figure out what it could be.
I should note that I have tried clearing the map tiles cache and it would fix it for a while then the problem would start again.
Also I cleared the map tiles cache and then created an brand new MapKit app and the problem started again so I am sure it isn't my app causing it. It is happening also on the iOS 4 and 5 simulators.
Thanks so much for your help!
There have been quite some reports of people from the Japan area that this affects all devices in the area. Maybe this is the same thing in Australia as well. There is a lengthy apple discussion on https://discussions.apple.com/message/16630435 with affected people.
I released an iPhone/iPad app some weeks ago. From 15 reviews (worldwide) I got a dozen 1 star reviews from users saying the app does not work, they only get a blank screen. The other three are happy and it works for them.
I tested the app on an iPad 1, an iPad 2, an iPhone 3GS and several iPhone 4s - it worked on every device flawlessly. And it passed the app store submission process, so it must have worked at Apple...
The crash report in iTunes Connect is empty - the app obviously does not crash, it just hangs somewhere.
Unfortunately there is no way to contact the users where it doesn't work :-(
I know its really hard to help with that less information, but I don't know what to do when I can't replicate the problem on my side...
So does anybody has any idea?
If its a memory problem - shouldn't the app crash then?
I use AVFoundation to play a movie and I know of some flaws since its a relatively new library - does somebody know of this problem (a blank screen) in relation with AVFoundation?
It would be helpful as well if you could download the app (the name is "Hyperactive") and test if you get a blank screen. If so I would be glad to learn the exact device and the iOS version. I hope this is not missunderstood as spam, thats not what I intend...
Thanks in advance,
best regards,
Walchy
This is a longshot, but maybe the user had the application running for a long time, receiving a viewDidUnload, and something you unload is not getting reloaded on the viewDidLoad.
Try running a "Simulate Memory Warning" on the iphone simulator options.
Both iPhone and iPad versions work fine on iPad 1.
Application won't install on iPhone 3G with iOS 4.2.1.
Have you tested your application on a jailbroken device?
It turned out that the black screen only happens on an iPod Touch and the solution is very easy:
You need an additional entry in the .plist file for the iPod Touch:
Main nib file base name ...
iPod Touch 4G thinks it's an iPad