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

Ruby 3+ Getitng PhaseScript errors with the .plist generating. #431

Open
ajrahim opened this issue Jul 13, 2024 · 1 comment
Open

Ruby 3+ Getitng PhaseScript errors with the .plist generating. #431

ajrahim opened this issue Jul 13, 2024 · 1 comment

Comments

@ajrahim
Copy link

ajrahim commented Jul 13, 2024

I have to remove this phase script from the pod in order for the app to successfully run. However this is causing issues with automated deployments.

@esphung
Copy link

esphung commented Dec 24, 2024

Having same issue. The problem is in ios/HeapSettings.bundle/generate_settings.rb. One of the directory path variables is nil but being used as a String. But yeah...this script (generate_settings.rb) needs to be fixed:

diff --git a/react-native-heap.podspec b/react-native-heap.podspec
index 2c16ced99c999755fffc3b52895a02e0a056d05c..d5723d65380fc4745dc27af7740cc9d33930e118 100644
--- a/react-native-heap.podspec
+++ b/react-native-heap.podspec
@@ -23,11 +23,11 @@ Pod::Spec.new do |s|
   
   s.frameworks = "SystemConfiguration"
 
-  s.script_phase = {
-    name: 'Generate `HeapSettings.plist`',
-    script: '"$PODS_TARGET_SRCROOT"/ios/HeapSettings.bundle/generate_settings.rb',
-    execution_position: :after_compile,
-    shell_path: '/bin/bash'
-  }
+#   s.script_phase = {
+#     name: 'Generate `HeapSettings.plist`',
+#     script: '"$PODS_TARGET_SRCROOT"/ios/HeapSettings.bundle/generate_settings.rb',
+#     execution_position: :after_compile,
+#     shell_path: '/bin/bash'
+#   }
   s.resource_bundles = {HeapSettings: ['ios/HeapSettings.bundle/HeapSettings.plist.template', 'ios/HeapSettings.bundle/HeapSettings.plist']}
 end

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

No branches or pull requests

2 participants