I'm running a Meteor server and a React-Native client (working in iOS mainly for now). Since I updated to React-native 0.33 the MeteorListView Component throws the following error:
My 'UserDos' follows the example of InProgress-team/react-native-meteor. When replacing the MeteorListView with a regular ListView everything works fine. Is anyone experiences this issue or can pinpoint/direct me to solving the issue?
Version
"react": "^15.3.1",
"react-native": "^0.33.0",
"react-native-lock": "^0.4.0",
"react-native-meteor": "^1.0.0-rc15",
"react-native-scrollable-tab-view": "^0.6.0",
"react-redux": "^4.4.5",
"redux": "^3.6.0",
"redux-thunk": "^2.1.0",
Fixed by reinstalling macOS and fresh install of React-native and dependances. Bit extreme solution but probably some complications with development version and upgrades; did the trick though!
Related
This Error is shown when creating the Android build:
It is too late to set sourceCompatibility
It has already been read to configure this project.
Consider either moving this call to be during evaluation,
or using the variant API.
This is what i'm running: "react": "18.1.0", "react-native": "0.70.6", "react-native-navigation": "^6.4.0"
I should be able to create android builds.
I have been contributing to a small open source project and found that when I used lessc (compiler) and prettier on windows 10 build 19043,
I got a significantly different result (final css file) than on ubuntu 20.04.
This google slides ([link][1]) documents the 2 intentional changes to the lessc file, then the 91 unintentional changes after running the compiler (resulting from lessc and prettier)
after running the exact same compile process on ubuntu, I got only the 2 intentional changes and nothing extra. My intentional changes are documented in a pull request here: [link][2]
These are the project dependencies from the .json file.
"devDependencies": {
"axios": ">=0.21.1",
"clean-css-cli": "^4.3.0",
"concurrently": "^5.3.0",
"less": "^3.13.1",
"less-watch-compiler": "^1.15.1",
"lessc": "^1.0.2",
"lite-server": "^2.6.1",
"minimist": "^1.2.3",
"node-less": "^1.0.0",
"object-path": ">=0.11.5",
"onchange": "^7.1.0",
"prettier": "^2.3.0"
Any idea why lessc or prettier would compile differently on linux vs windows? I am new to all this so forgive me if I've missed something obvious, thanks!
edit: I added 2 links, 1 for the windows errors and the 2nd with the correct linux output.
Thanks for the help!
[1]: https://docs.google.com/presentation/d/1dGjp5UEpkk4apojAtlNQg5hb2wktTKOgROU08sUN1OM/edit?usp=sharing
[2]: https://github.com/sButtons/sbuttons/pull/1397/commits/b1b1d6ddb3c15780e1fb3309fd637f3eec426106
I'm developing an app using Expo, using the Firebase JS SDK (https://docs.expo.io/guides/using-firebase/), only for Authentication and to use the Cloud Firestore Database. It works fine on browser but when I switch to Expo Go I get this error:
ReferenceError: Can't find variable: IDBIndex
It's my understanding that the Firebase SDK should work fine aside from when using Analytics, which I'm not using. I have spent hours googling this issue but most people refer to an issue with Analytics, so any help would be really appreciated!
My package.json:
"dependencies": {
"#react-native-community/masked-view": "0.1.10",
"#react-navigation/native": "^5.9.4",
"#react-navigation/stack": "^5.14.4",
"expo": "~41.0.0",
"expo-status-bar": "~1.0.4",
"firebase": "8.2.3",
"react": "16.13.1",
"react-dom": "16.13.1",
"react-native": "https://github.com/expo/react-native/archive/sdk-41.0.0.tar.gz",
"react-native-datefield": "^0.1.0",
"react-native-gesture-handler": "~1.10.2",
"react-native-reanimated": "~2.1.0",
"react-native-safe-area-context": "3.2.0",
"react-native-screens": "~3.0.0",
"react-native-web": "~0.13.12"
},
"devDependencies": {
"#babel/core": "^7.9.0"
}
I fixed this issue by using firebase#9.1.0. In the expo docs they mention that they are using this version in their example. https://docs.expo.dev/guides/using-firebase/
With newer versions of Firebase I encounter the same issue.
edit - There is something strange: mongo appears in both package.json and in .meteor/packages files (should it appear in package.json at all?? it wasn't there before the update) but in different versions. here is my package.json:
{
"name": "something",
"version": "1.1.1",
"private": true,
"scripts": {
"start": "meteor run"
},
"dependencies": {
"#babel/runtime": "^7.0.0-beta.49",
"babel-runtime": "^6.26.0",
"bootstrap": "^3.3.7",
"google-protobuf": "^3.5.0",
"grpc": "^1.12.2",
"grpc-tools": "^1.6.6",
"meteor-node-stubs": "^0.3.3",
**"mongodb": "^3.1.0-beta4",**
"react": "^16.4.0",
"react-dom": "^16.4.0",
"react-progressbar.js": "^0.2.0",
"react-router": "^3.2.1",
"react-router-dom": "^4.2.2"
}
}
and here is my .meteor/packages:
meteor-base#1.3.0 # Packages every Meteor app needs to have
mobile-experience#1.0.5 # Packages for a great mobile UX
**mongo#1.4.2 # The database Meteor supports right now**
blaze-html-templates#1.0.4 # Compile .html files into Meteor Blaze views
reactive-var#1.0.11 # Reactive variable for tracker
tracker#1.1.3 # Meteor's client-side reactive programming library
standard-minifier-css#1.4.0 # CSS minifier run for production mode
standard-minifier-js#2.3.1 # JS minifier run for production mode
es5-shim#4.7.0 # ECMAScript 5 compatibility for older browsers
ecmascript#0.10.6 # Enable ECMAScript2015+ syntax in app code
shell-server#0.3.1 # Server-side component of the `meteor shell` command
session#1.1.7
tarang:ssl
After updating to 1.6.1.1, my app won’t run, crashing with message 'Error: Cannot find module “mongodb” '.
Tried to run meteor npm install, even took away the entire node_modules folder and built it again.
Tried to run meteor npm update.
Tried to run meteor npm install mongodb.
Tried to downgrade back to version 1.6.0.1.
Still can’t find mongodb.
Important - mongodb is there, all collections are there - I can access it through the terminal with "meteor mongo".
Any help?
If it helps - The data in the db can be erased if there is no other way.
(running on ubuntu 16.04)
Thanks
In the end, the problem was not in the project but in meteor globally, so I uninstalled and re-installed meteor globally, and everything got back to normal…
Thank you all!
I have a nodejs GraphQL app running with the following
"graphql": "^0.10.5",
"graphql-errors": "^2.1.0",
"graphql-server-core": "^1.1.0",
"graphql-server-express": "^1.1.0",
"graphql-server-module-graphiql": "^1.1.0",
"graphql-subscriptions": "^0.4.4",
"graphql-tools": "^1.2.1",
"subscriptions-transport-ws": "^0.7.3",
Using this configuration, I can define a subscription in graphiql and watch the result appear in the output pane replacing the boilerplate message "Your subscription data will appear here after server publication!".
If I switch to the latest version of susbcriptions-transport-ws i.e.
"subscriptions-transport-ws": "^0.8.2",
this no longer works; the boilerplate message does not appear in the output pane and instead I get the cryptic [object] [object] message.
I've not been able to find any statement about version compatibility between graphiql and subscriptions-transport-ws; does anyone know if this version mix is supported?
I resolved the [Object Object] error in graphiql by reverting to these versions of following libraries in package.json:
"graphql-subscriptions": "^0.4.3",
"graphql-tools": "^1.0.0",
"subscriptions-transport-ws": "0.7.3",