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

TypeError: Cannot read property 'getConstants' of null in version 0.21.1 with react native 0.76.5 - NOT EXPO #397

Closed
alvmatias opened this issue Dec 17, 2024 · 4 comments

Comments

@alvmatias
Copy link

What react-native version are you using?
0.76.5

What react-native-blob-util version are you using?
0.21.1

What platform does your issue occur on? (android/ios/both)
Android

Describe your issue as precisely as possible :

Steps to reproduce the issue or to explain in which case you get the issue
Every time i launch my app it crashes due to the issue seen in the next image:

Screenshot_1734464274

@RonRadtke
Copy link
Owner

Similar to #394

@RonRadtke
Copy link
Owner

I am working already the whole day on figuring out why it breaks - so far I am getting closer but I don't have a solution yet.
Please use the previous version for now.

@RonRadtke
Copy link
Owner

RonRadtke commented Dec 17, 2024

That's the cause of it:
react-native-community/cli#2563

So nothing on my side, but still nasty...

So there are basically 3 solutions:

  1. See if you manage to update the cli to the patched version
  2. Fix the cli manually by editing the file: @react-native-community\cli-platform-android\build\config\findPackageClassName.js as shown in the linked merge. Basically you just have to adjsut the regex at the end of the file. And afterwards you must clear android/build
  3. downgrade this library until a fixed version of RN is available and you can upgrade
  4. Downgrade to 0.19.1, build once, copy the section for this lib in android/build/generated/autolinking.json, upgrade, build once, replace the section in the file. From now on it should work.
    But tbh. downgrade ist probably the best solution till RN released a fixed version

RonRadtke pushed a commit that referenced this issue Dec 18, 2024
@RonRadtke
Copy link
Owner

I close the issue since we have a workaround live

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

2 participants