Bug with style activeDayContainerStyle

[Mokutte]

I'm having an issue where the borderRadius in activeDayContainerStyle doesn't match my custom component, but I can't seem to change this behavior.

theme={{
monthTitleTextStyle: {
color: COLORS.Black,
fontFamily: 'Onest',
fontWeight: '400',
fontSize: 16
},
emptyMonthTextStyle: {
color: COLORS.Gray.ContentSecondary,
fontFamily: 'Onest',
fontWeight: '400',
fontSize: 17
},
weekColumnsContainerStyle: { display: 'none' },
weekColumnTextStyle: {
color: COLORS.Gray.ContentSecondary,
fontFamily: 'Onest',
fontWeight: '400',
fontSize: 17
},
nonTouchableDayTextStyle: {
color: COLORS.Gray.Border
},
dayContainerStyle: { height: 53, marginVertical: 1.5, borderRadius: 0, width: 48},
activeDayContainerStyle: {
backgroundColor: 'red' ,
borderRadius: 0,
},
}}

style my custom component - {
width: 53,
height: 53,
backgroundColor: COLORS.Black,
borderRadius: 100,
}

OS: macOS 14.1.1
CPU: (8) arm64 Apple M1 Pro
Memory: 80.56 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 21.0.0 - /var/folders/p5/31l93j0s09z6z_pqvf_mwcsc0000gn/T/yarn--1703426200592-0.5837184130403736/node
Yarn: 1.22.19 - /var/folders/p5/31l93j0s09z6z_pqvf_mwcsc0000gn/T/yarn--1703426200592-0.5837184130403736/yarn
npm: 10.2.0 - /opt/homebrew/bin/npm
Watchman: 2023.10.09.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.11.3 - /Users/georgijberidze/.rvm/gems/ruby-2.7.5/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 23.0, iOS 17.0, macOS 14.0, tvOS 17.0, watchOS 10.0
Android SDK:
Android NDK: 22.1.7171670
IDEs:
Android Studio: 2021.3 AI-213.7172.25.2113.9123335
Xcode: 15.0/15A240d - /usr/bin/xcodebuild
Languages:
Java: 11.0.13 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.1.0 => 18.1.0
react-native: 0.70.6 => 0.70.6
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. You may also mark this issue as a "discussion" and I will leave this open.