motion-fabric 0.5 → 0.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: e83fc3b225b1ec4d3b1e546dbc739af849142c35
-  data.tar.gz: 5e08fae2357fd556715bab9b4f27d2c50703422e
+  metadata.gz: 6fb9b887a9bde8b27368791de163b5ac4fc7163b
+  data.tar.gz: b9a7c17ee33271ce1abc0812a0c8dae61793f49a
 SHA512:
-  metadata.gz: 0be175a2a9d4a8889354ca45a3834698671738afc1310621f953b79f8705b6597010bad57ec0db6c04c228f1596af86d6c78c3859f1dc98705da414018194c49
-  data.tar.gz: 5fed7cd8be906df435579d9b61af182cfbc4cbb7bb4e19a89035764fc3bc1ab17e5f8f633933b490aa91d42348e8e9b4eac5aa7c8fcea676724f797ca3bfe9a2
+  metadata.gz: a78596780ea40d6da5dae3286611618e7c36b2b4a9c7f5bfb6727583858a2ec53390eb72949368a456999e26006b6195946928e88df42d51421b48aea50dc35f
+  data.tar.gz: 16c085055a812eca29bf9f559f42a21cc9435981bc5df079b7f69975c082a309dc4800336f241a77325eb0d1f63a83c59e5f866af2e7fdc6fec1b3b89a48c0e5

data/lib/motion-fabric.rb

@@ -27,6 +27,8 @@ unless defined?(Motion::Project::Config)
   raise "This file must be required within a RubyMotion project Rakefile."
 end
 
+require 'motion-cocoapods'
+
 class FabricKitConfig
   attr_accessor :name, :info
 
@@ -80,11 +82,24 @@ module Motion::Project
   end
 end
 
+require 'motion-cocoapods'
+
 Motion::Project::App.setup do |app|
   app.pods do
     pod 'Fabric', '~> 1.6'
     pod 'Crashlytics', '~> 3.7'
   end
+
+  # FIXME: TwitterCore and TwitterKit are static ios frameworks, but the .o
+  # files inside the archives include the "-framework Fabric" flag in their
+  # auto link section information. The linker will look for that framework and
+  # fail. As a workaround we include the Fabric framework path as a framework
+  # search path. The following warning will be printed, but everything will
+  # work fine at runtime:
+  # ld: warning: Auto-Linking supplied '/Users/mark/src/motion-fabric/sample_app/vendor/Pods/Fabric/iOS/Fabric.framework/Fabric', framework linker option at /Users/mark/src/motion-fabric/sample_app/vendor/Pods/Fabric/iOS/Fabric.framework/Fabric is not a dylib
+  # We will be able to fix this when motion-cocoapods supports the
+  # "use_frameworks!" option from Cocoapods.
+  app.framework_search_paths << './vendor/Pods/Fabric/iOS'
 end
 
 def fabric_setup(&block)
@@ -160,7 +175,7 @@ namespace :fabric do
       args << " -groupAliases \"#{ENV['groups']}\"" if ENV['groups']
       args << " -notifications \"#{ENV['notifications']}\"" if ENV['notifications']
 
-      system(%Q{#{pods_root}/Crashlytics/submit #{api_key} #{build_secret} #{args}})
+      sh %Q{#{pods_root}/Crashlytics/submit #{api_key} #{build_secret} #{args}}
     end
   end
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: motion-fabric
 version: !ruby/object:Gem::Version
-  version: '0.5'
+  version: '0.6'
 platform: ruby
 authors:
 - HipByte
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-04-14 00:00:00.000000000 Z
+date: 2016-05-25 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: motion-cocoapods
@@ -16,14 +16,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.7'
+        version: '1.8'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.7'
+        version: '1.8'
 description: Fabric in your RubyMotion applications.
 email: info@hipbyte.com
 executables: []