- ABP Framework version: v0.9.22
For some reason, the previous thread about the upgrade of the React Native / Expo template was closed without another one being opened so we decided to open one ourselves as there seem to be multiple problems still that needs to be solved. Maybe others have had better luck, but for us, it is not even working to launch the Expo Web with a newly created project with default configuration so we have not tried to use it for an actual production project yet. If someone else has, please share your experience, hopefully it is working better for others.
We would really need some input from ABP Team about the future of the React Native / Expo template and if it is still a first class citizen. That said, we truly hope and believe that these bugs will be ironed out and that ABP will again have a working React Native / Expo template which has been missing for several months now. Lets work together to make this great.
Thanks.
11 Answer(s)
-
0
Output from Expo-doctor
npx expo-doctor
Enabled experimental React Native Directory checks. Unset the EXPO_DOCTOR_ENABLE_DIRECTORY_CHECK environment variable to disable this check. ✔ Check package.json for common issues ✔ Check Expo config for common issues ✔ Check native tooling versions ✔ 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 for issues with Metro config ✔ Check npm/ yarn versions ✖ Validate packages against React Native Directory package metadata ✖ 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 ✔ Check that native modules use compatible support package versions for installed Expo SDK ✖ Check that packages match versions required by installed Expo SDK
Detailed check results:
Error: Problems validating fields in *********\react-native\app.json. Learn more: https://docs.expo.dev/workflow/configuration/ • Field: scheme - 'scheme' must match pattern "^[a-z][a-z0-9+.-]$". • Field: scheme - must be array. • Field: scheme - must match exactly one schema in oneOf.
The package "@types/react-native" should not be installed directly in your project, as types are included with the "react-native" package.
The following issues were found when validating your dependencies against React Native Directory: Untested on New Architecture: react-native-chart-kit Unmaintained: expo-random, react-native-chart-kit, reanimated-bottom-sheet, redux-persist No metadata available: prop-types, react-native-base64, redux-saga, yup Advice:
- Use libraries that are actively maintained and support the New Architecture. Find alternative libraries with https://reactnative.directory.
- Add packages to expo.doctor.reactNativeDirectoryCheck.exclude in package.json to selectively skip validations, if the warning is not relevant.
- 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.
The following packages should be updated for best compatibility with the installed expo version: react-native@0.76.5 - expected version: 0.76.6 react-native-screens@4.1.0 - expected version: ~4.4.0 Your project may not work correctly until you install the expected versions of the packages. Found outdated dependencies Advice: Use 'npx expo install --check' to review and upgrade your dependencies.
One or more checks failed, indicating possible issues with the project.
-
0
As previously reported in the ABP 9 bug & features thread:
First error after having created a new project in ABP 0.9.22 and just running npx expo start and trying to browse Expo Web
Console:
Refused to execute script from 'http://localhost:8081/node_modules/expo/AppEntry.bundle?platform=web&dev=true&hot=false&transform.engine=hermes&transform.routerRoot=app&unstable_transformProfile=hermes-stable' because its MIME type ('application/json') is not executable, and strict MIME type checking is enabled.
Terminal:
Web Bundling failed 6705ms node_modules\expo\AppEntry.js (2320 modules) Unable to resolve "normalize-css-color" from "node_modules\native-base\lib\module\utils\react-native-web-fucntions\normalizeColor.js"
-
0
Linking to this ticked as well related to the same topic
https://abp.io/support/questions/8706/abp-studio-0922-not-downloading-correct-react-native-template-with-microservices-template
-
0
Thank you for sharing the output from Expo-doctor. I would like to assure you that the concerns mentioned, such as validation warnings and package compatibility, are being addressed in upcoming releases.
These issues should not disrupt the core functionality of the app directly in the current version, but we recommend keeping an eye out for the next updates, which will resolve these points and improve overall compatibility.
-
0
These issues should not disrupt the core functionality of the app directly in the current version, but we recommend keeping an eye out for the next updates, which will resolve these points and improve overall compatibility.
This is probably true but mostly because of the fact that at least we could not get it to work at all. We only tried running Expo Web in a newly created project which turned out to be a no go so never tried getting it to run as a mobile app.
When will the new release be available ?
Thanks.
-
0
You can follow the release notes that is announced here.
-
0
You can follow the release notes that is announced here.
Thanks, but that does not answer my question about when updated templates will be available :)
Have you confirmed that the produced projects from the current template works as mobile apps even though they do not seem to work as Expo Web (which is the only thing we tried so far)?
Thanks.
-
0
Hi again @improwise, I appreciate your follow-up.
We have run the necessary tests, and the projects generated from the current template do work as mobile apps. While we acknowledge the issue with Expo Web, we can confirm that this does not impact mobile functionality.
We will proceed with small fixes that do not disrupt the expected flow, ensuring a smooth experience. Once we have completed the necessary maintenance—including the aspects you mentioned—these updates will be included in the release notes.
-
0
Please fix the problem that tickets get closed even though you just reopened them
-
0
We do not typically close tickets unless they are fully resolved or inactive for some time. We understand the issue you are facing and are actively working on a fix to prevent this from happening again. Thanks for your patience.
-
0
We do not typically close tickets unless they are fully resolved or inactive for some time. We understand the issue you are facing and are actively working on a fix to prevent this from happening again. Thanks for your patience.
The problem seems to be an overzealous bot with really poor patience that decides to close even unresolved ticket way too early.