Cannot open program database (RN Windows)
marcosrdz opened this issue · 5 comments
marcosrdz commented
Bug report
Summary
Unable to compile on react-native-windows
Environment info
react-native info
output:
info Fetching system and libraries information...
System:
OS: Windows 10 10.0.19042
CPU: (2) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
Memory: 926.15 MB / 4.00 GB
Binaries:
Node: 14.17.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.5 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.14.13 - C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK:
AllowDevelopmentWithoutDevLicense: Enabled
Versions: 10.0.18362.0, 10.0.19041.0
IDEs:
Android Studio: Not Found
Visual Studio: 16.10.31410.357 (Visual Studio Community 2019)
Languages:
Java: Not Found
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.1 => 17.0.1
react-native: 0.64.2 => 0.64.2
react-native-windows: 0.64.14 => 0.64.14
npmGlobalPackages:
*react-native*: Not Found
Library version: 2.1.1
namrog84 commented
It looks like your bluewallet project is looking for a RNLocalize.pri file (which doesn't exist).
While pri files are package resource indexing files, at first glance it looks like BlueWallet is expecting there to be on in RNLocalize for some reason. I think we need to figure out why and stop it from expecting it.
A few things to potentially try/investigate.
- Check your solutions configuration manager and make sure appropriate things are set to build. (I found a stack overflow referencing something might not be set to build that should be.
- Could you right click RNLocalize and do Build Project (independently of anything else) and see if it builds. Then share the 'output' (as Error List sometimes hides some useful information)
- Double check bluewallet's vcxproj and other related build scripts to make sure it isn't trying to expect or do anything special with RNLocalize.
- Look around and see if there is any special code related to PRI or resource indexing file that might be relevant.
zoontek commented
@marcosrdz Does it solve your issue?
macrozone commented
@macrozone Does it solve your issue?
wrong user pinged ;-)
zoontek commented
@macrozone Does it solve your issue?
wrong user pinged ;-)
Oups indeed, sorry!