timeZoneName and minimumDate incompatibility
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 48/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Stack tecnológico
- ios, javascript, react-native
Línea de trabajo
Start by reading the iOS date picker code that handles timeZoneName, minimumDate, and the visible calendar month; the issue does not name specific files or tests. Reproduce on iOS with datetime mode, a time zone ahead of the device, the date set to the first of the month, and minimumDate set to today. Done means the picker opens without crashing and respects both the configured time zone and minimum date.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Bug report
Summary
On iOS, with mode="datetime", set timeZoneName to a zone that's ahead of you. Say for instance that your phone is set to London time, you can hardcode this setting to Paris time (one hour ahead).
Then, set the the current date on your device to the first of the month, for instance any time on December 1st.
Also provide a minimumDate that can be today's date.
You'll now see a crash when you open the datepicker, saying "Exception thrown while executing UI block: Unable to set a visible month that is before the minimum or after the maximum date.
_44-IRCTUIManager"
Reproducible sample code
Steps to reproduce
- On iOS, with mode="datetime", set timeZoneName to a zone that's ahead of you. Say for instance that your phone is set to London time, you can hardcode this setting to Paris time (one hour ahead).
- Then, set the the current date on your device to the first of the month, for instance any time on December 1st.
- Also provide a minimumDate that can be today's date.
- You'll now see a crash when you open the datepicker, saying "Exception thrown while executing UI block: Unable to set a visible month that is before the minimum or after the maximum date.
_44-IRCTUIManager"
Describe what you expected to happen:
- The calendar should have been acting like the device is in the timezone according to the provided timeZoneName
- And minimumDate should still be respected, without crashing.
Environment info
npx react-native info output:
System:
OS: macOS 15.6.1
CPU: (10) arm64 Apple M2 Pro
Memory: 130.22 MB / 16.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 22.14.0
path: ~/.nvm/versions/node/v22.14.0/bin/node
Yarn:
version: 1.22.22
path: /opt/homebrew/bin/yarn
npm:
version: 10.9.2
path: ~/.nvm/versions/node/v22.14.0/bin/npm
Watchman:
version: 2025.03.10.00
path: /opt/homebrew/bin/watchman
Managers:
CocoaPods:
version: 1.13.0
path: /Users/stiaje/.rbenv/shims/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 24.2
- iOS 18.2
- macOS 15.2
- tvOS 18.2
- visionOS 2.2
- watchOS 11.2
Android SDK:
API Levels:
- "30"
- "31"
- "33"
- "34"
- "35"
Build Tools:
- 31.0.0
- 33.0.0
- 33.0.1
- 34.0.0
System Images:
- android-31 | Google APIs Intel x86 Atom_64
Android NDK: Not Found
IDEs:
Android Studio: 2024.2 AI-242.23726.103.2422.12816248
Xcode:
version: 16.2/16C5032a
path: /usr/bin/xcodebuild
Languages:
Java:
version: 21.0.4
path: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/javac
Ruby:
version: 2.7.8
path: /Users/stiaje/.rbenv/shims/ruby
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.3.1
wanted: 18.3.1
react-native:
installed: 0.75.5
wanted: 0.75.5
react-native-macos: Not Found
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: true
newArchEnabled: false
iOS:
hermesEnabled: true
newArchEnabled: false
Time zone name (If the problem you have is related to unexpected time / date. See list in https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).
datetimepicker version: 8.5.1
iOS / Android version: iOS 18.2
- Lenguaje dominante
- JavaScript
- Estrellas
- 2.9k
- Forks
- 459
- Merge medio
- 4 d 16 h
- PR fusionados (30 d)
- 5
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de react-native-datetimepicker/datetimepicker
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
-
Dificultad 3/5 1-2 días Aptitud para principiantes 58/100
react-native-datetimepicker/datetimepicker#1070 · 1 comentario ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 52/100
-
DateTimePickerAndroid.open() throws "Cannot read property" error on RN 0.78.3 new architectureAbierto
Dificultad 3/5 1-2 días Aptitud para principiantes 55/100
react-native-datetimepicker/datetimepicker#1047 · 6 comentarios ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 20/100
react-native-datetimepicker/datetimepicker#1046 · 1 comentario ·
Todos los issues de react-native-datetimepicker/datetimepicker
Issues similares
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 87/100
OWASP/CheatSheetSeries#2905 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
ComposioHQ/composio#5249 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
zilliztech/memsearch#838 ·
Los mantenedores suelen responder en 1 día
-
[DOCS] Nine one-colon directives hide code examples and notes in the reference docs (e.g. CustomJS)AbiertoTRIAGE
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
cdx-audit output written to a pipe is cut off at 64 KiBQuizá libre de nuevo Un pull request para esta issue se cerró sin fusionarse. Abiertobug mode:cli
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Los mantenedores suelen responder en 1 día