constructor FBSDKPackage in class FBSDKPackage
cannot be applied to given types;
new FBSDKPackage(mCallbackManager),
^
required: no arguments
found: CallbackManager
reason: actual and formal argument lists differ in length
1 error
https://github.com/facebook/react-native-fbsdk/issues/429
have tried all solutions in the above link and still facing same issue
react-native: 0.59.9
If you use the latest version of react-native-fbsdk you will no longer to have pass the callbackManager to the constructor and the reason I strongly recommend you to upgrade it is that's the requirement of facebook to Upgrade to SDK v5.0 for new privacy features and the previous versions will stop working.
Related
In relation to this post:
After upgrading from revit 21 to 22 in my company, we can no longer view anything else than the default 3D model in our forge viewer. Initially, i thought the issue arose due to this warning:
"Deprecated API usage: No "GlobalWorkerOptions.workerSrc" specified.".
However, i got that same message in the console of a working implementation i made today, leading me to believe that it has nothing to do with this warning at all.
However, i also see another warning:
"Warning: getOperatorList - ignoring errors during "GetOperatorList: page 0" task: "r: Cannot read properties of undefined (reading 'X')"."
I have tried creating a new nuxt app on Node version 14.9.0, implemented a forge viewer in accordance with the official v7 documentation, and the bug is no longer present.
I then tried to mimic that in my actual production app where the problem exists, by running it on Node version 14.9.0 instead of 10.0.0, getting rid of my entire forge implementation and implemented a simple viewer like above. That did not solve the problem, and i still see above warnings in the console.
The warning is thrown in pdf.worker.jss, which is loaded in via "webpack://adsk/node_modules/#adsk/pdfjs-dist/legacy/build/pdf.worker.jss".
I hope someone has a suggestion.
I created a React Native project from Expo. Then I wanted to add Flow to it. I noticed in my node_modules/react-native folder there was a .flowconfig so I copied that to the root of my project. After running flow I got some warnings from files in node_modules/exponent so I added an ignore for that whole folder. Afterwards, I still get many errors when running flow. Here are a few:
node_modules/react-native/Libraries/Animated/src/AnimatedImplementation.js:227
227: /* $FlowFixMe */
^^^^^^^^^^^^^^^^ Error suppressing comment. Unused suppression
node_modules/react-native/Libraries/Animated/src/AnimatedImplementation.js:1120
1120: if (__DEV__) {
^^^^^^^ identifier `__DEV__`. Could not resolve name
node_modules/react-native/Libraries/Animated/src/AnimatedImplementation.js:2162
2162: if (__DEV__) {
^^^^^^^ identifier `__DEV__`. Could not resolve name
Expo SDK version: 14.0.0
Flow version: 0.37.0
React Native version: 0.41.2
You can suppress errors in .flowconfig file, in [options] section as follows:
[options]
suppress_type=$FlowFixMe
suppress_comment=\\(.\\|\n\\)*\\$FlowFixMe\\($\\|[^(]\\|(\\(>=0\\.\\(3[0-8]\\|[1-2][0-9]\\|[0-9]\\).[0-9]\\)? *\\(site=[a-z,_]*react_native[a-z,_]*\\)?)\\)
Then, in [libs] section, you should point so called library definition file, like:
[libs]
./libdefs.js
And in libdefs.js just declare:
declare var __DEV__:string;
These changes should resolve your errors. See:
https://flow.org/en/docs/config/options/#toc-suppress-comment-regex and
https://flow.org/en/docs/libdefs/creation/ for details.
Looks like it might have been an oversight on the flow types for that release version.
All of those errors look fairly harmless though so you could just ignore it. If you absolutely cannot ignore it, update to a later version of React Native that's locked to a different version of Flow? I've had good results personally (no errors) with React Native # 0.42 and Flow # 0.38.
Found this issue which recommended updating the flowconfig to use the latest version from create-react-native-app. Seems to have worked for me.
I've recently upgraded to Protractor 5.1.1 and am facing some issues when setting cookies via browser.manage().addCookie()
The API has changed between versions 2 and 3 of Selenium-webdriver to expect an object rather than the previous 2..6 arguments. When I make the changes to my code to use the object, the typescript compiler complains saying that it expects 2..6 arguments.
old api:
browser.manage().addCookie('cookieName', 'cookieVal');
new api:
browser.manage().addCookie({name:'cookieName', value: 'cookieVal'});
I think this is because the #types/selenium-webdriver in the package.json of protractor v5.1.1 is pointing at version 2.53.39. The version of the actual selenium-webdriver the same package.json is referencing is 3.0.1.
Should this be the same value? Is anyone else experiencing problems with this?
Yup, this is happening because the type definitions was not written at the time.
workaround
Here is the workaround for now:
(browser.manage() as any).addCookie({name:'cookieName', value: 'cookieVal'});
We are setting browser.manage returned options object to any. Then we can give it the addCookie method.
OR
upgrade definitions
you could upgrade your #types/selenium-webdriver type definitions to version 3.
I'm having the same problem! I do know that the #types/selenium-driver is now updated to version 3.0.0.
I haven't had luck with this, but you could try installing it directly (i.e. npm install --save-dev #types/selenium-webdriver) and adding it to your list of types in your tsconfig.json file (i.e. types: [ "selenium-webdriver" ].
I am trying to compile the master branch of the react-native repo to submit a PR. I am following the docs https://facebook.github.io/react-native/docs/android-building-from-source.html
But doing exactly what do docs says, I get the following error on android:
Requiring unknown module "react/lib/ReactPropTypesSecret
Also running on ios gives similar kind of error:
Unable to resolve module react/lib/ReactPropTypesSecret from /Users/aakash/Projects/TestingPR/node_modules/react-native/Libraries/Utilities/deprecatedPropType.js: Unable to find this module in its module map or any of the node_modules directories under /Users/node_modules/react/lib/ReactPropTypesSecret
This issue occurs when an ReactNative-App based on RN 0.28 or older is upgraded to RN 0.30 or newer without to update also the "react"-package to at least 15.3.0.
Have you tried this?
If this will not solve your issue, you should provide your package.json.
I am using Flow with React Native 0.19.0. I am getting a bunch of errors in Animation files when running Flow, using the supplied .flowConfig:
node_modules/react-native/Libraries/Animated/src/AnimatedImplementation.js:143
143: type TimingAnimationConfigSingle = AnimationConfig & {
^ property `delay`. Property not found in
143: type TimingAnimationConfigSingle = AnimationConfig & {
^^^^^^^^^^^^^^^ object type
I get four more similar errors in the same file when running flow inside project root.
When I ignore the file AnimatedImplementation.js I get problems in other files where I reference functions in AnimatedImplementation.js.
Any ideas?
Make sure your Flow version is the same that your React Native version specifies in <your_app>/node_modules/react-native/.flowconfig. I get exactly the same error when trying to use a newer Flow version than 0.20.1 with React Native 0.19.
In my case, I resolved the issue by checking out branch 59d090c of Flow's GitHub repository, which is identical to the 0.20.1 release, and compiling the source.
Alternatively, you could upgrade to React Native 0.20 in your project. The release is just around the corner and supports Flow 0.21.