I build my app in Xcode4.6 and run it on iPod5 with iOS7.
The table view is grouped, all cells are standard. Table is in editing mode for one section.
There is a very weird glitch on cells which are in editing mode. Problem is shown on the screenshot (with glitch and normal).
This "thing" appears only for a moment, I am able to catch it only in dispatch_async from viewDidAppear. Then after a moment it disappears by itself and all comes to normal (cellForRowAtIndexPath, layoutSubviews in cell are not called, I'm not reloading the table! - weirdest thing).
My table and cells are pretty complex, but I digged down and removed all unrelevant views.
Here table is transparent, red is color of the view behind it.
I have set cell.contentView.alpha to zero (all my views are added to it), and cell itself is green.
I tried cell.alpha = 0, in this case cell is not showing and there is no glitch, so it is definitely problem with a cell.
Please write any suggestions, I ran out of ideas. Thanks.
UPD. It appears that this only happens in edit mode. If I don't set it to YES, everything's ok.
UPD 2. The glitch appears when [table setEditing:YES] is called. If animated, it shows that this thing expands to a normal width of a cell and becomes normal.
I'm starting to think that it's unsolvable (obviously Apple won't fix it)
Since I asked this question I have noticed this bug in many iOS6 applications in AppStore.
I assume this is a bug with iOS6 apps built on Xcode4 that are run on iOS7 in compatibility mode.
I do not use Xcode4 anymore, and I don't support iOS6 in my apps.
So this question is neither relevant nor worth solving.
Related
I'm experiencing a weird issue with my Swift 2.0 app.
I have a (editable) UITextView defined in my storyboard.
If I leave the text property empty in the storyboard everything is working as expected. But when I enter the text Kaasje (in the storyboard and recompiling), the app freezes when loading the nib (navigating through segue) and the CPU jumps to 100% (the app remains stuck).
The app will never reach viewDidLoad at this point.
It makes no difference when changing between fonts or fontsizes, behavior remains.
Pausing in Xcode does not leave me with anything useful, the main thread is busy without specifying any function. Nothing is logged to output nor any logs are created.
I'm running iOS9 on a iPad Air, the app has a built target of iOS8 and runs landscape-only.
Has anyone ever experienced anything like this before, and might have an explanation for this behaviour?
As far as my assumptions: Something goes wrong when calculating the text-size which results in a infinite loop while either calculating the size or adjusting the frame.
P.S. It happens with other texts too, but "Kaasje" always fails. It seems to fail when the the text is only 1 line. Longer texts tend to succeed aswel as leaving it empty.
As suggested in the comments there seems to be a bug in Xcode 7 in combination with iOS9.
I ended up recreating the entire view, the problem did not occur again.
I have a weird issue in an iOS app written in Xamarin. That happens is that the lower left item from time to time loads late.
I'm not quite sure which information is relevant to this issue, since I tried to remove almost all complexity (stuff like custom delegate and and UICollectionViewFlowLayout)
What makes this even weirder is that when it loads it is shown for about a second and then disappears, until i start scrolling past it.
Has anyone experienced a similar issue?
I'm developing a WatchKit app for the Apple Watch. I "finished" the app originally when the first beta was out back in Nov/Dec.
I recently upgraded the the final release and somethings in WatchKit changed (as to be expected). I had to fix couple lines of code here and there since they changed how the app views start up.
Anyway, after fixing the issues I noticed that my WKInterfaceTable displays and scrolls almost correctly. The last row in the table gets cut off (as indicated in the screenshot below). Also, the scrollbar is very short - shorter than it should be (also in the screenshot). Anyone else experiencing this?
In the screenshot, the app has about 10 rows, I just scrolled way to the bottom with a bit of an extra pull just to show the cut-off from the last row... Notice the bottom of the row and the scrollbar at the top right.
I've included extra screenshots that may be helpful. I researched some tutorials on WKInterfaceTable and they're not really doing anything different than I am in the Interface Builder. I'm lost here.
I'm not making ANY UI modifications in code. I'm just letting WatchKit handle the UI as much as possible without any intervention from me.
Thanks!
Other Screenshots:
The scrollbar is short by design, this isn't a bug. That's how it's meant to be.
Regarding the cutting off of the last row, add the table into a WKInterfaceGroup, then set the group's height to 'Size to Fit Content'. That should fix it.
I found several problems with rotations in ios6 using iPAD...all of us...I resolved mostly all of them using the new method shouldAutorotate and shouldAutorotateToInterfaceOrientation. But in one of the views is not updating properly the rotation. You can see (more or less) what happen:
The top images describes the behaviour from landscape to portrait...if I change the rotation of my app in other different of the first image, and come back to the first tab, the app doesn't update properly the view in portrait.
The bottom images describes what happen when I am comming from portrait to landscape...in the last screen I can the half of the screen completely black.
My level in iOS is really basic I will like some tips...what do you think which could be the problem? because in other tabs is not happen of the same app it is not happen.
If you need a piece of code, let me know...thank you!
Try this:
https://github.com/alexth/TBSV
Sample how to have NavigationBar, TabBar and SplitViewController in one project with correct looking transitions between orienations
Thanks for your reaction (ironic). I've discovered what was the problem with the rotation only in a particular screen of my app. The problem is that the one that built the app before me, used one UISplitViewController inside of a UITabBarController. This mix of ViewController, in iOS 6 bring a bunch of problems, specially with the rotations. After thousands of tries, I found this link and it is solved.
UISplitViewController inside UITabBarController in iOS6:
http://objectiveseesharp.wordpress.com/
That's all.
Should I change the title of the question?
I have a tableView with a few sections. When I remove all rows from a section, I also remove the section with the UITableViewRowAnimationTop animation (so it slides up). When running the app on an iOS 4 device, the deleteSections: withRowAnimations: method correctly makes the section slide up and disappear behind whatever is above it. However on iOS 5, the section slides up but stays infront of whatever is above it, then disappears once it's finished sliding. What could be wrong?
FYI: I'm using iOS5 but have changed the iOS deployment target to iOS 4.0, so my app will run on all iOS version from 4 upward, and have changed the architecture to armv6 armv7
EDIT: For testing, I created an empty project with just a UITableViewController, which had a couple of sections with a couple of rows in each, nothing fancy. Got the same behaviour, so although I'm really hesitant to do this (because it's almost never the case), I'm going to go out on a limb and say this is a bug in iOS5?
Having a similar problem. Popping a view controller where the animation is supposed to slide the prior view in from the left (works fine on iOS 4). But on iOS 5 the bulk of the page appears immediately while only the bottom tab bar slides in from the left. Have single-stepped through the code on both versions and it appears to be taking the same path right up to the popViewControllerAnimated call.
Unfortunately this is a very complex app (unnecessarily complex, but that's another story) where most of the screens are dynamic, so it's hard to simplify down to a test case. No obvious solution so far.