-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Before submitting a new issue
- I tested using the latest version of the library, as the bug might be already fixed.
- I checked for possible duplicate issues, with possible answers.
Bug summary
I copied the repo code directly into the root of my project, which was created with npx create-expo-app@latest
. It sets up perfectly, but I may be missing something on the presentation of the slider handle locations. When I adjust either one of the handles, I see proper values printed, but the handle snaps right back to the initialMin or initialMax, depending on which handle I grab. I'll include a video here to show the behavior.
Screen.Recording.2025-07-16.at.11.37.00.AM.mov
Environment info
npx expo-doctor --verbose
:
✔ Check package.json for common issues
✔ Check Expo config for common issues
✔ Check if the project meets version requirements for submission to app stores
✔ Check for common project setup issues
✔ Check dependencies for packages that should not be installed directly
✔ Check for app config fields that may not be synced in a non-CNG project
✔ Check npm/yarn versions
✔ Check native tooling versions
✔ Check for issues with Metro config
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check that native modules do not use incompatible support packages
✔ Check for legacy global CLI installed locally
✖ Validate packages against React Native Directory package metadata
✔ Check that packages match versions required by installed Expo SDK
✔ Check that native modules use compatible support package versions for installed Expo SDK
14/15 checks passed. 1 checks failed. Possible issues detected:
✖ Validate packages against React Native Directory package metadata
The following issues were found when validating your dependencies against React Native Directory:
No metadata available: react-native-fast-range-slider
Advice:
Update React Native Directory to include metadata for unknown packages. Alternatively, set expo.doctor.reactNativeDirectoryCheck.listUnknownPackages in package.json to false to skip warnings about packages with no metadata, if the warning is not relevant.
1 check failed, indicating possible issues with the project.
package.json
:
"dependencies": {
"@expo/vector-icons": "^14.1.0",
"@react-navigation/bottom-tabs": "^7.3.10",
"@react-navigation/elements": "^2.3.8",
"@react-navigation/native": "^7.1.6",
"expo": "~53.0.17",
"expo-blur": "~14.1.5",
"expo-constants": "~17.1.7",
"expo-font": "~13.3.2",
"expo-haptics": "~14.1.4",
"expo-image": "~2.3.2",
"expo-linking": "~7.1.7",
"expo-router": "~5.1.3",
"expo-splash-screen": "~0.30.10",
"expo-status-bar": "~2.2.3",
"expo-symbols": "~0.4.5",
"expo-system-ui": "~5.0.10",
"expo-web-browser": "~14.2.0",
"react": "19.0.0",
"react-dom": "19.0.0",
"react-native": "0.79.5",
"react-native-fast-range-slider": "^0.3.3",
"react-native-gesture-handler": "~2.24.0",
"react-native-reanimated": "~3.17.4",
"react-native-safe-area-context": "5.4.0",
"react-native-screens": "~4.11.1",
"react-native-web": "~0.20.0",
"react-native-webview": "13.13.5"
},
amitpdev
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working