pod-builder 5.0.0 → 5.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 6509579a498f83ab8b171004c0b3096a306b85b547392c2a6e16525d5f976fe9
-  data.tar.gz: 66bd6e1a6bf224b02ec05dbd51e5001ad0f2c29aa03baba43037e7d4616057fe
+  metadata.gz: 6e761d8fa097790ad9ff4e292ba83ba8e9673b82c21eee69122a8e34063659f0
+  data.tar.gz: 5e31d711b5910b0a5ae1f2667a114f219f7f93614e819d19e255a9864ffa9fcd
 SHA512:
-  metadata.gz: bbd9e59727c97c102429d4af1fe1b6a2c2e67c8b4460fd52582b6b3f0410abb6788340c3821d931d46524795a67e13102612f3444e9e44c2c4078840c13ab13e
-  data.tar.gz: 59ff68c1e2b9130f647d25152ad9729105ffbc55e3e77d89e0221bf6bc06da45d612d258e46f1102e0f8d1e20cdb47704c88256b4ecbf0bba33593efed8184cc
+  metadata.gz: 74f2b675929b005266ddb41c0809941dd984cec4f6f4148cdf615c54e6367f34d5d7431c6a140545431f9f6ef30e08eb77efcd4963133134fea6c2089badebc6
+  data.tar.gz: 944835d7249f5ff560af5668ad0798025d32f7172b0d0f40675b7b9b67ae96147ba06483f3ec1a7f061f4eb16e3694e874aeea9862e1717b5276b9e6556beef0

data/README.md

@@ -203,6 +203,15 @@ _PodBuilder.json_ allows some advanced customizations.
 
 ## Supported keys
 
+#### `development_team`
+
+Starting with Xcode 14 it is mandatory to sign both frameworks and framework bundles. PodBuilder will try to automatically extract the developer team from the application, however there are cases where this will fail and the development_team needs to be added explicitly in the configuration file.
+
+
+#### `development_language`
+
+Starting with Xcode 14, when the main language is different than english, it might be necessary to explicitly set the default app language to properly localize app's extensions. Use the ISO 639-1 code.
+
 #### `spec_overrides`
 
 This hash allows to add/replace keys in a podspec specification. This can be useful to solve compilation issue or change compilation behaviour (e.g. compile framework statically by specifying `static_framework = true`) without having to fork the repo.

data/lib/pod_builder/configuration.rb

@@ -78,6 +78,7 @@ module PodBuilder
       attr_accessor :pre_actions
       attr_accessor :post_actions
       attr_accessor :development_team
+      attr_accessor :development_language
     end
 
     @build_settings = DEFAULT_BUILD_SETTINGS
@@ -119,6 +120,7 @@ module PodBuilder
     @post_actions = {}
 
     @development_team = ""
+    @development_language = nil
     
     def self.check_inited
       raise "\n\nNot inited, run `pod_builder init`\n".red if podbuilder_path.nil?
@@ -252,7 +254,11 @@ module PodBuilder
             Configuration.development_team = value
           end
         end
-
+        if value = json["development_language"]
+          if value.is_a?(String) && value.length > 0
+            Configuration.development_language = value
+          end
+        end
         Configuration.build_settings.freeze
 
         sanity_check()
@@ -297,6 +303,7 @@ module PodBuilder
       config["build_using_repo_paths"] = Configuration.build_using_repo_paths
       config["react_native_project"] = Configuration.react_native_project
       config["development_team"] = Configuration.development_team
+      config["development_language"] = Configuration.development_language || "en"
       
       File.write(config_path, JSON.pretty_generate(config))
     end

data/lib/pod_builder/install.rb

@@ -426,3 +426,18 @@ module PodBuilder
     end
   end
 end
+
+# CocoaPods seems to hard code the development language to english
+# By monkey patching the project save we make sure that the to manually rewrite the 
+# development language if it has been manually specified in PodBuilder's configuration
+class Xcodeproj::Project
+  alias_method :swz_save, :save
+  
+  def save(save_path = nil)
+    if development_language = PodBuilder::Configuration.development_language
+      root_object.development_region = development_language
+    end
+
+    swz_save(save_path)
+  end
+end 

data/lib/pod_builder/rome/post_install.rb

@@ -381,7 +381,7 @@ Pod::HooksManager.register('podbuilder-rome', :post_install) do |installer_conte
       # There seems to be a potential bug in CocoaPods-Core (https://github.com/CocoaPods/Core/issues/730)
       if spec.nil?
         # Given the above issue when all specs of a pod are subspecs (e.g. specs contains Pod1/Subspec1, Pod1/Subspec2, ...) we'll fail getting the correct specification by relying on module name
-        spec = specs.detect { |t| t.name.split("/").first == module_name }
+        spec = specs.detect { |t| t.name.split("/").first == module_name } || specs.detect { |t| t.parent&.module_name == module_name }
       end
 
       next if spec.nil?

data/lib/pod_builder/version.rb

@@ -1,3 +1,3 @@
 module PodBuilder
-  VERSION = "5.0.0"
+  VERSION = "5.1.1"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: pod-builder
 version: !ruby/object:Gem::Version
-  version: 5.0.0
+  version: 5.1.1
 platform: ruby
 authors:
 - Tomas Camin
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2022-09-14 00:00:00.000000000 Z
+date: 2022-12-20 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -235,7 +235,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.2.32
+rubygems_version: 3.3.7
 signing_key:
 specification_version: 4
 summary: Prebuild CocoaPods pods