Android build fails on Expo SDK 56: HighlighterViewPackage and KeyboardInputPackage not found in PackageList.java
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.2k
- Forks
- 748
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 1
Description
Description
Android build fails when using react-native-ui-lib in a fresh Expo SDK 56 project. The same setup was previously working correctly with Expo SDK 54.
During the Android build process, compilation fails in PackageList.java because the generated package list references classes that cannot be found:
PackageList.java:80: error: cannot find symbol
new HighlighterViewPackage(),
^
PackageList.java:81: error: cannot find symbol
new KeyboardInputPackage(getApplication()),
^
Related to
- Components
- Demo
- Docs
- Typings
Steps to reproduce
- Create a new Expo SDK 56 project.
- Install
react-native-ui-lib. - Run Android build (
expo run:androidor EAS Build). - Build fails during native Android compilation.
- Observe the
PackageList.javaerrors shown above.
Expected behavior
The Android application should compile and build successfully after installing and configuring react-native-ui-lib, as it did with Expo SDK 54.
Actual behavior
The Android build fails because PackageList.java references HighlighterViewPackage and KeyboardInputPackage, which cannot be resolved during compilation.
More Info
Code snippet
npx create-expo-app@latest my-app
cd my-app
npm install react-native-ui-lib
eas build --profile development --platform android --local
Screenshots/Video
Build error:
PackageList.java:80: error: cannot find symbol
new HighlighterViewPackage(),
^
PackageList.java:81: error: cannot find symbol
new KeyboardInputPackage(getApplication()),
^
Environment
- React Native version: (React Native version bundled with Expo SDK 56)
- React Native UI Lib version: (please fill in your installed version)
- Expo SDK version: 56
Affected platforms
- Android
- iOS
- Web
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the Android build with a fresh Expo SDK 56 project and react-native-ui-lib, using expo run:android or the provided EAS command. Inspect the generated PackageList.java entries for HighlighterViewPackage and KeyboardInputPackage and the corresponding native package registration. Done means the Android application compiles successfully without unresolved package references.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, react-native
- Domain
- build-system, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100