Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The native module for Flipper seems unavailable. #4240

Closed
nikoden-io opened this issue Oct 19, 2022 · 7 comments
Closed

The native module for Flipper seems unavailable. #4240

nikoden-io opened this issue Oct 19, 2022 · 7 comments
Assignees

Comments

@nikoden-io
Copy link

nikoden-io commented Oct 19, 2022

🐛 Bug Report

After installing, v 0.171.1, got a warning message "The native module for Flipper seems unavailable. Please verify that react-native-flipper is installed as yarn dependency to your project and, for iOS, that pod install is run in the ios directory."
Flipper plugins are not working anymore, downgrade react-native-flipper version to 0.162.0 fix the issue but disabled updates for newest versions.

To Reproduce

  1. Create RN project
  2. yarn add react-native-flipper
  3. Install "redux-debugger" plugin for example
  4. Launch app on iOS (simulator or device) and Flipper 0.171.1
  5. Flipper plugins don't work

Environment

Flipper desktop: 0.171.1
RN 0.68.2
react-native-flipper 0.171.1
redux-flipper 2.0.1

@nikoden-io
Copy link
Author

nikoden-io commented Oct 19, 2022

Podfile content:
require File.join(File.dirname(node --print "require.resolve('expo/package.json')"), "scripts/autolinking")
require File.join(File.dirname(node --print "require.resolve('react-native/package.json')"), "scripts/react_native_pods")
require File.join(File.dirname(node --print "require.resolve('@react-native-community/cli-platform-ios/package.json')"), "native_modules")

require 'json'
podfile_properties = JSON.parse(File.read(File.join(dir, 'Podfile.properties.json'))) rescue {}

platform :ios, podfile_properties['ios.deploymentTarget'] || '12.0'
install! 'cocoapods',
:deterministic_uuids => false

target 'Pilot2' do
use_expo_modules!
config = use_native_modules!

use_frameworks! :linkage => podfile_properties['ios.useFrameworks'].to_sym if podfile_properties['ios.useFrameworks']

flags = get_default_flags()

use_react_native!(
:path => config[:reactNativePath],
:hermes_enabled => flags[:hermes_enabled] || podfile_properties['expo.jsEngine'] == 'hermes',
:fabric_enabled => flags[:fabric_enabled],
# An absolute path to your application root.
:app_path => "#{Dir.pwd}/.."
)

pod 'Firebase/Analytics'

permissions_path = '../node_modules/react-native-permissions/ios'
pod 'Permission-Camera', :path => "#{permissions_path}/Camera"
pod 'Permission-Notifications', :path => "#{permissions_path}/Notifications"

if !ENV['CI']
use_flipper!({ 'Flipper' => '0.171.1' })
end

post_install do |installer|
react_native_post_install(installer)
__apply_Xcode_12_5_M1_post_install_workaround(installer)
end

post_integrate do |installer|
begin
expo_patch_react_imports!(installer)
rescue => e
Pod::UI.warn e
end
end

end

@zT0Tz
Copy link

zT0Tz commented Oct 19, 2022

I'm having the same error,

Flipper desktop: 0.171.1
RN: 0.68.2
react-native-flipper: 0.171.1
redux-flipper: 2.0.1

@vdanylov
Copy link

Same thing. Tried several redux-debugger plugins:

Flipper desktop: 0.171.1
RN: 0.66.4
react-native-flipper: 0.171.1
redux-flipper: 2.0.1

@djMax
Copy link

djMax commented Oct 21, 2022

This is happening to me without any plugins:

RN: 0.67.4
react-native-flipper: 0.171.1
Flipper: 0.171.1

The error is "right" in that Flipper is NOT listed in the NativeModules. I'm digging further to see if I can see anything, but the Flipper initialization code seems to run fine, but NativeModules doesn't get modified.

@djMax
Copy link

djMax commented Oct 21, 2022

More detail - after yarn-updating to 171, after running pod install, there is NO pod in Podfile.lock for react-native-flipper. 0.162.0 will add an entry. It's not clear to me exactly how this resolution happens

@nikoant nikoant self-assigned this Oct 21, 2022
lblasa pushed a commit to lblasa/flipper that referenced this issue Oct 25, 2022
Summary:
Related to facebook#4240

Resolving facebook#3859 led to breaking changes in react-native-flipper which made it incompatible with react-natvie < 0.69.
In this diff we migrate our example app to react-native 0.69 and add a notice to our readme about the react-native 0.69+ requirement

Reviewed By: lblasa

Differential Revision: D40673740

fbshipit-source-id: 57abd22f7578e588a79a5d4f8235c8d446b7b390
facebook-github-bot pushed a commit that referenced this issue Oct 25, 2022
Summary:
// allow-large-files

Pull Request resolved: #4265

Related to #4240

Resolving #3859 led to breaking changes in react-native-flipper which made it incompatible with react-natvie < 0.69.
In this diff we migrate our example app to react-native 0.69 and add a notice to our readme about the react-native 0.69+ requirement

Reviewed By: lblasa

Differential Revision: D40673740

fbshipit-source-id: 18f4742449d115be7a5100f2bc4d834dcebea80f
@aigoncharov
Copy link
Contributor

Quoting #4265: Resolving #3859 led to breaking changes in react-native-flipper which made it incompatible with react-natvie < 0.69.

As a result, we had to make a hard decision of supporting future react-native-flipper updates only for react-native 0.69+. Please, upgrade your react-native to 0.69+. If you want to keep using react-native < 0.69, please, keep using react-native-flipper 0.162
I wan to highlight that you still can use new versions of Flipper itself! For instance, you should be able to run react-native-flipper@0.162 with Flipper@0.171.1.

@saikishore-232
Copy link

Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1. How to fix this compliation error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants