Hi @jvzTrifork, Thank you for reporting this issue. We will look into it.

Hi there. We have the exact same problem. Do you have any workarounds? Or when will it be updated? We have a big form and lots of Safari users...but changing it to another Select element is painful...

We ended up downgrading to version 3.4.6 which does not have this bug.

Any update on this issue?

Also experiencing this, version 3.4.19. Does anyone know of a compatible Select element for a replacement?

Also experiencing this. Has there been any progress made on this issue?

Any update?

We have this issue too. I'd appreciate any workaround or fix, or even suggestions to other select libraries.

@Krithikj20

After some digging, I've found out the reason is the prop selection in the commonInput rendered on the Select component. After cloning the select component inside my project and removing this prop (which is extracted in nonLayoutProps) the bug goes away.

Also, the component works just fine without this prop. Perhaps it should be added only on safari on web.

not only on Safari, mobile Chrome also has this issue. Any update?

@lts-po and I made a work around in our codebase for this issue by creating two custom components that inherit Select.

The first is basically a no-op but needs to wrap Select from native-base
https://github.com/spr-networks/super/blob/main/frontend/src/components/Select.js

The second is for the web clients
https://github.com/spr-networks/super/blob/main/frontend/src/components/Select.web.js

Here is the implementation

import React from 'react'

import { Select as NBSelect } from 'native-base'


const Select = (props) => {
  const isSafari = () =>
    /Safari/.test(navigator.userAgent) &&
    /Apple Computer/.test(navigator.vendor);


  return (
    <NBSelect {...props} selection={isSafari() ? 1 : null}/>
  );
};

Select.Item = NBSelect.Item
export default Select
export { Select }

Mobile Chrome for iOS has the same issue.

Mobile Chrome for iOS has the same issue.

Yes confirm. Maybe this problem has disappeared in Glustack-ui?