Skip to content

timeZoneName and minimumDate incompatibility #1028

@stianjensen

Description

@stianjensen

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

  1. 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).
  2. Then, set the the current date on your device to the first of the month, for instance any time on December 1st.
  3. Also provide a minimumDate that can be today's date.
  4. 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:

  1. The calendar should have been acting like the device is in the timezone according to the provided timeZoneName
  2. 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions