I am using vfr/reader in my application for reading pdf files. It was working fine in IOS 6.1. But crashes when trying to run in IOS 7, the app crashes stating EXC_BAD_ACCESS code = 1 while executing CGContextDrawPDFPage(context, _PDFPageRef); for a particular page everytime.
I've googled and came to know that the same issue was also raised when the ios 6 was released. I don't know how they solved the issue.
I also tried adding the following two lines before CGContextDrawPDFPage(context, _PDFPageRef) as per this link, but it doesn't helped solving the bug.
CGContextSetRenderingIntent(context, kCGRenderingIntentDefault);
CGContextSetInterpolationQuality(context, kCGInterpolationHigh);
As I am a newbie to the Iphone application development, any help would be much appreciated.
Thanks,
Abilash.G
Just tested with XCode 5.1 Developer Preview in iOS 7.1 and it seems they have fixed the issue.
No crash, works as it should. :)
This is a bug in iOS 7.
You should file a bug report with Apple and provide them with the PDF file that is causing the crash.
Related
I am working on a fix for iOS 7 and having a problem. When I run my app on real device (iPhone 4S iOS 7), the screen looks different than when I run the same app on iPhone 3.5 inches iOS 7 Simulator. I am trying to understand why and what is the reason for that, if anyone can help it would be great!
First screenshot from Simulator, second picture from Device:
SOLVED: The app on the real iPhone has a base SDK 6.0 and the app that is on the Simulator has base SDK 7.0. So I guess the real device knew how to compensate for the low SDK base, unlike the simulator which behaved totally in a SDK 7.0 environment and thats why it was showing differently. thanks!
For anyone else reading this, Roy's 'Solved' comment above is correct.
I have gone into Xcode after the update and it had automatically updated my Base SDK to the latest 'iOS 7.0'.
After changing this back to 'iOS 6.1' - both the Simulator and Device are now working the same, as expected on iOS 7.
Not trying to steal Roy's thunder (whose saved me a good numbers of hours - thank you), just summarizing to others how to quickly fix the issue.
Ralph
Contrary to the proposed solution, Apple Documentation recommends to set Base SDK to the latest iOS https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/ConfiguringYourApp/ConfiguringYourApp.html#//apple_ref/doc/uid/TP40012582-CH28-SW37, so there must be a better solution
I also faced same issue..
I solved by adding below code at viewDidLoad method..of view controller.
if ([self respondsToSelector:#selector(edgesForExtendedLayout)])
self.edgesForExtendedLayout = UIRectEdgeNone;
Hope it helps..Thanks.
I have been working on an iOS app. It was working fine until a couple of days ago, it started behaving strangely. The app crashes on production but it creates no crash logs. However, when same scenario is tested out in QA, it works fine. Now I have been trying to find out the reason but without any crash logs or crash in debugging mode, it has become very difficult for me.
Any suggestion, how to tackle it?
Thanks!
P.S. I am using XCode 4.6.1 and app is for iOS 6.0.
Answering my own question, I have found out after detailed research on the internet that some crashes kill the application before logging the Crash Log. My error was that of a delegate property for my services. After long hard tries, I got to the root cause of the problem, since I had converted the code to ARC so the delegate property was unsafe_unreatained, which released the delegate while it was still in use by the service, so I just had to convert it into strong and set it to nil in dealloc. Further description can be seen here: https://stackoverflow.com/a/9065105/1351911.
I had the same problem, building ipa's in Xcode 4.6.1 with sdk version 6.0 or above crashes the app like anything. Try archiving it in Xcode 4.4 or 4.3 may be a lower version and try.
My app is working fine for iOS 5.1 simulator and less but its getting crashed for ios 6 simulator. No changes done in code for both versions. At debugging this error appears:
[unknown]Not safe to look up objc runtime data.
After googling i found this link.
Not safe to lookup objc runtime data
but nothing helped right for me.
Any help would be greatly appreciated
New here guys but have got a genuine problem. I have an iPhone app that was developed using SDK4. With apple introducing the new iOS version 6, does my code need to be recompiled on the new SDK to make it compatible with version 6?
Right now it crashes on iOS6. Also, do I need to do that everytime apple brings out a new version? I wonder every other app on earth already does that ?!
The problem with major iOS upgrades is method deprecation. It may happen that some parts of your code relies on methods that are not supported in iOS6. When this happens you should first check for API changes then recompile it with the latest API. If your code base works fine with iOS6 than there is no need for recompiling it, but unfortunately that doesn't seems to be your case.
Sometimes you don't need too. Most of the time, Apple publishes updates for libraries, so sometimes the old code is not compatible anymore. You have to recompile it, or you'll find issues.
For example I had a working app on iOS 5. With the iOS 6 update, I had to refer some code new because the app crashed with SIGABRT. Before iOS 6 it was working fine. Through Xcode's Debugger, most of the time finding issues is not hard work.
I've found that most of the time a crash will be caused by an existing bug in my application that I wasn't aware of. Subtle changes revealed it. It is rarely just a question of recompiling, but of fixing that bug.
Just recompiling can be dangerous. Apple can (and does) detect what version of the development tools your app was compiled with, maintains some behaviour that will keep your app running. Update, and you'll get the new behaviour instead.
I didn't have to recompile mine just for the sake of IOS6. They worked fine. But I had to adjust for 4" iphone 5 screen.
Please, somebody help me. I've been struggling with my problem for two days, I surfed all Internet and didn't find anything. I use Unity to make games for iDevices. Everything was just fine when I used Snow Leopard with xCode 4.0, but now I have Lion and xCode 4.2 and I can't build ANY app. I tried 5 different projects, and I even tried to make totally blank app, but every project I try to build in xCode to my device just closes on splash screen without any error. xCode just says that app finished running. I tried on iPod 4 and iPhone 3Gs - same. This is killing me! Please, someone help!
Finally problem solved! I've just removed Unity 3.4.2 and installed Unity 3.4.0 and it worked! Strange bug, I've spent three days blaming Apple, wouldn't think that this problem would be from Unity side.
Finally problem solved! I've just removed Unity 3.4.2 and installed
Unity 3.4.0 and it worked! Strange bug, I've spent three days blaming
Apple, wouldn't think that this problem would be from Unity side.
I just had the inverse problem...
I switched from 3.4.0 to 3.4.2 now nothing is working anymore...
Is there something new to do? I just re-created my whole Xcode project with all the storekits, openfeint and all and nothing works. It crashes on Unity splashscreen