I don't know why the OP need native pickers, but from my perspective iOS users expect consistency and don't understand why an iOS app would not use native pickers as probably 99% of all apps do. iOS users basically don't care about developer considerations and CN1 limitations. I had this feedback from early tests of my app. Not sure if absence of native pickers is make-or-break issue, but definitely an app doesn't score any points from it.
And personally, I hadn't even realized they had been deprecated on iOS. There are also a couple of other differences/regressions between native iOS apps and CN1 apps I've noticed: no (working) support for scroll-to-top when tapping status bar, not possible to select displayed text for copy/paste or Look Up, different feel of 'tensile' dynamics (eg bounce on scroll to top/bottom). On Saturday, May 29, 2021 at 6:58:14 AM UTC+2 Shai Almog wrote: > Native pickers break with every release of iOS. As a result we deprecated > them on iOS. I'm not sure if we'll fix them. > The question is: why do you need them? > > On Friday, May 28, 2021 at 2:07:06 PM UTC+3 [email protected] wrote: > >> We have noticed that implementing native pickers in ios does not work. >> We would like to find out why this happens. >> > -- You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/codenameone-discussions/be967d53-ea2c-4a55-914f-1b21b865a025n%40googlegroups.com.
