Closed rastepanenko closed 17 hours ago
Thank you for your issue report. Please note that the following information is missing or incomplete:
Please update your issue with this information to help us address it more effectively.
Note: issues without complete information have a lower priority
Getting same in running yarn run android
in the expo example. Using jdk 17.0.12.
I confirm this issue @paulrinaldi @KrzysztofMoch I think this should be solved by using following doc: https://docs.expo.dev/modules/autolinking/ But monorepo should be better to apply it :/ let me know your expectations
@rastepanenko I don't think you have the same issue than the one reported by paul. Do you have the expo go issue ? please check other closed tickets which deals with the same issue
@freeboub I'm not using expo in this project. This is pure RN
@paulrinaldi Were you able to solve this problem?
@rastepanenko The issue with the sample are different as the RNV code is directly linked without autolink. Can you recreate your issue in a very basic sample you can share ?
I confirm this issue @paulrinaldi @KrzysztofMoch I think this should be solved by using following doc: https://docs.expo.dev/modules/autolinking/ But monorepo should be better to apply it :/ let me know your expectations
Thank you, I followed the steps linked there plus my intuition and was not able to fix this problem.
My expectations are that one can run yarn run install && yarn run android
in the examples/expo
directory without needing to run anything else.
I am suspicious are that there is no declaration of react-native-video
(even linking to like ../../src or whatever was there before) in the expo example.
Steps:
I ran the command: npx expo-modules-autolinking search
In the ouput, I see there are 6 packages that are not in the package.json
but are declared in the Podfile.lock
and do exist in the node_modules
folder. In the ouput, I also see two packages, "expo"
and "expo-splash-screen"
, which are in the package.json
but of different versions in the output than in the package.json
). I haven't come across this before linking.
Running npx expo-doctor
in this expo directory yields the following failure:
...
✖ Check for app config fields that may not be synced in a non-CNG project
✔ Check Expo config (app.json/ app.config.js) schema
✖ Check that packages match versions required by installed Expo SDK
...
Detailed check results:
This project contains native project folders but also has native configuration properties in app.json, indicating it is configured to use Prebuild. When the android/ios folders are present, if you don't run prebuild in your build pipeline, the following properties will not be synced: plugins, android, ios.
Advice: Add '/android' and '/ios' to your .gitignore file if you intend to use CNG / Prebuild. Learn more: https://docs.expo.dev/workflow/prebuild/#usage-with-eas-build
(node:5782) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
The following packages should be updated for best compatibility with the installed expo version:
@react-native-picker/picker@2.8.1 - expected version: 2.7.5
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.
Running 'npx expo install --check' changed the package.json's version of react native picker but after this, running yarn run android
, still yields the error in this issue.
I ran npx expo-modules-autolinking resolve --platform apple
and npx expo-modules-autolinking resolve --platform android
and after each I ran npx expo-modules-autolinking verify
which outputted "Everything is fine!"
Using yarn run start
+ a
yields same issue as well.
Also is the example/expo
project for testing tvOS or android phone/tablet?
I see, "react-native": "npm:react-native-tvos@~0.74.5-0"
which confuses me.
Also is the example/expo project for testing tvOS or android phone/tablet? I see, "react-native": "npm:react-native-tvos@~0.74.5-0" which confuses me.
this is for tvOS support... tvOS is not separated package as visionsOS so this is only way to do it (I have do it as expo docs says to do it)
I am little busy right now, but I will try to debug it on my side and get back to you - Also thanks for sharing you research
Oh ok, understood @KrzysztofMoch this is not high priority for me. However, it was not obvious to me that this was for TV support until now.
@paul-rinaldi I fixed it in the expo sample ! As we don't have any news from @rastepanenko let's close this issue
Version
6.7.0
What platforms are you having the problem on?
Android
System Version
Android 14
On what device are you experiencing the issue?
Simulator
Architecture
Old architecture
What happened?
The bug occurs when rendering the component with Video and only on Android. It works perfectly on iOS! I'm on RN 0.75.3, JS.
My Package.json file
Reproduction Link
No response
Reproduction
Step to reproduce this bug are: