I'm using a UIWebView in my app, and everything works fine in iOS5 and 6.
But on iOS7 the UIWebView can't load the page requested (an html from internet) and start an infinite loop with this error every 10 secs:
void SendDelegateMessage(NSInvocation *): delegate (webView:decidePolicyForNavigationAction:request:frame:decisionListener:) failed to return after waiting 10 seconds. main run loop mode: kCFRunLoopDefaultMode
The webview loadrequest is located in viewDidAppear.
I found no documentation for this bug for iOS.
The method decidePolicyForNavigationAction seems to be used only in WebKit for MacOS.. and not for iOS.
Same problem both on device and on simulator.
I saw similar topics on stackoverflow, but noone report a working solution :/
Thanks for your help.
Try to download new xCode version 5.0.1
This issue is fixed in version 5.0.1
Also, clean all the builds from the path ~/Library/Developer/Xcode/DerivedData/~
Build after clean. Everything works fine.
Let me know if the issue still persist.
Problem solved:
My problem was related to a library linked in the project: pspdfkit v2.x on iOS7.
Initializing the uiwebview before pspdfkit (even without presenting it) solved my problem.
Related
I'm seeing a bug in WatchKit where it shows a wrong image when assigned by name programmatically or from the storyboard. Am I doing anything wrong here?
How to reproduce
Add images to the WatchKit app with names image_1.png and image_10.png.
Set the first image to the interface image: image.setImageNamed("image_1")
Expected behaviour
First image image_1.png is shown.
Actual behaviour
Second image image_10.png is shown.
Tested in Xcode
Version 6.2 (6C131e)
Version 6.3 (6D532l)
Demo
https://github.com/evgenyneu/watch-image-glitch-demo
Update
This bug has been submitted to Apple Bug Reporter. Apple confirmed that this is a bug.
You should definitely file a Serious Bug radar. I pulled down your sample project (great work by the way) and ran it. I'm certainly seeing the same behavior on Xcode 6.2 (6C131e).
I also moved the images into the xcassets bundle which didn't have any affect on the issue. The only thing that I noticed is that renaming the image_10 to image_11, image_12 or image_100 did fix the problem. It appears that only image_10 is the culprit.
If you want to show just one image, you can still use startAnimating with a range that starts at your image and has a length of 1 (duration is 0 in this case). It works fine as a workaround until the bug is fixed.
UIImageView+AFNetworking has always worked ok in a UITableViewCell for me. Images used to load smartly while scrolling and rarely failed to load. Recently, it stopped working well. Has anyone else experienced this? Was this UIImageView category never intended to work inside of a UITableView?
A few details: my UIImageView is inside of a UITableViewCell in a Storyboard. I call setImageWithURL: from within the cellForRowAtIndexPath: method.
The problems seem to have started when switching to AFNetworking 1.0, specifically in conjunction with moving to Xcode 4.6 and building against iOS 6.1 SDK.
Use SDWebImage, a perfect replacement for AFNetworking and perfectly compatible with iOS 6.1.
Switched to the AsyncImageView library, using it in exactly the same way (from within cellForRowAtIndexPath:), and I've had no problems since. Might be an AFNetworking + iOS 6.1 bug... Would love to know if anyone else has had similar problems.
My App, which is created for iOS4, is crashing in iOS6 and is not installing on simulator or device.
It just shows the splash screen and crashes.
Did finish Launching is not being called.
Can anybody please Help?
Finally i got the solution of my problem mentioned above.
In my ios4 App, in FirstViewController.xib "Use AutoLayout" was checked.
I just removed the checkmark and my App start working.
Amazing!!!
I would recommend creating a new project, and either carefully looking for the changes in delegate or any deprecated code, or just moving all of your code to the new project. Also, you should run a convert to modern syntax check.
There may be issue with Application Delegate. The obvious reason - your object is not set as an application delegate.
Looking at Apple documentation there is quite a few ways to accomplish it:
Remove application delegate binding in Interface Builder (.xib file
for the window) Set 4th parameter of UIApplicationMain in main.h to
something else than nil.
Check you nib file in Interface Builder and see if the App Delegate is setup.
Or Reference to documentation Core Application Design
Hope this will you out.
Look into the release notes of xcode, ios6
It is said that when working with IOS6, Auto Layout is turned on and that crashes the app if used on older versions. Check the link, which has other things to watch out for:
https://developer.apple.com/library/mac/#releasenotes/DeveloperTools/RN-Xcode/_index.html
https://developer.apple.com/library/ios/#releasenotes/General/RN-iOSSDK-6_0/_index.html
I have the following problem. When making this call inside a view controller :
[self.webView loadRequest:[NSURLRequest requestWithURL:[NSURL URLWithString:#"http://www.youtube.com/user/mc1975mc1/videos?sort=dd&view=0&page=1"]]];
I am getting it correct in the simulator. see the following screen capture:
But when running on the device, I am getting to separated overlays. See the following pics:
The first one is the left part, the seond one is when starting scrolling while the last one is the second part.
Is it a bug? or there is a way to work around?
Thank you
OK.
This is defineitly Apple's bug.
I tested the code with an old 3gs phone and it works perfectly (line the pic of the simulator above).
I will report it to apple.
I downloaded the new iOS 6 and the problem solved.
Nobody talked to mee, not any help from apple. But at last it has been solved.
I've got an issue with my iphone App and i'm not sure if its an xcode project issue or a code issue (I'm leaning towards xcode project issue at the moment).
If I reset the iphone simulator and build and run my app it works fine. If I then do a build and debug again the app will crash straight away with no meaningful callstack. The app will continue to crash until I remove it and start again. I didn't previously have this issue which makes me think i've just changed some project setting recently by mistake.
Has anyone had this before or can anyone think or a reason for this issue?
Are you saving/retrieving state? Without any other details, that's the first area I'd look into. Also try setting breakpoints and debug to pinpoint the problem.
paul_sns is correct, try setting breakpoint on your AppDelegate class and step-over. Probably you're retreaving a state that is incorrect. You could also activate the debugging console (run the application in debug mode) to see where it crashes (the callstack).
OK I've finally got to the bottom of it. I had quite a lot of memory overwriting going on (a sizing issue with a 2d array) and this was why it wasn't giving me any useful information when it crashed. Thanks for all the help - am glad I stumbled upon the problem before I pulled all my hair out!