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.
Related
At this time I'm trying to edit an app of mine to support iOS6+7 aswell as 3.5+4 inch displays.
However I'm trying to do this without changing the code. And it works fine...for one of my requirements.
First I tried fix the 3.5/4 inch display issue with autolayout/contraints. It worked well but either it looked good with iOS6 or iOS7. And I didn't find a way to fix the iOS6/iOS7 diffrence without adjusting tons of code.
Then I resetted my contraints, disabled autolayout and fixed the iOS6/7 issue via offsets (iOS6/7 Deltas). Worked fine too for resolving the other requirement.
Since you can't use offsets AND autolayout at the same time I'm wondering if it's not possible to fix both problems without either checking iOS version or display size in my code?
I didn't provide code or screenshots because it's a more general question and I'm trying to solve this issue without touching my code. However what I can say is that I'm using .xib files to create the views not knowing if that's a problem too...
Thanks in advance,
blaluma
if your using storyboard with autosizing you can achieve that one
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.
Consider the above's IB objects listing. Siblings further down the list should be on top of the siblings listed further up when rendered on the screen.
Under Xcode 4.5.2, everything is ok if iphone simulator 5.1 is used. But for simulator 6.0 the map just covers everything. The same if using actual devices (phones) for testing.
Hope that somebody knowledgeable could help.
Please also add comments if you do not (or do) find such a problem on simulator 6.0. Chances are the problem is related to how my project is setup.
Update :
Have setup a new test project with iOS 6 map view myself. There seems to be no problem with z-order at all. So the problem could relate to my code. Unfortunately, quite a lot have already been written, there wouldn't be enough time to go over everything for the time being. I suspect that it has something to do with the rootViewController property. My project initially followed a older scheme in which rootViewController was not used ...
I dont know if that order is reliable at all -- in the past definitly not and I am not conviced it is today :D. (even though apple claims it :D)
see: IPhone Interface Builder: Z-Index, Z-order of a button, image, ui element, etc?
(the 3rd answer currently. 7 votes)
The problem is solved by calling Window's bringSubviewToFront method. But I believe a better and more proper solution can be found given enough time.
First of all I want to say that I'm I aware that my question is probably way too vague to answer and may be closed/down-voted. I just hope for some inspiring brain-storming on possible solutions.
Here's the story:
My app was crashing on iPad 2, but not on iPad 1. I've fixed the crash related to unarchiving nib and now I have a very strange problem - my universal app still runs without any problems on 1st gen iPad with iOS 4.2.1 and 4.3.3, but not on (some/all?) iPads 2 with 4.3.3. Unfortunately I don't have an access to iPad 2 with iOS < 4.3.3 to test further and narrow down the problem.
My app has it's main screen displayed by using presentModalViewController. My modal VC is MGSplitViewController (it mimics native UISplitViewController and enhances its functionality). When my VC is presented, only "root view" is displayed and remaining part of screen for "detail view" is just black and empty however the controller is loaded and active (debug logs are printed etc.).
So on iPad 2 I have access to, it fails to display detail view properly, however I've heard from one user that it's fine on his iPad 2 (both iOS 4.3.3). App also works ok on iPhone/iPod regardless iOS version, so I assume it's related only to iPad code of my universal app.
I believe it may be more general issue with displaying views. I've tried to read view property of my detail view, which should force view to be displayed, but it didn't help. It may also be related to IB stuff (the initial nib unarchiving crash only on iPad 2??), but I think everything is wired ok in IB...
Anyone has a slightest idea how to investigate this problem?
EDIT: BTW: My iPad 2 is giving me hard time as it drops Wi-Fi connection very often. Other people are also reporting this kind of "feature". Can it be that it's just something wrong with my iPad 2?
EDIT2: the app is also not correctly displayed on iOS 3.2, 4.2 and 4.3.3 Simulator (via XCode 4), but gets displayed correctly on iOS 3.2, 4.2 Simulator via Xcode 3. Strange, isn't it?
Anyone has a slightest idea how to investigate this problem?
If you'll allow a somewhat vague answer to a somewhat vague question, then yes, I do have an idea.
To approach problems like this in general, bisection of the problem field is a great way to go forward:
You identify the general problem area. Could it be presentModalViewController in your case?
Then about halfway through the code in question, you set a breakpoint/write a message to a log file/play a sound/send a mail/tweet/whatever it takes to verify that your code has come that far without a crash.
Run it and see if your message has been produced.
If it has been produced, the problem is not in the first half, so it must be in the second half (a log message at the end of the identified problem area is useful, too, just to make sure that the crash actually happens before that).
On the other hand, if there is no trace of your log message, then the crash must occur in the first half, and you can rule out the second half of your code for this particular problem.
Now you repeat the algorithm by setting your breakpoint/log message about halfway into the culprit half you just identified.
Repeat until you find the problem. It won't take many iterations.
Of course, the crash may be due to some variable stored at a previous step or in another method, but now you know where to look.
Initially the app was crashing due to unarchiving the nib. I don't recall the exact crash output, but it was quite strange for me that same nib was properly unarchived on iPad 1 with same OS version, so I suspected that the problem lies in xib file... I've recreated the xib from scratch routing everything carefully and - bam! - it started working on both iPad 1 and iPad 2! How come some nibs aren't unarchived in a same way on same OS running different HW???
I am using a Data.plist file to populate my UITableView/Navigation-based Application with data. it works perfectly on the simulator, and it shows up all 261 names, with the subtitle. The detail view also works 100%.
But, no matter what I do, reboot, clean, comment out, it refuses to show up on my Device. (iPhone 3G, unfortunately. Soon to be iPhone 4).
I have a Footer on my Table View that calculates the amount of Cells and totals them up for me. "Movies: 261" is what it shows. Yes, my app is an in-house only app that is my DVD Index.
But, on the Device, it shows "Movies: 0" even though the Data.plist is there, and everything should be working.
Is there anything I'm doing wrong? Can anyone help me?
Thank-you.
Sorry, problem fixed. Turns out the iPhone itself is CaSe SeNsItIvE where as the Simulator is not. So, if the PLIST file you're using is called "Data.plist" and it's referenced as "data.plist" in your code, it will NOT populate on the Device.
I hope this helps everyone who had the same problem as I did. :)
Thanks,
BenBen