With Widget 2.0 if tapping tableviews, they "slide down" and disappear almost off-screen, and on a second tap they slide back to their original position.
This seems like some sort of "layer dismissal" functionality, but why would they suddenly appear on tableviews?
Anyone knows why this happens?
There were serious bugs when they realeased Widget 2.0. Tableviews are implemented using scrollview which still contain a lot of bugs. I already submited 2 bugs but it will take some time until they will fix them. Try to install the latest corona build and check the forum or try to submit this bug.
Related
I am dealing with a weird bug on Ionic's iOS native build where I sometimes cannot swipe back or switch tabs once I transition to a new page using router.navigateByURL(...), and trying to debug this issue has been troublesome since I can't "see" how the gestures are handled. Does anyone know where I should be looking in the code for handling transition gestures?
Here's a video demo of the problem: https://streamable.com/hk9c0
In the video, you can see me:
Swiping down to refresh using the ion-refresher element and you can see the page beneath (already entered a bug report for that part: https://github.com/ionic-team/ionic/issues/18284 )
Trying to tap the back arrow in the left corner
Attempting to swipe left to right to go back a page (hard to show that one)
Tapping the bottom tabs to transition to new tab, at one point, I tap on a tab that has an ion-fab element which appears in the bottom right because its z-index is higher than the "stuck" page.
Currently the best I've been able to do is by looking at the css classes that are added to the pages, but it's not much use....
Where app-release is the page you can see in the video and app-home is the page underneath the stack. It's my understanding that Ionic uses hammer.jsfor gestures, so I added it as a tag, please correct me if I am wrong. I cannot, for the life of me, recreate this bug consistently, but will often trigger 1 out of 50 tries.
I've been digging through the utils in Ionic Core to see where elements are being added and removed, with no luck.
I created a bug request for this here as well: https://github.com/ionic-team/ionic/issues/18305
Are you using #angular/animations to make the transitions between the pages? I had some issues like yours, as you can see in my question.
Router navigate on Ionic with animation blinking on ios using angular animations
If I am right about the use of #angualar/animations I suggest to use a custom animation of the Ionic itself, and not te angular's. You can see an working example here of its use here:
https://github.com/mhartington/ionic4-custom-animation
Since I have less tem 50 rep I cant comment so I had to post this anwser not knowing if it was really your case. Hope it helps.
I have issue when I try to push view controller in willTransitionToPresentationStyle:. The view was blinking for a split second before it fully expanded. It might be a small glitch or bug since iOS 10 and Xcode 8 are still in beta. But when I manually requested to change presentation style to MSMessagesAppPresentationStyleExpanded by calling requestPresentationStyle: after I push view controller, it went to expand mode more smoothly. Does anyone have similar issue?
I have had similar problems with transitions in iMessage apps. I think this should improve considerably when iOS 10 and Xcode 8 come out of beta, but for now we have to deal with Xcode's bugs.
There's a few things I've done to make this look better. Inside my extension I have a method that checks the presentation style every time the view changes. This method manages two different UIs - one for MSMessagesAppPresentationStyleExpanded and one for MSMessagesAppPresentationStyleCompact. This method hides and shows specific views accordingly. In my compact UI I have a button that allows the user to expand the interface by clicking it (this is basically the same as clicking the up arrow at the bottom right of the screen).
I've noticed that if you let the user expand the messages app after the view has been loaded for a while the transitions are much smoother and less buggy. Not sure why this is the case, but you should give it a try. Also, I've found segues to be extremely buggy, so that's why I went with keeping everything on one view controller.
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.
If youre working with small slide you will notice they often stall halfways thru the slide. im using slide and not fade. Ive tested this on the basic flexslider example there is. It doenst matter if its a big og small slide if you slide the picture to 50% and you leave your finger from the slide, going straight down, then the image is stuck with 50% of to images.. Is this a bug or is there a solution? tested on ios 6 phone gap
edit it doenst have to be 50% you its everywhere u start sliding images and move the finger out of the slider then the sliding animation is stopped and youre stuck with something of two images.
Solution: Its currently a bug according to github A minor bug with no one to fix it anytime soon.. However i experienced severals flicker bugs when creating a slider on a transformed moved div...
therefor the solution for me was use iosslider instead. Its perfect! ive tried all sliders out there this one does it all with no bugs!!!.. Its free for personal use however not free for commercial :/ anyways its the best and there really isnt an alternative to what i need a slider for.
Say thank you with +1 if you went ahead and downloaded iosslider :) You will be satisfied i promise!
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.