I am currently trying to set up the FBSDK for react-native (react-native-fbsdk).
It was working great in previous versions when I was running react-native-fbsdk#0.1.0 and react-native#0.41.0.
However, right now with react-native-fbsdk#0.6.0 and react-native#0.45.1, I had to reinstall a lot of components.
My app is sending me:
Warning: Native component for "RCTFBLikeView" does not exist
Warning: Native component for "RCTFBLoginButton" does not exist
Warning: Native component for "RCTFBSendButton" does not exist
Warning: Native component for "RCTFBShareButton" does not exist
So considering to other posts like this, this is supposed to be due to a problem with libRCTFBSDK.a.
However, after removing and adding back this file from Build Phases, the problem is still occuring.
Is there a way to find the latest version of this file somewhere? I do not see it in the node_modules and I am only adding it from workspace.
Related
I am building a menu bar app witih rumps and using py2app to export. When I am building using Alias mode its completely fine.
When I am building for production however it prompts me this error:
ValueError: New Mach-O header is too large to relocate in '/Users/isaacng/Developer/Menu Bar Spotify/Rumpify/dist/rumpify.app/Contents/Resources/lib/python3.10/lib-dynload/cryptography/hazmat/bindings/_rust.so' (new size=2264, max size=2260, delta=72)
I have tried rolling back a few versions of py2app and nothing. I found this FAQ in py2app but I really don't understand how to rebuild binaries with enough space?
https://py2app.readthedocs.io/en/latest/faq.html
This error can be avoided by rebuilding binaries with enough space in the Mach-O headers, either by using the linker flag “-headerpad_max_install_names” or by installing shared libraries in a deeply nested location (the path for the install root needs to be at least 30 characters long).
Very greatful if anyone can figure this out! I really don't want to use pyInstaller!!
When I am trying to build my ios app in xcode, the build is failing due to lexical or preprocessor issue the error shows up like this
This was a problem specific to the react-native-device-info module.
For your specific case you may try v1.6.1 or higher (currently at 2.0 as of May 21, 2019) of the library and that should fix things for you.
For others interested more generally in the problem, this is a react-native library that uses native code, so it has an XCode project embedded within it for use in react-native after you run react-native link react-native-device-info. Unfortunately, the library was not including any directories in it's header search path, so it was of course unable to find the header files for the react-native objects it was using locally.
A library user proposed a change that fixed that problem for tvOS, and I extended the change to cover iOS as well, and now the library no longer generates errors like this for iOS or tvOS targets.
Perhaps someone with a similar issue may find the specific changes required for the fix useful in their projects
I can't seem to get the Photoeditor packages properly imported into my project while following the instructions here and here. It doesn't seem to work after trying to install using pods and manually. The issue is that after attempting to install, one or more other packages in my current project become interrupted or mishandled preventing me to launch the application. It disrupts these things usually causing an "Argument too long: recursive header expansion" error in Xcode. This happens only after I try installing.
Trying to create a NEW project which targets -both- macos and ios/android seems to fail.
Steps:
Followed steps on react native website, using create-react-native-app to get a native application. It works fine.
Use react-native-macos init and macos to get the mac app - it also works fine.
Noticing that #1 uses an App.js and #2 uses some sort of index.platform.js model, I change the xcode project in #2 to look for App.js instead. This at least makes sure the same code is reached.
As the react-native-macos github page says to do, I merge #2 into #1.. (unclear whether should overwriting, used 'ditto' command)
Add the rn-cli.config.js file to root, as react-native-macos says to do
Missing modules when I try to run macos - fails to bundle.
It looks to me like the 'react-native' folder in the node modules is somehow screwing up the react-native-macos folder. I'm still trying a variety of things but it's been exhausting considering how easy 'merge into your existing project' sounds.
https://github.com/ptmt/react-native-macos <- what i want to merge in
You likely will not be able to use create-react-native-app and react-native-macos together without some trail and error. This is because create-react-native-app actually creates an Expo app which is built on top of react-native but tries to abstract away a lot of the native details from the end user. For example you can't use any native modules that are not shipped with Expo when using create-react-native-app. The documentation of react-native-macos is likely assuming you are using react-native init which creates a base react-native project that you have to handle building on your own instead of offloading the build process to Expo.
I have a "fat" framework built for iOS, which is being used in a debugging tool built for macOS. Previously I was linking this framework statically, which worked, even though XCode complains about it being built for the simulator (since the architecture is the same). But now, newer versions of the library are dynamic, so that route doesn't work, as the tool is a command line application, which doesn't support embedding frameworks.
I could turn it into an application bundle, it seems, in order to solve that, but I'm not sure what this entails (creating a new project?). I can certainly figure it out but ..
In the meantime, I thought I'd load the library dynamically using dlopen() etc and retrieve the classes/methods I need (I already have some code for this which at least compiles). However, that call fails with the following message:
no suitable image found. Did find:
/<path to library file>: mach-o, but built for simulator (not macOS)
Since linking statically is only a warning and actually works, is there a way to make dlopen work as well?
Recompiling the framework itself is not an option for me in this situation.
Are you considering editing the binary of the dylib framework? If so in the Macho-O header you could try changing LC_VERSION_MIN_IPHONEOS to LC_VERSION_MIN_MACOSX.Probably it won't be enough,but it's a simple change for a quick test. Here's a screenshot comparison of those load commands in MachOView
Also covered the other way round here